Community
Participate
Working Groups
Starting New AC on linux using the config file generated with SetConfig.sh utility gives the following error Error occurred during initialization of VM Unable to load native library: libjvm.so: cannot open shared object file: No such file or directory This is due to the <Jvm>/home/proj/tptp/vnaikawa/j2sdk1.4.2_10/jre/lib/i386/server/libjvm.so</Jvm> entry in the config file. The file libjvm.so does exist in the Java installation. If I remove the BC config block from the config file, AC starts up fine.
This error is specific to Backward compatibility on linux. We are trying to launch the fileServer for BC. Additional porting and investigation is required to get this working. In particular we depend on the plugins being loaded correclty to set up the classpath. This bug mentions that we are not loading libjvm correctly... it is possible that the load is in fact working but the call to initialize is failing... this from past linux experience. This bug does not need to be resolved until BC is ported to linux. (4.3 I believe)
It's not likely we will get backwards compatibility fixed and tested in time for i3 - although it was a stretch goal. Reducing priority and severity.
We decided to remove the default serviceconfig.xml file from our package. That means users will always have to run SetConfig, and therefore they will be getting the version that includes the backwards compatibility TLs in it. Hence, this becomes a must fix.
The expedient solution would be to ifdef this code for windows and address file transfer on linux when we have completed the BC linux port.
The code that starts the jvm for file transfer is now ifdef'ed for windows. We will need to address this issue on linux when we have started the general BC linux porting and testing.
Re-openning as the bug was not fixed. Just a workaround put in place to allow non-backward compatibility Linux new Agent Controller to work with a generated config file. Lowering severity to Normal and priority to P1, keeping an i3 target as there is still a stretch goal for Linux AC to work in BC mode.
Changed title to indicate this issue blocks backwards compatibility on Linux. Reset target to i4 - if time allows.
Retarget backwards compatibility support on linux to 4.3.
Target 4.3i2.
The issue here was that the LD_LIBRARY_PATH needed to be set so that it could find the lib. Since this is a platform specific env setting, the fix is to define the path properly in the start script ACStart.sh (RAStart.sh). That issue is tracked under bug 154387. *** This bug has been marked as a duplicate of 154387 ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
