php-java-bridge-users Mailing List for PHP/Java Bridge

Hi,

> seemingly random, frequent intervals greeted by a friendly
> "Protocol error; , Invalid document end at col 10.
> Check the back end log for details."

Can you please open a ticket (please use http://sourceforge.net/tracker/?func=add&group_id=117793&atid=679233), set the log level to 4 or above and attach the log at the end of the ticket?

Please start tomcat with the option -Dphp.java.bridge.default_log_level=4

JAVA_OPTS=-Dphp.java.bridge.default_log_level=4 /opt/tomcat/catalina.sh run


> Sadly, I do not know where to find the back end log.

Unless you have log4j ("chainsaw") running, errors appear in the tomcat log file. Look for OutOfMemoryErrors or something.
 

> The problem seems to be related to the error described in
> this previous thread:

No. The protocol error mentioned there was caused by "GNU Java", a buggy "Java" implementation which was popular until Sun has released Java as open source.


> The problem is there in both cases. In addition, even
> though the log file is specified explicitly in the
> standalone case, there are no error messages to be had
> there..

Well, over a year ago I have committed a change which suppresses all exceptions on default_log_level <= 3. Since the bridge code was mature I didn't think this may become an issue. 

However, the trace is still useful when a broken Java implementation is used or the back end reflects bugs in PHP itself (see http://bugs.php.net/bug.php?id=46451, which translates into a NullPointerException in the back end and a connection abort).  


> Any clues about how to resolve this problem? 

The communication failure can be caused by System.exit() as well as by a OutOfMemoryError. The details will be in the log file; we'll see. 


Regards,
Jost Boekemeier



      

Hello!

We are running an Ubuntu 8.04 server with a backend daemon program written in PHP that uses the PHP-Java-Bridge v5.3.2.1.2 for communicating with an external Java API. When we attempt to call up the PHP-Java-Bridge, we are at seemingly random, frequent intervals greeted by a friendly die() coming from line 784 in the Java.inc-file. The error message is:

"Protocol error; , Invalid document end at col 10. Check the back end log for details."

Sadly, I do not know where to find the back end log.

The problem seems to be related to the error described in this previous thread:

http://sourceforge.net/mailarchive/forum.php?thread_name=48B6FC13.4030406%40federatedmedia.net&forum_name=php-java-bridge-users

Like in the above thread, the error seems to spring up merely by doing

require_once("http://localhost:8080/JavaBridge/java/Java.inc");

.. which we do in a single place only when we need to communicate with the external Java API. Since in our case, the program calling JavaBridge functions is a single-threaded backend program, I do not believe that the problem of running out of threads should be an issue.

We have tried running the JavaBridge both as a Tomcat web app (using Tomcat 6.x and
Java/Sun 1.5.0_15) and as standalone:

java -jar JavaBridge.jar SERVLET_LOCAL:8080 3 /var/log/javabridge.log

The problem is there in both cases. In addition, even though the log file is specified explicitly in the standalone case, there are no error messages to be had there..

Any clues about how to resolve this problem? At the moment, our whole backend is crashing quite resolutely due to this issue.

Best regards,
Johannes Staffans
itCampus GmbH

php...@li... a écrit :
>> disable the 
>> TOMCAT5_SECURITY in /etc/default/tomcat5,
> 
> Not really. See FAQ http://php-java-bridge.sourceforge.net/pjb/FAQ.html#tomcat-security. :)

You're right, it is not needed. A complete production should not disable 
tomcat security.

I had some more troubleshooting to do and didn't want to use some time 
on tomcat security configuration, as i was already trying to figure how 
to install some four technos, all of which were totally new for me :-)