|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2001-03-09 13:34 UTC] sniper@php.net
[2001-03-09 17:04 UTC] alt at gimp dot org
[2001-03-09 17:47 UTC] sniper@php.net
[2002-02-24 06:06 UTC] yohgaki@php.net
[2002-03-28 00:00 UTC] php-bugs at lists dot php dot net
|
|||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Fri Oct 24 07:00:01 2025 UTC |
./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).