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

I just forge to say, if I run:

echo '<?php require_once("http://localhost:8080/JavaBridge/java/Java.inc");
echo java("java.lang.System")->getProperties();?>' | php -n -d
allow_url_include=On

It works... can it be a problem in my php.ini? I don't mind, since with the
JavaBridge.war deployed everything works fine.

2008/8/28 Carlos Eduardo Rodrigues Diógenes <cer...@gm...>

> Hi,
>
> I installed php java bridge successful.
>
> Using the JavaBridge.war I can share the PHP session (running in a apache
> server) with the "war" in the JBoss server.
>
> I removed the JavaBridge.war and tried to mimic it's configuration in a
> seam application that I'm developing, but I'm getting the 403 error when I
> try to run the php file apache. I can't understand what is wrong. I already
> look the logs, googled a lot, but can't find an aswear to this error.
>
> If someone can give me some hint to bypass this error I will be very
> grateful.
>
> Thanks,
> Carlos.
>

Just to follow up, it seems that the problem was related to including
java/Java.inc on every page view, which appeared to quickly overwhelm
the number of available threads (20). Instead it turns out that by
moving the Java.inc require to a separate script that only runs
periodically (when there are java bridge related actions to take), we
fixed the problem.

Justin


php...@li... wrote:
> Given that the exception starts with:
> 
> php.java.bridge.ThreadPool$Delegate.run(ThreadPool.java:60)
> 
> I'm wondering if this isn't some sort of thread pool error (or maxed out
> resource issue). Or if we've otherwise misconfigured things for our
> standalone setup (docs are pretty threadbare in this area).
> 
> Anyone have any ideas?
> 
> Justin
> 
> 
> php...@li... wrote:
>> 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
>> -------------------------------------------------------------------------
>> 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
> 
> -------------------------------------------------------------------------
> 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

Hi,

I installed php java bridge successful.

Using the JavaBridge.war I can share the PHP session (running in a apache
server) with the "war" in the JBoss server.

I removed the JavaBridge.war and tried to mimic it's configuration in a seam
application that I'm developing, but I'm getting the 403 error when I try to
run the php file apache. I can't understand what is wrong. I already look
the logs, googled a lot, but can't find an aswear to this error.

If someone can give me some hint to bypass this error I will be very
grateful.

Thanks,
Carlos.

Given that the exception starts with:

php.java.bridge.ThreadPool$Delegate.run(ThreadPool.java:60)

I'm wondering if this isn't some sort of thread pool error (or maxed out
resource issue). Or if we've otherwise misconfigured things for our
standalone setup (docs are pretty threadbare in this area).

Anyone have any ideas?

Justin


php...@li... wrote:
> 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
> 
> -------------------------------------------------------------------------
> 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

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

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