|
From: <php...@li...> - 2010-06-11 10:27:02
|
The "hanging" is a separate issue. Since version 6 we use chunked
connections everywhere. HTTP/1.1 Transfer-Encoding: chunked requires
0\r\n as a shutdown sequence. If PHP crashes early, both, the
front-end and the back-end side will wait for each other's 0\r\n to
appear. Similar to this bug already fixed in the standalone component.
2010-05-23 <jostb@intern>
* server/php/java/bridge/http/ChunkedInputStream.java
(read): PR#3005379: Return the buffer contents before reading from
the network, in order to avoid deadlock.
Thanks to Oliver Billmann.
* server/php/java/bridge/http/ChunkedInputStream.java
(eof): New method
* server/php/java/bridge/http/ChunkedOutputStream.java
(eof): New method
* server/php/java/bridge/JavaBridgeRunner.java
(doPut): do not read/write 0\r\n chunk after an exception (e.g.:
OutOfMemoryError or RequestAbortException) occured
I think the new 6.x versions still aren't ready for prime time ... :(
On 6/11/10, Jost Boekemeier <jos...@go...> wrote:
> Hi Sravan,
>
> thank you very much for this bug report. This is a regression. We have
> added security checks to JavaProxy.php, see NEWS file and
> http://php-java-bridge.cvs.sourceforge.net/viewvc/php-java-bridge/php-java-bridge/server/buildJavaProxy.php?view=markup
>
> Since version 6.x the java/JavaProxy.php cannot read your .php file
> anymore.
>
> Please change the php_include_java option to "Off"
>
> -
> <init-param><param-name>php_include_java</param-name><param-value>On</param-value></init-param>
> +
> <init-param><param-name>php_include_java</param-name><param-value>Off</param-value></init-param>
>
> and include Java.inc in each of your PHP scripts. I will fix this in
> the CVS head and change the install instructions.
>
> Thanks again for reporting this issue.
>
>
> Regards,
> Jost Bökemeier
>
|