Re: [Php-java-bridge-users] Protocol error: Invalid document end at col 10.

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