André Warnier wrote:
Hi.
Instead of POST-ing to the Apache server on port 80, what happens if
you try to send your POST firectly to Tomcat, at http://localhost:8080 ?
Can you send a logfile of /Tomcat/ after you try that ?
Or better : stop Tomcat, remove your webapp, clean the Tomcat logs,
re
André Warnier wrote:
Hi.
Instead of POST-ing to the Apache server on port 80, what happens if
you try to send your POST firectly to Tomcat, at http://localhost:8080 ?
Can you send a logfile of /Tomcat/ after you try that ?
Or better : stop Tomcat, remove your webapp, clean the Tomcat logs,
re
Caldarale, Charles R wrote:
From: Scott Carlson [mailto:scarl...@i2s.com]
Subject: Re: Ubuntu 8.10 GWT Apache2 Tomcat Servlet Problems
The majority of the forums always bring up web.xml
Which is appropriate, since yours is incorrect. Your URL pattern should be:
/MsgService
- Chuck
Caldarale, Charles R wrote:
From: Scott Carlson [mailto:scarl...@i2s.com]
Subject: Re: Ubuntu 8.10 GWT Apache2 Tomcat Servlet Problems
That was what I had originally, it has changed often due to
conflicting advice on forums. I did change it back to test.
Leave it as is, without
We've setup TC 7.0.32 with Clustering and Tomcat Container Managed
Authentication. HTTPSessions and SSOSessions are clustered across the
wire. With logging turned way up, I can see the synchronization and I can
see the sessions in the Tomcat Manager.
When I "kill -9" one of the tomcats, I'm aut
