HttpProcessor Problem - Starting background thread
Hi, My webapp was running fine for 2 days when suddenly, a static thread had stopped... this thread should be always alive I searched the logs but find only this entry 2004-04-16 13:43:41 HttpProcessor[8080][6] Starting background thread What does this mean? Please can any tell me the scenarios it could happen ?? Can i do some thing before or after this event is called, like pesisting the objects??? I m using Tomcat standalone running on port 8080. Linux + tomcat 4.0.4 + JDK 1.4 Thanks in advance, sudhakar Log server.xml below. NOTE: usually when i start/stop the thread i find these 2004-04-15 14:11:07 jsp: init 2004-04-15 14:11:07 StandardWrapper[/sfpsr:ssi]: Loading container servlet ssi 2004-04-15 14:11:07 ssi: init 2004-04-15 14:11:07 action: init 2004-04-15 14:11:08 Ajp13Connector[8007] Opening server socket on host IP address 127.0.0.1 2004-04-15 14:11:08 Ajp13Connector[8007] Starting background thread 2004-04-15 14:11:08 Ajp13Processor[8007][0] Starting background thread 2004-04-15 14:11:08 Ajp13Processor[8007][1] Starting background thread 2004-04-15 14:11:08 Ajp13Processor[8007][2] Starting background thread 2004-04-15 14:11:08 Ajp13Processor[8007][3] Starting background thread 2004-04-15 14:11:08 Ajp13Processor[8007][4] Starting background thread 2004-04-15 14:11:08 HttpConnector[8080] Starting background thread 2004-04-15 14:11:08 HttpProcessor[8080][0] Starting background thread 2004-04-15 14:11:08 HttpProcessor[8080][1] Starting background thread 2004-04-15 14:11:08 HttpProcessor[8080][2] Starting background thread 2004-04-15 14:11:08 HttpProcessor[8080][3] Starting background thread 2004-04-15 14:11:08 HttpProcessor[8080][4] Starting background thread 2004-04-15 14:11:10 jsp: init server.xml Server port=8005 shutdown=SHUTDOWN debug=0 Service name=Agent8005 Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8007 minProcessors=5 maxProcessors=100 acceptCount=10 debug=0 address=127.0.0.1 / Connector className=org.apache.catalina.connector.http.HttpConnector port=8080 minProcessors=5 maxProcessors=200 enableLookups=false redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=6/ Engine jvmRoute=a8050 name=Agent8050 defaultHost=localhost debug=0 Manager className=org.apache.catalina.session.PersistentManager debug=0 saveOnRestart=true maxActiveSessions=-1 minIdleSwap=-1 maxIdleSwap=-1 maxIdleBackup=-1 Store className=org.apache.catalina.session.FileStore/ /Manager Logger className=org.apache.catalina.logger.FileLogger prefix=JVM8050. suffix=.txt timestamp=true/ Realm className=org.apache.catalina.realm.MemoryRealm / Host name=localhost debug=0 appBase=webapps unpackWARs=true Context path=/TMAgent docBase=TMAgent debug=0 privileged=true Valve className=org.apache.catalina.valves.RemoteAddrValve allow=127.0.0.1/ /Context Context path=/manager docBase=manager debug=0 privileged=true /Context /Host /Engine /Service /Server This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: HttpProcessor Problem - Starting background thread
thanks Yoav.. Actually The Thread hang was a DB problem and i confused with this log msg.. sudhakar -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, April 16, 2004 6:28 PM To: Tomcat Users List Subject: RE: HttpProcessor Problem - Starting background thread Hi, 2004-04-16 13:43:41 HttpProcessor[8080][6] Starting background thread What does this mean? Please can any tell me the scenarios it could happen It means there was sufficient concurrent load on the server that it needed to start another processing threads, and that less than the maximum number of threads for connector were already started, so it went ahead and started another. Can i do some thing before or after this event is called, like pesisting the objects??? Only if you want to write some very tomcat-specific code, and you don't. This is not a highly significant event in terms of resources, just another thread, and the 6th (or 7th) one at that so it's not even a high load scenario. Yoav Shapira 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] This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Objects using thread on Start/Stop of Tomcat
Thanks Yoav, sudhakar -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 6:24 PM To: Tomcat Users List Subject: RE: Objects using thread on Start/Stop of Tomcat Hi, It's funny that you wrote your own thread manager and have to ask this question. No, tomcat cannot destroy all your threads and objects referred to from these threads. Tomcat can only destroy daemon threads for you. You need to take care of the rest by yourself. A ServletContextListener's contextDestroyed method is an excellent place to do this: shut down your thread manager and all your threads, otherwise tomcat's JVM process will not die. Yoav Shapira Millennium Research Informatics -Original Message- From: Namasivayam, Sudhakar (Cognizant) [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 2:10 AM To: Tomcat Users List Subject: Objects using thread on Start/Stop of Tomcat hi all, I have a Thread mgr which will create a thread. No if i Start and Stop the Tomcat, The older mgr object seems to be still in the JVM and this causes a problem because a new mgr is created and i have two copies of threads running simultaneously.. Can any one tell me whether all objects will be destroyed if i do start and stop of tomcat? Should i do anything in the Context Destroyed method od context listener? The older object is null in the context destroyed but the thread seems to be alive? Configuration : Linux + tomcat 4.0.4 + JDK 1.4 thanks in advance sudhakar 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] This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Objects using thread on Start/Stop of Tomcat
hi all, I have a Thread mgr which will create a thread. No if i Start and Stop the Tomcat, The older mgr object seems to be still in the JVM and this causes a problem because a new mgr is created and i have two copies of threads running simultaneously.. Can any one tell me whether all objects will be destroyed if i do start and stop of tomcat? Should i do anything in the Context Destroyed method od context listener? The older object is null in the context destroyed but the thread seems to be alive? Configuration : Linux + tomcat 4.0.4 + JDK 1.4 thanks in advance sudhakar This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts 1.1 +Tomcat 4.0.4 -- RequestProcessor - Exception
Hi, No luck in that mailing list :( May be i thought this might have to do some thing with tomcat... I am using the default RequestPrcessor only. I m using the default package of struts! Thanks, sudhakar -Original Message- From: Adrian Lanning [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 7:40 PM To: Tomcat Users List Subject: Re: Struts 1.1 +Tomcat 4.0.4 -- RequestProcessor - Exception Hi, You might have more luck with this in the struts-user mailing list. Are you using a custom request processor? If so did you extend org.apache.struts.action.RequestProcessor or org.apache.struts.tiles.TilesRequestProcessor? Adrian - Original Message - From: Namasivayam, Sudhakar (Cognizant) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 12:27 AM Subject: Struts 1.1 +Tomcat 4.0.4 -- RequestProcessor - Exception Hi all, This error happens only in Tomcat 4.0 and not Tomcat 5.0.19 in Linux 7.0. Am i missing any library files? I have put the latest library files. I did find similar mail in the struts archives but no response to that... Or is this the problem with my manager webapp? I do not get Class cast exception message when i stop and start the webapp. Only when a action is invoked this exception occurs!! Both the times( stop-start and action.do ) it is trying to get the same RequestProcessor object but the second time it throws an error. If i insert a try catch block in the ActionServlet class,it works fine... Can any one explain me why this exception occurs? I did verify that getServletContext().getAttribute(key); in ActionServlet.java:855 returns a RequestProcessor object. Pls find the log and my server.xml at the end of the mail. Thanks in advance, Sudhakar 2004-03-22 15:18:09 Manager: start: Starting web application at '/sfpsr2' 2004-03-22 15:18:09 StandardHost[localhost]: standardHost.start /sfpsr2 2004-03-22 15:18:09 StandardContext[/sfpsr2]: Configuring ProxyDirContext [EMAIL PROTECTED] 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploying class repositories to work directory /usr/local/tomcat4.0.4/work/Agent8050/localhost/sfpsr2 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/activation.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/activation.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/classes12.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/classes12.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-beanutils.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-beanutils.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-collections.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-collections.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-dbcp-1.1.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-dbcp-1.1.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-digester.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-digester.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-fileupload.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-fileupload.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-lang.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-lang.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-logging.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-logging.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-logging1.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-logging1.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-validator.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-validator.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/jakarta-oro.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/jakarta-oro.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/log4j-1.2.8.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/log4j-1.2.8.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/mail.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/mail.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/servlet.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/servlet.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/struts.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/struts.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/struts2.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/struts2.jar 2004-03-22 15:18:09 StandardManager[/sfpsr2]: Seeding random number generator class java.security.SecureRandom 2004-03-22 15:18:09 StandardManager[/sfpsr2]: Seeding of random number generator has
Struts 1.1 +Tomcat 4.0.4 -- RequestProcessor - Exception
Hi all, This error happens only in Tomcat 4.0 and not Tomcat 5.0.19 in Linux 7.0. Am i missing any library files? I have put the latest library files. I did find similar mail in the struts archives but no response to that... Or is this the problem with my manager webapp? I do not get Class cast exception message when i stop and start the webapp. Only when a action is invoked this exception occurs!! Both the times( stop-start and action.do ) it is trying to get the same RequestProcessor object but the second time it throws an error. If i insert a try catch block in the ActionServlet class,it works fine... Can any one explain me why this exception occurs? I did verify that getServletContext().getAttribute(key); in ActionServlet.java:855 returns a RequestProcessor object. Pls find the log and my server.xml at the end of the mail. Thanks in advance, Sudhakar 2004-03-22 15:18:09 Manager: start: Starting web application at '/sfpsr2' 2004-03-22 15:18:09 StandardHost[localhost]: standardHost.start /sfpsr2 2004-03-22 15:18:09 StandardContext[/sfpsr2]: Configuring ProxyDirContext [EMAIL PROTECTED] 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploying class repositories to work directory /usr/local/tomcat4.0.4/work/Agent8050/localhost/sfpsr2 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/activation.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/activation.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/classes12.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/classes12.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-beanutils.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-beanutils.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-collections.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-collections.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-dbcp-1.1.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-dbcp-1.1.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-digester.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-digester.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-fileupload.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-fileupload.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-lang.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-lang.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-logging.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-logging.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-logging1.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-logging1.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/commons-validator.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/commons-validator.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/jakarta-oro.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/jakarta-oro.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/log4j-1.2.8.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/log4j-1.2.8.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/mail.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/mail.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/servlet.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/servlet.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/struts.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/struts.jar 2004-03-22 15:18:09 WebappLoader[/sfpsr2]: Deploy JAR /WEB-INF/lib/struts2.jar to /usr/local/tomcat4.0.4/webapps/sfpsr2/WEB-INF/lib/struts2.jar 2004-03-22 15:18:09 StandardManager[/sfpsr2]: Seeding random number generator class java.security.SecureRandom 2004-03-22 15:18:09 StandardManager[/sfpsr2]: Seeding of random number generator has been completed 2004-03-22 15:18:10 ContextConfig[/sfpsr2]: Added certificates - request attribute Valve 2004-03-22 15:18:10 Initializing application variables 2004-03-22 15:18:11 StandardWrapper[/sfpsr2:default]: Loading container servlet default 2004-03-22 15:18:11 default: init 2004-03-22 15:18:11 jsp: init 2004-03-22 15:18:12 StandardWrapper[/sfpsr2:ssi]: Loading container servlet ssi 2004-03-22 15:18:12 ssi: init 2004-03-22 15:18:12 action: init 2004-03-22 15:18:13 Manager: list: Listing contexts for virtual host 'localhost' 2004-03-22 15:19:09 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception java.lang.ClassCastException at org.apache.struts.action.ActionServlet.getRequestProcessor(ActionServlet.java:855)
java.lang.IllegalStateException: zip file closed
Hi all, I deployed my webapp using the war file biult using ant 1.6. The webapp is deployed and works well. But when i stop and atart again through the manager I get the exception Zip file closed error. But removing and installing again works well... What could be posssible cause??? I dont get this error if i unpack the war and deploy. But tomcat 4.0.4 under linux (jdk 1.4) does not unpack by default but creates a context. Reload also works well. Is there any way to unpack the war by default This issue does not arise in tomcat 5.0. But i need to use 4.0 :( Config : tomcat 4.0.4 ,Struts 1.1, jdk1.4 Thanks in advance, sudhakar java.lang.IllegalStateException: standardHost.start /sfpsr3: LifecycleException: start: : java.lang.IllegalStateException: zip file closed at org.apache.catalina.core.StandardHost.start(StandardHost.java:855) at org.apache.catalina.servlets.HTMLManagerServlet.start(HTMLManagerServlet.java:375) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:534) This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
