| 4:12:14 AM PDT - Fri, May 4th 2012 |
|
Okay, I got the 64-bit version running fine now. But it was quite a simple problem that caused all the trouble.
I started playing around a bit with the activemq directory in the ecce/server/ folder, getting to the activemq starting script. I checked it for the point where Java is detected or invoked. So the point is:
The ECCE installation script checks the Java installation via executing "java -version". This gave the JDK 1.6.0.
The server startup script checks Java with the help of $JAVA_HOME, which was in my case pointing to some ancient Java directory (1.5.0, not even sure if JRE or JDK). Why this was the case although the java "executable" was 1.6.0 doesn't make sense to me, but that was the point.
So I ensured that all Java environmental variables are set correctly to the JDK 1.6.0, ran the ECCE installation again and started the sever without any issues...
Conclusion: The mixture of Suse 11.3, Java 1.5.0 and ActiveMQ seems to be somewhat unhealthy.
Again, thank you very much for your help and all the suggestions.
Felix
|