[Php-java-bridge-users] The infamous "protocol error: , Invalid document end at col 1."

[<php...@li...>]

We're running the PHP/Java Bridge as a standalone Java service (not as a
servlet engine or J2EE service), and seem to be sporadically getting the
following error (from line 768 of Java.inc):

"protocol error: , Invalid document end at col 1. Check the back end log
for details."

This happens even when we're not accessing the Java Bridge code---it
seems to crop simply by virtue of java/Java.inc being included (at first
glance). We're running the latest version of the bridge 5.2.2. Obviously
the xml doc to parse is blank, which is why this error is happening. I
just don't know why.

Additionally it seems strange for lib code like this to contain "die()"
statements since Java.inc gets included in larger codebases. In our case
it brings our platform to a screeching halt. Would be nice if it failed
a little more gracefully.

But that aside, any clue as to why this would be happening so frequently
given our set up? Assuming a standalone setup's errors get logged to
Apache's error log, we're seeing not related messages in the "back end
log". I'm wondering if I could/should just comment out that die()
statement starting on line 768...?

Thanks in advance,
Justin Watt
Federated Media