From: <php...@li...> - 2006-09-05 20:24:25
|
Hi Brent, in version 3.1.4 the autoconf script doesn't check if the Java VM can really use JNI and always compiles the java.so against unix domain sockets. You can test this with the following command: /usr/java/jdk1.5.0_08/bin/java -jar /usr/local/lib/php/extensions/no-debug-non-zts-20050922/JavaBridge.jar LOCAL:@dummy 3 "" If the above command displays an error message, please configure the bridge to use TCP sockets (or use the J2EE/Tomcat back end) instead: Please either set: java.hosts = 127.0.0.1:9267 java.servlet = Off and start Java manually with the command: java -jar JavaBridge.jar Or start Java via a J2EE server or the Tomcat servlet engine, copy JavaBridge.war to the J2EE autodeploy folder, e.g.: /opt/tomcat/webapps, wait 10 seconds while the Java server starts the bridge and set the following options: java.hosts = 127.0.0.1:8080 java.servlet = On After that please restart the http server, for example with: apachectl restart. The test.php should now run without errors. However, can you please open a ticket (please use http://sourceforge.net/tracker/?func=add&group_id=117793&atid=679233) and attach the output of the following command: strace -s 1024 /usr/java/jdk1.5.0_08/bin/java -jar /usr/local/lib/php/extensions/no-debug-non-zts-20050922/JavaBridge.jar LOCAL:@dummy 1 "" 2>error.log The error log should display the reason why Java could not be started automatically. This will help us to improve the latest version, which already contains code for channel negotiation during startup. Regards, Jost Boekemeier ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de |