ID: 9659
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Bogus
Status: Open
Bug Type: Unknown/Other Function
Assigned To:
Comments:
Reopened. Sorry, my fingers were quicker than my brain. :)
--Jani
Previous Comments:
---------------------------------------------------------------------------
[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).
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9659&edit=2
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
