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

We've solved this problem: we had 'magic_quotes_runtime' set to 'On' in our php.ini file. I suspect this caused the bridge parser to choke. In any event, this parameter is deprecated (and absent in PHP 6). We turned it off and everything worked fine.

-Michael




Require java.inc directly from your back end in order to avoid
version-specific problems.

This Java message means that php crashed immediately during the first
connect. And your PHP message means that Java crashed when processing a
protocol request. There was a protocol related change from 5.4.4 to
5.4.4.2, see our NEWS file for details.

Please use require_once("http://.../java/Java.inc") to avoid these problems.
Or make sure to use the Java.inc distributed with your java back end.

Regards,
Jost Boekemeier

2. Jun 2009 5:21 vorm. schrieb am <
php-java-bridge-users@li...>:

I'm getting an error when running a simple bridge demo on CentOS with
Apache. The problem is that the demo PHP code runs fine when piped into PHP
(version 5.2.9) on the command line, but gives the following error when
accessed via the web server:

protocol error: <O v=\"1\" m=\"java.lang.System\" p=\"O\" n=\"F\"/>,
> required at col 8. Check the back end log for OutOfMemoryErrors.

I also see this warning in VMBridge.log:

"VMBridge WARNING: contextfactory: Orphaned context: ContextFactory:
Context# 1@, credentials: null, SimpleContextFactory: class php.java.bridge.
http.SimpleContextFactory, current loader:
sun.misc.Launcher$AppClassLoader@77cde100 removed."

No OOM error is logged, and a check of free memory shows over 1GB available.
The memory required by the demo app is trivial. We aren't running a J2EE
container, instead running the Java app standalone per the FAQ. The Java
version is 1.6. Here is the relevant line of Java code in our Main class:

static final php.java.bridge.JavaBridgeRunner runner =
php.java.bridge.JavaBridgeRunner.getInstance("8087");

I can connect to the runner successfully on port 8087, and have configured
the bridge to connect on that port.

The demo PHP code is:

<?php require_once("java/Java.inc"); echo
java("java.lang.System")->getProperties(); ?>

As noted above, this code runs fine from the command line. The error only
occurs when it's run through the web server.

Is there any other kind of problem besides an OOM error that could result in
a protocol error such as this?

Thanks,

-Michael

Require java.inc directly from your back end in order to avoid
version-specific problems.

This Java message means that php crashed immediately during the first
connect. And your PHP message means that Java crashed when processing a
protocol request.  There was a protocol related change from 5.4.4 to
5.4.4.2, see our NEWS file for details.

Please use require_once("http://.../java/Java.inc") to avoid these problems.
Or make sure to use the Java.inc distributed with your java back end.

Regards,
Jost Boekemeier

2. Jun 2009 5:21 vorm. schrieb am <
php...@li...>:

I'm getting an error when running a simple bridge demo on CentOS with
Apache. The problem is that the demo PHP code runs fine when piped into PHP
(version 5.2.9) on the command line, but gives the following error when
accessed via the web server:

       protocol error: <O v=\"1\" m=\"java.lang.System\" p=\"O\" n=\"F\"/>,
> required at col 8. Check the back end log for OutOfMemoryErrors.

I also see this warning in VMBridge.log:

        "VMBridge WARNING: contextfactory: Orphaned context: ContextFactory:
Context# 1@, credentials: null, SimpleContextFactory: class php.java.bridge.
http.SimpleContextFactory, current loader:
sun.misc.Launcher$AppClassLoader@77cde100 removed."

No OOM error is logged, and a check of free memory shows over 1GB available.
The memory required by the demo app is trivial. We aren't running a J2EE
container, instead running the Java app standalone per the FAQ. The Java
version is 1.6. Here is the relevant line of Java code in our Main class:

       static final php.java.bridge.JavaBridgeRunner runner =
php.java.bridge.JavaBridgeRunner.getInstance("8087");

I can connect to the runner successfully on port 8087, and have configured
the bridge to connect on that port.

The demo PHP code is:

       <?php require_once("java/Java.inc"); echo
java("java.lang.System")->getProperties(); ?>

As noted above, this code runs fine from the command line. The error only
occurs when it's run through the web server.

Is there any other kind of problem besides an OOM error that could result in
a protocol error such as this?

Thanks,

-Michael

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
php-java-bridge-users mailing list
php...@li...
https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users

I'm getting an error when running a simple bridge demo on CentOS with Apache. The problem is that the demo PHP code runs fine when piped into PHP (version 5.2.9) on the command line, but gives the following error when accessed via the web server:

	protocol error: <O v=\"1\" m=\"java.lang.System\" p=\"O\" n=\"F\"/>, > required at col 8. Check the back end log for OutOfMemoryErrors. 

I also see this warning in VMBridge.log:

	 "VMBridge WARNING: contextfactory: Orphaned context: ContextFactory: Context# 1@, credentials: null, SimpleContextFactory: class php.java.bridge. http.SimpleContextFactory, current loader: sun.misc.Launcher$AppClassLoader@77cde100 removed."

No OOM error is logged, and a check of free memory shows over 1GB available. The memory required by the demo app is trivial. We aren't running a J2EE container, instead running the Java app standalone per the FAQ. The Java version is 1.6. Here is the relevant line of Java code in our Main class:

	static final php.java.bridge.JavaBridgeRunner runner = php.java.bridge.JavaBridgeRunner.getInstance("8087");

I can connect to the runner successfully on port 8087, and have configured the bridge to connect on that port.

The demo PHP code is:

	<?php require_once("java/Java.inc"); echo java("java.lang.System")->getProperties(); ?>

As noted above, this code runs fine from the command line. The error only occurs when it's run through the web server.

Is there any other kind of problem besides an OOM error that could result in a protocol error such as this?

Thanks,

-Michael