Thanks Shawn. I tried that but the log just reports the following, which I
guess is usual:
EACCELERATOR hit: /path/to/script.php
EACCELERATOR cached: /path/to/script.php
There are no mention of memory leaks, or anything else.
Anyone got any other suggestions?
--
View this message in context:
Hi everyone,
I've installed eAccelerator 0.9.5.3 for PHP (installed as an Apache module).
I have noticed that when I use my TYPO3 application, I am getting memory
leak errors in Apache's error log. These errors only appear after I restart
Apache, and not whilst I am browsing the PHP pages. If
Thanks.
However, I'm using this process as a test. In the proper application we will
be using a JDBC or JDNI connection initiated by PHP to connect to our IDMS
database. Its complicated but it means we have to use the PHP-Java Bridge,
Java and JDBC. so we can't use ODBC.
I'm using this as a
Hi everyone!
This is driving me nuts!
I have setup a Linux webserver. Tomcat is running at the backend and is
connected to Apache at the frontend using mod_proxy. At the moment I have a
few test applications setup, which involves Apache sending JSP requests to
Tomcat via mod_proxy. They all work
4 matches
Mail list logo