ID: 14754 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: No Feedback +Status: Open Bug Type: Java related Operating System: Windows XP Home / Apache 1.3.24 -PHP Version: 4.2.1 +PHP Version: 4.2.1 & 4.3.0-dev New Comment:
Marking as open and updating version Previous Comments: ------------------------------------------------------------------------ [2002-10-08 11:12:20] [EMAIL PROTECTED] Iam still facing this bug even after trying with the snapshot specified.Iam running on apache 1.3.26 and win2K. I first experienced this on Php 4.2.2. Actually I took a closer look at the source.It seems to me that the reference to the global pointer to jvm( java.c ) seems to be reset resulting in the call to jvm_create after the first request(when it shouldnt, as the pointer should still be valid as we are not releasing the jvm pointer). Since there was no call to jvm_destroy, I guess some internal resource has been locked up resulting in JNI_CreateVM returning -1(undefined error in JNI.h) on the subsequent calls. Any help would be highly appeciated ------------------------------------------------------------------------ [2002-09-26 20:06:04] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2002-09-07 00:13:06] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-08-25 11:01:57] [EMAIL PROTECTED] Tested with the following: * Windows XP Home * Apache 1.3.24 * PHP 4.2.1 * Java SDK 1.4.0 The bug is still valid. Actually, even recompiling the Java class is not necessary - even if the class is run correctly, hitting Refresh in the browser multiple times (simulating heavy load) eventually causes the error to persist until Apache restart. Another observation - I change my class code and recompile, but PHP still uses the old class method code and returns outdated results, suggesting some kind of caching is taking place somewhere. I'm not sure if the two things are related or not. ------------------------------------------------------------------------ [2002-08-08 10:08:09] [EMAIL PROTECTED] Is this bug still valid for you in the recent releases? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14754 -- Edit this bug report at http://bugs.php.net/?id=14754&edit=1