After I manually shutdown tomcat (shutdown.sh) the ajp socket seems
to stay open for an extended period of time. If I attempt to restart,
I get the following output in catalina.out. The problem is that ajp13
should be listening on 8889, but this port is never released, and for
some odd reason, it
/jdk1.5.0
_05/jre/lib/i386:/usr/local/jdk1.5.0_05/jre/../lib/i386
Fenlason, Josh wrote:
Take a look at this thread to fix this problem.
http://marc.theaimsgroup.com/?l=tomcat-userm=114062756728076w=2
,
Josh.
-Original Message-
From: Joey Geiger [mailto:[EMAIL PROTECTED]
Sent: Friday
].[hostname.com].[/] -
Loading Spring root WebApplicationContext
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 9:15 AM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.15 Context Reloading issue
From: Joey Geiger [mailto:[EMAIL
Oddly enough, the banks don't even care about this.
US Bank, for example, claims their login on the front page is secure and
has you enter your account data into a non https form. After the browser
sends the information, it then redirects to a secure(https) link.
I wrote them about this, and
I've done some further searching, and noticed that tomcat was also dumping
information into stdout. There is another log trace that might be helpful if
anyone else recognizes the problem. I'm of the belief that this is a bug of
some sort, but I don't know who to pass the information along to.
Session Listeners
http://pdf.coreservlets.com/CSAJSP-Chapter9.pdf
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 8:38 AM
To: Tomcat Users List
Subject: Logging session timeouts
Is there any way of trapping session timeouts, so I can
-
From: Joey Geiger [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 8:48 AM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
Session Listeners
http://pdf.coreservlets.com/CSAJSP-Chapter9.pdf
-Original Message-
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent
Here is the code I use, instead of a filter, I use a listener so I don't
have to worry about setting urls.
This part is in web.xml
listener
listener-classyourpackage.SessionListener/listener-class
/listener
The majority of this code was found online (and I think came from
coreservlets.com)
While the user can delete the cookie that is associated with the session,
the server will consider the session valid until it times out, as the user
is unable to end the session manually. If you add in a link/button that says
Remove my session from server and then have the application invalidate
case, the filter does a whole lot more, but I stripped it
down before posting it to only show the relevant section.
Tim
-Original Message-
From: Joey Geiger [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 12:27 PM
To: 'Tomcat Users List'
Subject: RE: Logging session timeouts
I've run into an issue with Tomcat 5.5.15 and the Context reloading. When I
change a file in my application, I have the context set to automatically
restart. This was working fine with 5.5.12, but there seems to be an issue
after I upgraded to 5.5.15.
The host is configured as:
Host
11 matches
Mail list logo