| 1:34:50 PM PDT - Thu, May 3rd 2012 |
|
I just finished installing a 64-bit OpenSUSE 11.3 virtual machine and installing/testing ECCE 6.3. Here are my results:
1. I first installed the 64-bit ECCE binary distribution
2. The only package I needed to install via YaST after the base Linux install was "gtk2-devel". This was found by the "prerequisite check" option on the main install menu.
3. I was able to start the ActiveMQ mesage server just fine. I first edited the "server/ecce-admin/start_ecce_message_server" script and changed the "java -version >& /dev/null" line to just "java -version" so it would report the version number actually being used to start the server.
4. I ran the start_ecce_message_server script and it reported 1.6.0_17 as the java version before starting the server without problem.
5. I ran stop_ecce_message_server.
5. I started ecce (which implicitly restarted the server including both the data and message servers--depending on how you install you might need to explicitly run "start_ecce_server"). I verified the rest of ECCE worked as expected including the Builder with OpenGL and running an NWChem calculation locally. I then ran stop_ecce_server to stop both data and message servers.
6. I decided to install the JDK development kit because only the base java is bundled initially. This meant installing the "java-1_6_0-openjdk-devel" package via YaST. This was just just to see if the version changed because the full JDK isn't really needed just to run ECCE, but only if you are building ECCE from the source code distribution.
7. Re-running start_ecce_message server I got a new java version of 1.6.0_22. So both the first version of java and the new version of java are slightly different than the 1.6.0_20 you said you are running. It was able to successfully start the message server as well after installing JDK (note that prior to the JDK install the javac command is not found while it is found after so that's a quick way of seeing if you have a base Java or the full JDK).
So, my only recommendations to you would be to install the latest java-1_6_0-openjdk-devel package and see if that fixes your problem. Short of that you'll need to update to a newer OpenSUSE (or other Linux) if you want to run the 64-bit ECCE binary distribution. I actually think you'll get this same issue even if you build ECCE from the source code distribution because this problem is with starting the ActiveMQ server, not running any of the ECCE code. For the ActiveMQ server we just distribute a binary ActiveMQ distribution because java byte code should run on any platform regardless of where it is compiled (we get the binary ActiveMQ distribution directly from the ActiveMQ Apache website).
But, as mentioned before, the 32-bit ECCE binary distribution may work fine for you and that would be my other recommendation. I also tested this myself on my OpenSUSE 11.3 VM and it worked fine. I did find that there was a missing shared library for running the 32-bit Builder (libdrm.so.2), but I updated the ECCE 32-bit binary distribution to include this if you grab the latest version. Then it ran just fine including the message server, Builder, etc. So, my three recommendations in order are:
1. Try installing the latest java-1_6_0-openjdk-devel package via YaST and see if that fixes your problem starting the message server. Make the change so that either/both start_ecce_message_server and start_ecce_server report the actual java version being used so you know for sure it's not running something like java 1.4 that is known not to work with ActiveMQ.
2. Download and install/test the latest ECCE 32-bit binary distribution on your 64-bit system.
3. Upgrade to a newer OpenSUSE (at least 11.4 if not 12.1).
I can't think of anything else to try on this end so it's over to you. Based on my googling your error message from starting the server, it just seems like OpenSUSE 11 is somewhat problemmatic with certain java applications. ActiveMQ isn't the only one that reports this message if you do some googling yourself. Let me know if you are able to resolve this.
Gary
|