| 10:56:15 AM PDT - Fri, May 4th 2012 |
|
Hi Felix,
Good work tracking that one down. I agree inconsistent use of $JAVA_HOME can lead to problems. I never knew that the activemq sh wrapper script (which isn't an ECCE thing, but part of the ActiveMQ distribution) used $JAVA_HOME. Obviously it's easy for $JAVA_HOME to become unsynchronized with java being run via $PATH. Looking at java documentation I see that they expect users to keep them synchronized. That's a nice theory, but a poor design in practice. Since the rest of ECCE doesn't use $JAVA_HOME, I decided the best solution was to unset $JAVA_HOME prior to invoking the activemq sh script in start_ecce_server and start_ecce_message_server. That way it's guaranteed to run the same one as the client side of ECCE (if you look in the $ECCE_HOME/scripts/ecce wrapper, you'll see that the Gateway toolbar is started under a Java VM and that's how all these C++ applications are able to use java based messaging. It will also be consistent with what is reported for the version of java as part of the install (or build for compiling the ECCE source code distribution).
I just pushed out new downloads for this change (both binary distributions as well as the source code distribution). I assuming your solution was similar. If so, you shouldn't need to download/install again.
Gary
|