tomcat connectionpooling/broken pipe
Hi Is the tomcat connection pooling reliable. We are configuring database properties in server.xml and using the DataSource to lookup the jdbc datasource and get the connection. If in case the database goes down and later it is up, will the tomcat recreate the connections in the pool as the previous connections of pool will be stale. Does tomcat connection pooling has this feature. Though the database is up, we are sometimes noticing the 'broken pipe' error in the log file, when does this error is thrown. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JK2/tomcat 4.1.18 - broken pipe problem
Thx, Bill! But how do I get rid of them in my catalina.out log file ?! Should I set file logging in the worker2.properties ?! jk2.properties ?! Something :-) /Jesper Birch The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
I thought this could never be a problem(user htiing stop button), as I alreday mailed, I got it solved by relpacing sun jvm with ibm jvm, But I got it on redhat linux, but you are on solaris right, So what I am thinking is to think this problem in different dimension, This is just my suggestion -Original Message- From: Jesper Birch [mailto:[EMAIL PROTECTED]] Sent: Fri 1/3/2003 6:58 AM To: [EMAIL PROTECTED] Cc: Subject:Re: JK2/tomcat 4.1.18 - broken pipe problem Thx, Bill! But how do I get rid of them in my catalina.out log file ?! Should I set file logging in the worker2.properties ?! jk2.properties ?! Something :-) /Jesper Birch The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK2/tomcat 4.1.18 - broken pipe problem
Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK2/tomcat 4.1.18 - broken pipe problem
Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
Even I too got the same problem with configuraion of apache 2.0.40, tomcat 4.0.4 and j2sdk1.4.1(sun jvm) on redhat 7.3 but when I replaced sun jvm with ibm jvm, surprisingly I didn't get this problem, I am not sure here but what I thought is sun jvm can't support green threads on redhat linux but supports only native threads where as ibm jvm can support green threads on linux machines Thks, -Venkat -Original Message- From: Jesper Birch [mailto:[EMAIL PROTECTED]] Sent: Thu 1/2/2003 6:01 AM To: [EMAIL PROTECTED] Cc: Subject:JK2/tomcat 4.1.18 - broken pipe problem Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372)at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] winmail.dat-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JK2/tomcat 4.1.18 - broken pipe problem
Hi Thx for the suggestion... I forgot to write that I have the problem on Solaris 7... /Jesper Birch -Original Message- Even I too got the same problem with configuraion of apache 2.0.40, tomcat 4.0.4 and j2sdk1.4.1(sun jvm) on redhat 7.3 but when I replaced sun jvm with ibm jvm, surprisingly I didn't get this problem, I am not sure here but what I thought is sun jvm can't support green threads on redhat linux but supports only native threads where as ibm jvm can support green threads on linux machines Thks, -Venkat -Original Message- Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.j ava:500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users on my site has any problems when it appears. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! Or it should be in that way ?! :-) Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JK2/tomcat 4.1.18 - broken pipe problem
The most common reason for this is that the user has hit the stop button in the browser before the page has been fully loaded. The AJP13 protocol (currently) doesn't support out-of-band messages to notify Tomcat of this fact, so mod_jk(2) simply drops the connection to Tomcat instead. Jesper Birch [EMAIL PROTECTED] wrote in message 1041497967.27623.14.camel@wbirch">news:1041497967.27623.14.camel@wbirch... Hi, I have setup a environment with Apache 2.0.43, Tomcat 4.1.18 and JK2 connector. Everything seems to work fine, except an error message I get time to time in my logs: 2003-01-02 05:55:56,681 [Thread-49] ERROR org.apache.jk.server.JkCoyoteHandler - Error in action code java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:435) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:627)at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.coyote.tomcat4.OutputBuffer.close(OutputBuffer.java:326) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteResponse.java: 500) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:224) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:632)at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:590) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:707) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:530) at java.lang.Thread.run(Thread.java:536) It does not seems like the users of my site has any problems when using it. So I am not sure when exactly this is happening. Can somebody explain for me the condition for when this should happen - so I can look into this error, or maybe somebody has an idea to what the problem can be ?! I have built JK2 from the 4.1.18 connectors package.. Thanks Jesper Birch -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat and broken pipe
Hello! I have a problem with the connection between tomcat and oracle. When I open a connection to the DB once at the beginning, then save it for later. When I come back in several hours, the DB has dropped the connection, so when I try to use it, I get that message, can anyone help me? I don't know what it happens: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:292) at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:31 3) at es.terra.mobile.smsinvertia.Servidor.insertaRegistro(Servidor.java:38) at es.terra.mobile.smsinvertia.Cliente2Servlet.service(Cliente2Servlet.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) 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.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) 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:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) Thanks, Raquel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
SV: tomcat and broken pipe
Hi This means that the database has auto-disconnected the connection. In many DB's this is configurable. Otherwise you have to deal with it programmatically. Never leave a connection open after you have finished work on it. Hermod -Opprinnelig melding- Fra: Raquel R.L. [mailto:[EMAIL PROTECTED]] Sendt: 25. juni 2002 12:26 Til: [EMAIL PROTECTED] Emne: tomcat and broken pipe Hello! I have a problem with the connection between tomcat and oracle. When I open a connection to the DB once at the beginning, then save it for later. When I come back in several hours, the DB has dropped the connection, so when I try to use it, I get that message, can anyone help me? I don't know what it happens: java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleStatement.init(OracleStatement.java:292) at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.jav a:31 3) at es.terra.mobile.smsinvertia.Servidor.insertaRegistro(Servidor.java:38) at es.terra.mobile.smsinvertia.Cliente2Servlet.service(Cliente2Servlet.java :50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tion FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.ja va:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.ja va:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.ja va:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:234 3) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja va:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 72) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) Thanks, Raquel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that DnB cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]