Servlet SAPI questions
| From: | Chris Todd | Date: | Sun, 19 Nov 2000 18:04:01 +0000 |
| Subject: | Servlet SAPI questions | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38511@lists.php.net to get a copy of this message | ||
Hello PHP developers-
I was able to successfully build the PHP interpreter as a servlet on Linux,
and I am even able to access it to pull up the phpinfo page and a few other
pages. The problem I have is that I am only able to access something like
two to four scripts before the JVM core dumps. This may be related to some
of the other recent servlet-related bug reports, but what happens to me does
not exactly match, so I thought I'd ask you all about it.
To be a little more specific, I am running Red Hat 6.0 on intel, and I have
tried this with PHP 4.0.0, 4.0.2 and 4.0.3pl1. Same result. I have also
tried it with the following JVMs: IBM 1.1.8 and 1.3, Sun 1.2.2 and 1.3. I
built PHP
using --with-servlet --with-java --without-mysql --without-gd --without-xml
(I was trying to create the simplest interpreter possible). I also tried
building PHP either with or without the option "--disable-posix-threads",
since I wondered if this could be a Linux/Java threading problem. I got the
exact same result under all of these combinations.
Unrelated to this bug, I wanted to ask what the advantages were of using the
PHP interpreter as a servlet vs. using a "cgi servlet", which would contain
a method call to Runtime.exec("php myscript.php").
Sincerest regards,
Chris Todd
Software Engineer
Alabanza Corporation
ctodd@alabanza.com