Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP 401 error because of interrupted Tomcat?

Highlighted
sradtke
Regular Collector

HTTP 401 error because of interrupted Tomcat?

Hello,

does anyone has experience with PPM's embedded Apache Tomcat? We are running an PPM 7.1 SP10 cluster (two application server) with Microsoft IIS webserver on each node. The environment is running in Single Sign On mode.

We did alot of Performance test via loadrunner and got many http 401 errors.

We found these error messages in the webserver log:

[Fri Aug 28 10:48:11 2009] [5944:5968] [error] jk_ajp_common.c (1794): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=applserver1 failed
[Fri Aug 28 10:48:11 2009] [5944:5968] [error] jk_isapi_plugin.c (1073): service() failed


I believe, that the embedded tomcat from PPM is down and therefore the IIS can't connect to him. I think, the tomcat couldn't handle all connections.

Can anyone help me?

Segards
Sascha
12 REPLIES
Sascha Mohr
Esteemed Contributor

Re: HTTP 401 error because of interrupted Tomcat?

Hi. You are running an IIS on each of the PPM application servers?
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

We are running a Microsoft IIS webserver on each application server. We configured the cluster with the IIS webserver load balancing.
Sascha Mohr
Esteemed Contributor

Re: HTTP 401 error because of interrupted Tomcat?

That's not a very common setup I guess, but in theory this should work too.
The error message comes from the web server plugin ("jakarta"), probably you will need to revise the port configurations in the server.conf of PPM and the workers.properties of the web server plugin.
Example:
- Webserver listens on Port 80
- in workers.properties
workerer.server1.port is set to 8009
- in server.conf EXTERNAL_WEB_PORT is also set to 8009
- HTTP_PORT must be set to a free port, especially not port 80

Then test the setup. We assume here of course, that there are no restrictions by firewalls etc.
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

At the moment, we use the following configuration:

Application Node 1:
___________________

server.conf:
HTTP_PORT = 8081
EXTERNAL_WEB_PORT = 8080

workers.properties:
EXTERNAL_WEB_PORT = 8080


Application Node 2:
___________________

server.conf:
HTTP_PORT = 8081
EXTERNAL_WEB_PORT = 9085

workers.properties:
EXTERNAL_WEB_PORT = 9085
Sascha Mohr
Esteemed Contributor

Re: HTTP 401 error because of interrupted Tomcat?

And the IIS itself is on port 80?
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

Yes
Sascha Mohr
Esteemed Contributor

Re: HTTP 401 error because of interrupted Tomcat?

Sounds good. The error message implies that SSO is not involved here but the http errors do.
Normal user access to the dashboard works?
I don't know loadrunner very will. Does it also support the authentication method you use? Unfortunately, as soon as you activate SSO there is no longer direct access to the PPM nodes possible.
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

We couldn't reproduce the error without the loadrunner.

In sometimes the load balancer redirects our user request to the first application node but we also get an authentication pop-up for the second application node.

I'm confused seeing that, because i was redirected to the first node.

Regards
Sascha
Sascha Mohr
Esteemed Contributor

Re: HTTP 401 error because of interrupted Tomcat?

If the problems occur with loadrunner only I would still assume it is the SSO not being supported by loadrunner. Did you post the issue in the loadrunner forum too?
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

At the moment, i only posted the issue in this forum. But i will post it at the loadrunner forums aswell.
sradtke
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

Hello,

now we run another test and found out, that the application server 2 is the bottleneck.
The isapi.log shows alot of new error messages since the last test. But only the webserver of the application node 2.

Is seems, that the first application node works fine without any errors. Now we focus our research on the second application server.

Regards
Sascha
Vinod Jadhav
Regular Collector

Re: HTTP 401 error because of interrupted Tomcat?

Hi Sascha,

Have you got the solution to this problem? We are also facing the same issue and not getting answer.

Thanks
Vinod
//Add this to "OnDomLoad" event