Hi, I'm experiencing connections problems between Apache and WebSphere that are peventing Apache processes from getting destroyed.
The visible error is that httpd processes from Apache are being created and never destroyed. When the number of httpd processes reaches the maximum configured for the Apache instance, the web server stops responding.
After researching the base problem, we've found that the connection to the apps server, WebSphere, was not responding. The WebSphere process itself works, since the log still writes down information, but the connection pool to the apps server does not respond.
If anybody had this problem before and can give me some pointers here, I'd really appreciate it.
Thanks and regards.
The visible error is that httpd processes from Apache are being created and never destroyed. When the number of httpd processes reaches the maximum configured for the Apache instance, the web server stops responding.
After researching the base problem, we've found that the connection to the apps server, WebSphere, was not responding. The WebSphere process itself works, since the log still writes down information, but the connection pool to the apps server does not respond.
If anybody had this problem before and can give me some pointers here, I'd really appreciate it.
Thanks and regards.