Re: strange tomcat Behavior need urgent help.
This is a MySql problem. It shuts down connections if they have been idle for too long. You need a pool manager that takes care of this. Something like c3p0 will do the job. On Sun, 19 Dec 2004 12:28:09 + (GMT), Krishnakant Mane [EMAIL PROTECTED] wrote: hello all, I am Krishnakant Mane from India. I own a software firm and we generally implement our systems on linux and all open source servers like jakarta tomcat and apache server in particular. of late I have been facing a strange problem with tomcat. I am a tomcat 5 aka 5.0.25 user. I have deployed an database based application using mysql as the back-end. I use mysql jdbc driver to connect to the database. the application runs fine for a long time. I check it personally for the entire day. since our developers work on the server the entire day, I am sure there is that it works. but when we shut our office and come next day morning, the application does not respond. what could be the problem. it is strange to see that when the server is under some kind of a small work load it works absolutely fine. but when we don't touch it for the entire night the thing sympally does not work. does tomcat also require warm-up? haha. by the way, I have kept the jdbc (jar) library in the common/lib directory as all my applications are database based. is it the right thing to do? and lastly what steps should I take to avoid the above mentioned problem. one thing I will like to mention. when the application give problem in the morning, it responds with just the title and when it comes to the database connection it gets stuck I believe. but when I run some console app with the same jdbc driver it properly connects to the same database/table. and the application works fine when I reload again. Please provide some valuable feedback thanks Krishnakant. ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: strange tomcat Behavior need urgent help.
The pool manager built into Tomcat handles this just fine. Also ensure you have the latest drivers. Doug - Original Message - From: Eric Rotick [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, December 20, 2004 7:39 AM Subject: Re: strange tomcat Behavior need urgent help. This is a MySql problem. It shuts down connections if they have been idle for too long. You need a pool manager that takes care of this. Something like c3p0 will do the job. On Sun, 19 Dec 2004 12:28:09 + (GMT), Krishnakant Mane [EMAIL PROTECTED] wrote: hello all, I am Krishnakant Mane from India. I own a software firm and we generally implement our systems on linux and all open source servers like jakarta tomcat and apache server in particular. of late I have been facing a strange problem with tomcat. I am a tomcat 5 aka 5.0.25 user. I have deployed an database based application using mysql as the back-end. I use mysql jdbc driver to connect to the database. the application runs fine for a long time. I check it personally for the entire day. since our developers work on the server the entire day, I am sure there is that it works. but when we shut our office and come next day morning, the application does not respond. what could be the problem. it is strange to see that when the server is under some kind of a small work load it works absolutely fine. but when we don't touch it for the entire night the thing sympally does not work. does tomcat also require warm-up? haha. by the way, I have kept the jdbc (jar) library in the common/lib directory as all my applications are database based. is it the right thing to do? and lastly what steps should I take to avoid the above mentioned problem. one thing I will like to mention. when the application give problem in the morning, it responds with just the title and when it comes to the database connection it gets stuck I believe. but when I run some console app with the same jdbc driver it properly connects to the same database/table. and the application works fine when I reload again. Please provide some valuable feedback thanks Krishnakant. ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
strange tomcat Behavior need urgent help.
hello all, I am Krishnakant Mane from India. I own a software firm and we generally implement our systems on linux and all open source servers like jakarta tomcat and apache server in particular. of late I have been facing a strange problem with tomcat. I am a tomcat 5 aka 5.0.25 user. I have deployed an database based application using mysql as the back-end. I use mysql jdbc driver to connect to the database. the application runs fine for a long time. I check it personally for the entire day. since our developers work on the server the entire day, I am sure there is that it works. but when we shut our office and come next day morning, the application does not respond. what could be the problem. it is strange to see that when the server is under some kind of a small work load it works absolutely fine. but when we don't touch it for the entire night the thing sympally does not work. does tomcat also require warm-up? haha. by the way, I have kept the jdbc (jar) library in the common/lib directory as all my applications are database based. is it the right thing to do? and lastly what steps should I take to avoid the above mentioned problem. one thing I will like to mention. when the application give problem in the morning, it responds with just the title and when it comes to the database connection it gets stuck I believe. but when I run some console app with the same jdbc driver it properly connects to the same database/table. and the application works fine when I reload again. Please provide some valuable feedback thanks Krishnakant. ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: strange tomcat Behavior need urgent help.
Hi Krishnakant, I think there was a problem with MySQL connections after a certain amount of time. I am assume that you have defined a Datasource within TC and are using a connection pool for the connection. If not, I would highly recommend doing so, especially since your problem could be related to not having a connection pool. If you do have all of the above I would try adding the following parameters to your ressource -Original Message- From: Krishnakant Mane [mailto:[EMAIL PROTECTED] Sent: Sunday, December 19, 2004 1:28 PM To: [EMAIL PROTECTED] Subject: strange tomcat Behavior need urgent help. hello all, I am Krishnakant Mane from India. I own a software firm and we generally implement our systems on linux and all open source servers like jakarta tomcat and apache server in particular. of late I have been facing a strange problem with tomcat. I am a tomcat 5 aka 5.0.25 user. I have deployed an database based application using mysql as the back-end. I use mysql jdbc driver to connect to the database. the application runs fine for a long time. I check it personally for the entire day. since our developers work on the server the entire day, I am sure there is that it works. but when we shut our office and come next day morning, the application does not respond. what could be the problem. it is strange to see that when the server is under some kind of a small work load it works absolutely fine. but when we don't touch it for the entire night the thing sympally does not work. does tomcat also require warm-up? haha. by the way, I have kept the jdbc (jar) library in the common/lib directory as all my applications are database based. is it the right thing to do? and lastly what steps should I take to avoid the above mentioned problem. one thing I will like to mention. when the application give problem in the morning, it responds with just the title and when it comes to the database connection it gets stuck I believe. but when I run some console app with the same jdbc driver it properly connects to the same database/table. and the application works fine when I reload again. Please provide some valuable feedback thanks Krishnakant. ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: strange tomcat Behavior need urgent help.
SORRY, HERE IS THE FULL MAIL Hi Krishnakant, I think there was a problem with MySQL connections after a certain amount of time. I am assume that you have defined a Datasource within TC and are using a connection pool for the connection. If not, I would highly recommend doing so, especially since your problem could be related to not having a connection pool. If you do have all of the above I would try adding the following parameters to your ressource (within your applicationName.xml file) ResourceParams name=jdbc/yourJNDIname parameter nameurl/name valuejdbc:mysql://nameOfServer:port/databaseName?autoReconnect=true/value /parameter parameter namemaxIdle/name value15/value /parameter parameter namemaxActive/name value50/value /parameter parameter namedriverClassName/name valuecom.mysql.jdbc.Driver/value /parameter parameter namemaxWait/name value1/value /parameter parameter nameremoveAbandoned/name valuetrue/value /parameter /ResourceParams You will have to play around with the values provided above but these have worked for me so they might be a reasonable starting point. If this doesn't help, I would suggest searching -- http://lists.mysql.com/java. I think there must be plenty of posts related to your problem. HTH, Jan -Original Message- From: Krishnakant Mane [mailto:[EMAIL PROTECTED] Sent: Sunday, December 19, 2004 1:28 PM To: [EMAIL PROTECTED] Subject: strange tomcat Behavior need urgent help. hello all, I am Krishnakant Mane from India. I own a software firm and we generally implement our systems on linux and all open source servers like jakarta tomcat and apache server in particular. of late I have been facing a strange problem with tomcat. I am a tomcat 5 aka 5.0.25 user. I have deployed an database based application using mysql as the back-end. I use mysql jdbc driver to connect to the database. the application runs fine for a long time. I check it personally for the entire day. since our developers work on the server the entire day, I am sure there is that it works. but when we shut our office and come next day morning, the application does not respond. what could be the problem. it is strange to see that when the server is under some kind of a small work load it works absolutely fine. but when we don't touch it for the entire night the thing sympally does not work. does tomcat also require warm-up? haha. by the way, I have kept the jdbc (jar) library in the common/lib directory as all my applications are database based. is it the right thing to do? and lastly what steps should I take to avoid the above mentioned problem. one thing I will like to mention. when the application give problem in the morning, it responds with just the title and when it comes to the database connection it gets stuck I believe. but when I run some console app with the same jdbc driver it properly connects to the same database/table. and the application works fine when I reload again. Please provide some valuable feedback thanks Krishnakant. ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Strange tomcat behavior
Hi everybody on the list! We observed a strange tomcat behavior (tomcat 4.1.24) while running a servlet: Everything works fine some days or even weeks. Suddenly (and at random time) tomcat throws the following exceptions: 2003-10-08 11:44:48 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:484) This exception occurs some times. Suddenly tomcat throws another exception: 2003-10-08 11:46:44 CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at java.lang.String.charAt(String.java:509) at org.apache.tomcat.util.buf.ByteChunk.indexOf(ByteChunk.java:669) at org.apache.coyote.tomcat4.CoyoteAdapter.normalize(CoyoteAdapter.java:578) at org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:280) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:484) Note that there are no user defined classes in the stacktrace. What's the reason of this behavior? Regards Ralf * OptiSoft GmbHRalf Bechtel Pforzheimer Str. 68a mail : [EMAIL PROTECTED] D-75242 Neuhausenphone: +49 7234 9518-51 http://www.optisoft.de fax : +49 7234 9518-44 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange tomcat behavior
[EMAIL PROTECTED] wrote:
Hi everybody on the list!
We observed a strange tomcat behavior (tomcat 4.1.24) while running a servlet: Everything works fine some days or even weeks. Suddenly (and at random time) tomcat throws the following exceptions:
2003-10-08 11:44:48 CoyoteAdapter An exception or error occurred in the container
during the request processing
java.lang.NullPointerException
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:484)
This exception occurs some times. Suddenly tomcat throws another exception:
2003-10-08 11:46:44 CoyoteAdapter An exception or error occurred in the container
during the request processing
java.lang.NullPointerException
at java.lang.String.charAt(String.java:509)
at org.apache.tomcat.util.buf.ByteChunk.indexOf(ByteChunk.java:669)
at org.apache.coyote.tomcat4.CoyoteAdapter.normalize(CoyoteAdapter.java:578)
at
org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:280)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:484)
Note that there are no user defined classes in the stacktrace. What's the reason of this behavior?
The second one was weirder, so I looked into it:
For the TC 4.1.24 source:
CoyoteAdapter.java:578: index = uriBC.indexOf(/../, 0, 4, index);
For reference: ByteChunk.java:668: public int indexOf( String src, int
srcOff, int srcLen, int myOff ) {
ByteChunk.java:669: char first=src.charAt( srcOff );
If you get a NPE inside charAt on a constant String, I think it means
your VM has issues.
For the first one, the engine associated with the engine valve is null,
which can't happen either, but I can't demonstrate as easily that it's
not a Tomcat bug.
--
x
Rémy Maucherat
Senior Developer Consultant
JBoss Group (Europe) SàRL
x
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strange tomcat behavior
Howdy,
I recall having the charAt NPE -- it went away during an upgrade of the JDK (to 1.4.2)
and tomcat (to 4.1.27). At that time I also had them update all the Solaris OS
patches required by the JDK. So I don't know which was the deciding factor in the
charAt NPE you're getting, but doing all the updates should work ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 10:24 AM
To: Tomcat Users List
Subject: Re: Strange tomcat behavior
[EMAIL PROTECTED] wrote:
Hi everybody on the list!
We observed a strange tomcat behavior (tomcat 4.1.24) while running a
servlet: Everything works fine some days or even weeks. Suddenly (and at
random time) tomcat throws the following exceptions:
2003-10-08 11:44:48 CoyoteAdapter An exception or error occurred in the
container during the request processing
java.lang.NullPointerException
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav
a:164)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo
keNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConn
ection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja
va:619)
at java.lang.Thread.run(Thread.java:484)
This exception occurs some times. Suddenly tomcat throws another
exception:
2003-10-08 11:46:44 CoyoteAdapter An exception or error occurred in the
container during the request processing
java.lang.NullPointerException
at java.lang.String.charAt(String.java:509)
at org.apache.tomcat.util.buf.ByteChunk.indexOf(ByteChunk.java:669)
at
org.apache.coyote.tomcat4.CoyoteAdapter.normalize(CoyoteAdapter.java:578)
at
org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java
:280)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConn
ection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja
va:619)
at java.lang.Thread.run(Thread.java:484)
Note that there are no user defined classes in the stacktrace. What's
the reason of this behavior?
The second one was weirder, so I looked into it:
For the TC 4.1.24 source:
CoyoteAdapter.java:578: index = uriBC.indexOf(/../, 0, 4, index);
For reference: ByteChunk.java:668: public int indexOf( String src, int
srcOff, int srcLen, int myOff ) {
ByteChunk.java:669: char first=src.charAt( srcOff );
If you get a NPE inside charAt on a constant String, I think it means
your VM has issues.
For the first one, the engine associated with the engine valve is null,
which can't happen either, but I can't demonstrate as easily that it's
not a Tomcat bug.
--
x
Rémy Maucherat
Senior Developer Consultant
JBoss Group (Europe) SàRL
x
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat behavior
Hi Folks , I have a question Folks : Does Tomcat Processes become 0 at some point if Web Application is not accessed for a while. What has happened is twice in our environment that on a Weekend Morning around 2:00 AM Tomcat Processes became 0 and they later increased to 36 processes .I found out it through a small Script that checks for the number of Apache and Tomcat processes every Minute .I found the similar behavior for Apache Twice with Apache processes becoming 0 and then after a while number changing to 8 which is normal in our environment. My question is : Does Tomcat Shuts down and restarts itself at a certain regular interval like once in a month or so .If yes then ,is there any Configuration file in Tomcat from where this can be Controlled.The same question applies for Apache --if Apache shuts and restarts itself at a certain regular interval . Thanks in Advance Sameer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat behavior
for example on red hat 7.x, the log rotate script does HUP apache. you may have things like that going on. but you give us no system info. -jason On Thu, 16 Jan 2003, Mohbe, Sameer wrote: Hi Folks , I have a question Folks : Does Tomcat Processes become 0 at some point if Web Application is not accessed for a while. What has happened is twice in our environment that on a Weekend Morning around 2:00 AM Tomcat Processes became 0 and they later increased to 36 processes .I found out it through a small Script that checks for the number of Apache and Tomcat processes every Minute .I found the similar behavior for Apache Twice with Apache processes becoming 0 and then after a while number changing to 8 which is normal in our environment. My question is : Does Tomcat Shuts down and restarts itself at a certain regular interval like once in a month or so .If yes then ,is there any Configuration file in Tomcat from where this can be Controlled.The same question applies for Apache --if Apache shuts and restarts itself at a certain regular interval . Thanks in Advance Sameer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
old tomcat behavior?
is this an old tomcat behavior? if im logged in and my last page is page1.jsp and my session times out so im redirected to /login.jsp. problem is after logging in, it redirects me back to page1.jsp. i dont want it to be this way. is there a way to manually set the page to go to should be index.jsp? this sucks up when you have frames and u timed out. when u login instead of being showin with frames it will only show the page of the frame where u last did some events on it (clicking, etc) mark --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.401 / Virus Database: 226 - Release Date: 10/9/2002 -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Strange Tomcat behavior during authentification
Hi! I am developing an application using FORM-based authentification and JDBCReal from Tomcat 4.0.3 (and Tomcat 4.0.4 also checked). Two problems occure: 1. Authenticating with wrong role never allows to re-login again. When user tries to login with correct username/password, but not isUserInRole() to access requested resource then Tomcat returns 403 error code and you never can get back to login screen to relogin with the correct role (other username). Requesting the login URL directly and then submitting the data results in 404 error code: The requested resource (/j_security_check) is not available. 2. 400 error code: Ivalid direct reference to login page after logoff and session timeout. In my application when user is logged of he is redirected to the context root (exactly to the welcome file) URL, which results in a new redirect to the login screen. But if the session times out then logging in results in 400 error code. The user should strip the login.html from the URL manually and then try again to enter the application. So, the question is: am I doing something wrong, are there any workarounds or these are bugs in Tomcat and are fixed already (in which version?) or will be fixed soon? My config: - WinNT 4.0 - JDK 1.3.1 - Tomcat 4.0.3/4.0.4 (Antything else?) Thanks in advance. Regards, Konstantin Piroumian -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
