LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: dhrobertson

hi there,

I have tried to add more threads to my LAE server running on windows 2012 by editing the C:\Program Files (x86)\Lavastorm\LAE6.0\conf\brain\ls_brain.prop and changing the line below from 1 to 16:
ls.brain.controller.farm=( "${ls.brain.server.host=localhost}:${ls.brain.serv er.port}:16" )

after rebooting the server and running a graph manually through logistics manager, the graph just hangs and doesn't complete. I created a basic graph to test, just 4 static nodes with a line each to test the parallel processing and then concat and output to a file.
it just hangs and I don't know where to go and want to do to find out what the problem is.
If I run the graph with 1 thread (default) the graph runs.

what am I doing wrong?

regards

doug


UPDATE:

after playing around some more I have found that it seems to hang on a basic filter node for some reason. I have 3 flows and all 3 go through a filter node which just emits * and excludes 1 column..... any ideas why this would happen? it works fine when running through the BRE via the same server. the attached images is a screen shot of the processes which are just sitting doing nothing.filters.jpg

this is the error expressed for the filter nodes that don't process the data

<logEvent level="WARN" timestamp="1438334238000"><message xsi:type="errorMessage"><code key="brain.node.NodeControl.cpp.1267"/><message xsi:type="rawMessage"><![CDATA[socket i/o initialization timed out]]></message></message><detail context="Salmon::NED::NodeControl::waitForIo()" file=".\NodeControl.cpp" line="1267" xsi:type="cppDetail"/></logEvent><logEvent level="ERROR" timestamp="1438334238000"><message xsi:type="errorMessage"><code key="brain.node.NodeControl.cpp.1236"/><message xsi:type="rawMessage"><![CDATA[Cannot connect all streams]]></message></message><detail context="finishAccepts()" file=".\NodeControl.cpp" line="1236" xsi:type="cppDetail"/></logEvent>

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: xathras

I recommend you contact Technical Support for this one.