LAE

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

Originally posted by: rbonneux

Hello, I tried putting a Java Node into my graph (no additional code) and just press run to see if it would work, it did not.

I found the Training Session 8 Sample and tried running the sum sample and that did not work either. I have an updated server and local bre (4.5.2).

I'm wondering if it is my implementation or if it is something i'm missing in code. I'm getting the following error:

2012-02-22 12:40:04.924; WARN: The property ls.brain.machineName is not set. This might cause a Windows server to hang.
id: 0 chain: 0 group: 0
javaDetail: com.lavastorm.brain.BRAINApplication.loadMachineNa me(BRAINApplication.java@1193)

2012-02-22 12:40:05.053; ERROR: Error compiling the node.
id: 7 chain: 0 group: 0
javaExceptionDetail: com.lavastorm.tools.build.compiler.CompileExceptio n: 'Error compiling source unit.
Error occurred attempting to compile source with entry type (com.lavastorm.tools.build.java.MultiJavaBuiltUnit ).
Exception thrown:
java.lang.NullPointerException
at com.lavastorm.tools.build.java.JavaSourceCompiler. compile(JavaSourceCompiler.java:177)
at com.lavastorm.tools.build.java.JavaSourceCompiler. compile(JavaSourceCompiler.java:56)
at com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java:98)
at com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java:56)
at com.lavastorm.tools.build.BuilderCompiler.compile( BuilderCompiler.java:16)
at com.lavastorm.brain.node.build.NodeBuilderCompiler .compile(NodeBuilderCompiler.java:77)
at com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java:98)
at com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java:56)
at com.lavastorm.brain.node.NodeWrapper.buildJavaNode (NodeWrapper.java:1088)
at com.lavastorm.brain.node.NodeWrapper.load(NodeWrap per.java:1066)
at com.lavastorm.brain.node.NodeWrapper.run(NodeWrapp er.java:613)
at com.lavastorm.brain.node.NodeWrapper.main(NodeWrap per.java:1151)
Compilation diagnostics:';
stack trace:
com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java@102)
com.lavastorm.tools.build.cache.CachingBuilder.bui ldAndLoad(CachingBuilder.java@56)
com.lavastorm.brain.node.NodeWrapper.buildJavaNode (NodeWrapper.java@1088)
com.lavastorm.brain.node.NodeWrapper.load(NodeWrap per.java@1066)
com.lavastorm.brain.node.NodeWrapper.run(NodeWrapp er.java@613)
com.lavastorm.brain.node.NodeWrapper.main(NodeWrap per.java@1151)
javaDetail: com.lavastorm.brain.node.NodeWrapper.buildJavaNode (NodeWrapper.java@1091)

2012-02-22 12:40:05.060; ERROR: Node failed.
id: 8 chain: 7 group: 0
javaDetail: com.lavastorm.brain.node.NodeWrapper.run(NodeWrapp er.java@651)


Anyone have any ideas, or an extremly simple Java node that i can run that will test weather its coding or implementation?

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

Originally posted by: Tim Meagher

Hi,

I'm pretty sure that the problem is because the system can't locate the java compiler.
I assume that this is occurring while running against a Unix or Solaris install, as the Lavastorm desktop comes packaged with the correct JDK version required to run the nodes.

We do not package Java with the unix based installers and as mentioned in the LAE Enterprise Installation Guide, this is 3rd party software that needs to be installed prior to installing the LAE.

This requires a 1.6 version of the JDK (not just the JRE).

After installing the correct version of the JDK, you can start the LAE installation.

As part of the installation instructions, you are prompted for the java executable. The value provided should be the java.exe from the JDK bin directory (not the JDK/jre/bin directory).

I'm pretty sure you can sort this all out without having to reinstall by just modifying the PATH entry in your .profile.lavastorm or .cshrc.lavastorm file that gets created with the install - to point it to the bin directory containing correct java executable, but ... I'm not sure that this is the only place where the path is used, so it's safer to start with a fresh installation.

Still, the error message you posted is ugly and is cryptic in that there no information is provided as to why the error is occurring.
I will raise this as a bug that we can fix in later releases.


Let me know if this fixes the problem or if you need further assistance.

Tim.