ID: 9659
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Java related
Operating System: Linux RH 6.1
-PHP Version: 4.0 Latest CVS (09/03/2001)
+PHP Version: 4.0 Latest CVS (
New Comment:
Please test with PHP 4.1.1+JDK 1.2 and report the result back Thanks.
Previous Comments:
------------------------------------------------------------------------
[2001-03-09 17:47:35] [EMAIL PROTECTED]
Reopened. Sorry, my fingers were quicker than my brain. :)
--Jani
------------------------------------------------------------------------
[2001-03-09 17:04:24] [EMAIL PROTECTED]
Please note that 9658 and 9659 are not related. They resulted from two
different areas of tests being performed on the servlet sapi.
------------------------------------------------------------------------
[2001-03-09 13:34:33] [EMAIL PROTECTED]
This info moved to #9658
------------------------------------------------------------------------
[2001-03-09 12:34:25] [EMAIL PROTECTED]
./configure --with-java --with-servlet
Sun JVM (also happens with IBM JVM).
Java version "1.3.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_02)
Java HotSpot(TM) Client VM (build 1.3.0_02, mixed mode)
sapi_servlet_ub_write() and other native methods should
check for java exceptions when calling java methods.
The call to
(*jenv)->CallVoidMethod(jenv, servlet, write, arg);
should really be followed by :-
{
jthrowable exc;
exc = (*jenv)->ExceptionOccurred(jenv);
if (exc) {
(*jenv)->ExceptionClear(jenv);
}
}
or similar with reporting capabilities.
(When I applied this patch it seemed to fix the exception problem).
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=9659&edit=1
