ID: 18600
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: Java related
Operating System: Windows 2000
PHP Version: 4.2.3
New Comment:
Hi,
I'm reporting the same error using:
Win2k Server
apache_2.0.36-win32-x86-no_ssl.msi
php4-win32-latest.zip (PHP Version 4.2.3)
j2sdk-1_4_1_01-windows-i586.exe or (jdk-1_2_2_014-windows-i586.exe)
... I've got periods of errors and periods of success when
instantiating $system = new Java("java.lang.System"); from within
PHP.
Error message is:
"Fatal error: Unable to create Java Virtual Machine in ..."
I see a lot of such bug reports around but still no solution ;-(.
Any ideas?
Thanx
Alberto
Previous Comments:
------------------------------------------------------------------------
[2002-11-28 07:19:46] [EMAIL PROTECTED]
Hi
I'm asking it again:
Is anyone using sablotron (ext/xslt) together with the java extension,
then you're in bad luck, because:
sablotron < 0.97 and jdk >= 1.3 does not work together.
Sablotron 0.97 is not out yet, but there is an RC1 in their CVS
(didn't
find a link to download it), which should solve the problem..
try not loading the sablotron extension and see if it solves the
problem
unix people which have problem with even starting up, should try the
symlink trick:
make a symlink from java.so to libphp_java.so and see if that works.
chregu
------------------------------------------------------------------------
[2002-11-05 05:43:54] [EMAIL PROTECTED]
I am also seeing this bug, unfortunatly I'm running apache 1.x on
Solaris 8.
Works fine for a little while, then stops working after a number of
requests. I can stop the symtoms by turning off keep-alive in apache or
by reducing the requests per child to a very low number. Of course,
none of these solutions are acceptable. I am trying to test 4.3.0pre2
just now but having compilation errors. More later.
------------------------------------------------------------------------
[2002-10-31 08:51:16] [EMAIL PROTECTED]
Yeah the only real issue I can see here is that this is a Windows
specific issue. I've looked through the the DSP file, and read up on
specific linking issues in Windows... everything looks right from the
end of PHP.
I'm guessing this can be one of (or possibly all of) these things:
A) specific to a JVM version - in which case we'd need to find out
which one works, and then update the specific hooks into PHP to use the
newer versions.
B) Windows not liking Java at all - not much we can do about that.
C) specific to PHP alone - in which case someone with more Windows dev
experience will have to take a look at this. As I don't see any real
issue with the way we're linking and calling things (beyond the really
resource intensive comments).
------------------------------------------------------------------------
[2002-10-31 07:44:50] [EMAIL PROTECTED]
I found this problem using Apache 1.x on Win2k.
PHP 4.2.3 causes the JVM create failure (although I couldn't get any
access violations).
Under IIS4 , the access violation causes some serious problems, albeit
intermittently. I found that starting small with Java-inclusive scripts
allowed some java work to be done (such as retrieving JVM versions,
etc).
However, when I started some more serious Java work with some custom
classes I got both the JVM create failure and an access violation which
crashed IIS. A reboot was necessary to bring IIS back up (Win2k
wouldn't even let me force kill the process!!).
I took a look at the latest snapshot posted below, but this caused an
immediate crash in Apache upon starting the service.
Any other suggestions?
------------------------------------------------------------------------
[2002-09-27 12:00:04] [EMAIL PROTECTED]
just to add to the list of symptoms.
First time I run a script, I get
Warning: Unknown list entry type in request shutdown (0) in Unknown on
line 0
when the script is ending. The next time I try to load the same script,
I get
Fatal error: Unable to create Java Virtual Machine in
c:\web\qvc\reports\test.php on line 2
win2k, j2sdk1.4, php 4.2.3.
Does that help?
------------------------------------------------------------------------
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/18600
--
Edit this bug report at http://bugs.php.net/?id=18600&edit=1
