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

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

More information, found the "back end log" for us it's
/var/log/https/error_log

And we seem to be getting tons of NullPointerExceptions:

Aug 28 12:22:47 VMBridge ERROR: An exception occured:
java.lang.NullPointerException
java.lang.NullPointerException
   at php.java.bridge.StringCache.put(StringCache.java:122)
   at php.java.bridge.StringCache.getString(StringCache.java:155)
   at php.java.bridge.JavaBridge.getCachedString(JavaBridge.java:2023)
   at
php.java.bridge.ParserString.getCachedStringValue(ParserString.java:89)
   at php.java.bridge.Request.begin(Request.java:232)
   at php.java.bridge.Parser.CALL_BEGIN(Parser.java:134)
   at php.java.bridge.Parser.parse(Parser.java:195)
   at php.java.bridge.Request.handleRequest(Request.java:377)
   at php.java.bridge.Request.handleRequests(Request.java:485)
   at php.java.bridge.JavaBridge.run(JavaBridge.java:213)
   at php.java.bridge.ThreadPool$Delegate.run(ThreadPool.java:60)

Any ideas?

Our version of Java (from RHEL5):

$ java -version
java version "1.4.2"
gij (GNU libgcj) version 4.1.2 20071124 (Red Hat 4.1.2-42)

Much appreciated.
Justin Watt


php...@li... wrote:
> 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
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users