Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error with initializing HPI library

Status
Not open for further replies.

princegbenga

IS-IT--Management
Jul 31, 2003
7
A2
I got the following error while trying to start an application process:

"There was an error trying to initialize the HPI library.
Please check your installation. HotSpot does not work correctly when installed in the JDK 1.2 Soaris Production Release, or with any JDK 1.1.x release.
The JAVA Virtual Machine failed to initialize, exiting.
Run-time exception error; current exception: long
No handler for exception."

Please, does any has a useful tip or solution steps to resolve this problem.

Thanks,

Princegbenga.
 
I searched all resources that were available, which includes the JNI books, JNI FAQ, forums and the knowledge bases for the answer. One resource located at pointed me toward a missing "libhpi.so", but it is in the LD_LIBRARY_PATH so I dismissed that as the problem.

The problem got resolved in the process of trying anything that affected the libraries to hopefully make it work. I noticed that the $(JDK)/jre/lib/sparc/ directory had the same libjvm.so (byte size comparison) as did the $(JDK)/jre/lib/sparc/client directory, since the $(JDK)/jre/lib/sparc/server directory had different sized libraries, I put that directory in the front of the LD_LIBRARY_PATH and everything started to work as expected.

What was extremely interesting is that in the process of trying everything, I moved the task into ant (it uses a Runtime.exec to execute the command) for ease of repeating the testing scenario. The ant task executed the invoker.exe and the JVM was created properly through the invocation API. I don't know why the fact of using a jvm that is running the default "client" VM would be able to successfully load the executable that would spawn the jvm worked.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top