DO NOT REPLY [Bug 13093] - Compliance Issue - NPE not thrown if a null reference is passed to PageContext.handlePageException(Exception) or PageContext.handlePageException(Throwable).
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=13093. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=13093 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36470] New: - Connections not release on encountering exception.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36470. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36470 Summary: Connections not release on encountering exception. Product: Tomcat 5 Version: 5.0.28 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Connector:AJP AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When a valve throws an unhandled exception during run time, it seems like the connector does not release the socket immediately. If a number of these instances occur, we get into a state where, unless the socket timeout is not reached, it is not possible to get another connection to the web server. The server starts returning HTTP 503 in this case. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27104] - got an exception when testing a simple cluster app
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27104. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27104 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | --- Additional Comments From [EMAIL PROTECTED] 2005-08-25 08:12 --- We are getting this issue on our servers at the moment. We are using Tomcat 5.0.28 and I have seen this issue under Linux and Windows. Our site is constantly causing this issue, and the only solution is to get the customer to shutdown all of their browsers to disconnect from the session then start again. It seems that the DeltaSession gets lost and then when the replication happens it has some sort of internal error. Any ideas on a solution for this one? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 5.5.10 cluster exception
Dennis wrote: I'm working with the cvs tagged 5.5.10 version of tomcat to check out some clustering fixes. When I bring a 2nd server into the pool, I get this exception repeated every time an mcast packet is received: ==CUT== java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Ljava.lang.Object;ILjava.lang.Object;II)V(Unknown Source) at org.apache.catalina.cluster.mcast.McastMember.getMember(McastMember.java:181) at org.apache.catalina.cluster.mcast.McastServiceImpl.receive(McastServiceImpl.java:209) at org.apache.catalina.cluster.mcast.McastServiceImpl$ReceiverThread.run(McastServiceImpl.java:253) ==END CUT== Here are the relevant lines of code from McastMember.java: ==CUT== byte[] domaind = new byte[dlen]; System.arraycopy(data, nlen + 24, domaind, 0, domaind.length); ==END CUT== I added some debugging to figure out the length of the data. The exception occurs because data.length is 23. Obviously 23+24 is going to throw an ArrayIndexOBE. My question is.. is there a configuration thing that is causing data to be sent to be less than the desired length? It appears the data is not coming in in the format expected. Thoughts? Your post is OT on this mailing list, but I thought I would play a little with the clustering. This works for me, with this config: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=true notifyListenersOnReplication=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.0.4 mcastPort=45564 mcastFrequency=500 mcastClusterDomain=dev mcastDropTime=3000/ Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=4002 tcpSelectorTimeout=100 tcpThreadCount=6/ Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=pooled ackTimeout=15000/ Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;/ ClusterListener className=org.apache.catalina.cluster.session.ClusterSessionListener/ /Cluster The domain feature for membership is new in this release (which caused the data packets sent to change). I recommend trying tomcat-user, or filing a bug if you can give working instructions on how to reproduce the problem. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
5.5.10 cluster exception
I'm working with the cvs tagged 5.5.10 version of tomcat to check out some clustering fixes. When I bring a 2nd server into the pool, I get this exception repeated every time an mcast packet is received: ==CUT== java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Ljava.lang.Object;ILjava.lang.Object;II)V(Unknown Source) at org.apache.catalina.cluster.mcast.McastMember.getMember(McastMember.java:181) at org.apache.catalina.cluster.mcast.McastServiceImpl.receive(McastServiceImpl.java:209) at org.apache.catalina.cluster.mcast.McastServiceImpl$ReceiverThread.run(McastServiceImpl.java:253) ==END CUT== Here are the relevant lines of code from McastMember.java: ==CUT== byte[] domaind = new byte[dlen]; System.arraycopy(data, nlen + 24, domaind, 0, domaind.length); ==END CUT== I added some debugging to figure out the length of the data. The exception occurs because data.length is 23. Obviously 23+24 is going to throw an ArrayIndexOBE. My question is.. is there a configuration thing that is causing data to be sent to be less than the desired length? It appears the data is not coming in in the format expected. Thoughts? Thanks Dennis Here is the config I'm using on each server for the cluster. ==cluster config== Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=false notifyListenersOnReplication=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=228.0.1.2 mcastPort=45564 mcastFrequency=500 mcastClusterDomain=dev mcastDropTime=3000/ Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=192.168.1.27 tcpListenPort=8010 tcpSelectorTimeout=100 tcpThreadCount=3/ Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=pooled ackTimeout=15000/ Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;/ !-- Deployer className=org.apache.catalina.cluster.deploy.FarmWarDeployer tempDir=/tmp/war-temp/ deployDir=/tmp/war-deploy/ watchDir=/tmp/war-listen/ watchEnabled=false/ -- ClusterListener className=org.apache.catalina.cluster.session.ClusterSessionListener/ /Cluster ==END cluster config== - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26436] - Jasper generates code weak against exception in doAfterBody()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=26436. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=26436 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-07-26 22:49 --- *** This bug has been marked as a duplicate of 18778 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 [EMAIL PROTECTED] changed: What|Removed |Added Severity|minor |trivial Priority|P3 |P5 --- Additional Comments From [EMAIL PROTECTED] 2005-07-25 11:13 --- OK. My application in not important. Other J2EE application servers usually throws SecurityException for directory access from asynch Threads started into init() or service() method call. Threre is no difference between servlet.init() and servlet.service(...) permission. I don't see difference in J2EE specification for servlet.service(...) and servlet.init() permission. @see http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf Page 87: J2EE.6.2 Java 2 Platform, Standard Edition (J2SE) Requirements It's a trivial problem. Thanks for your effort into developing Tomcat. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | Version|5.0.12 |5.5.9 --- Additional Comments From [EMAIL PROTECTED] 2005-07-22 11:23 --- (In reply to comment #8) Assuming problem did go away, since no response given by original poster. Problem is go away. But the bug is exist in Tomcat 5.0.28. Also the bug is exist in Tomcat 5.5.9. But it is not so critical. 1. JSP is used. 2. Deploy application. 3. Open 1.jsp. We receive a IOException instead of Exception from 2.jsp. 4. Open 3.jsp. We receive content of 3.jsp. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-22 11:42 --- Please do not reopen the report. This issue will not be fixed in 5.0.28 (obviously), and does not exist in 5.5.x code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-07-22 12:28 --- (In reply to comment #10) Please do not reopen the report. This issue will not be fixed in 5.0.28 (obviously), and does not exist in 5.5.x code. Sorry. Tomcat 5.5.9 is not contan this bug. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 --- Additional Comments From [EMAIL PROTECTED] 2005-07-22 16:22 --- Dario, I understand that you need additional permissions for your application becasue you're doing a DataSource creation in the initialization. But I wonder if, instead of changing the policy file that comes with Tomcat, we should simply document this. I'm very hesitant to put DBCP-specific permissions in the default Tomcat policy file. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-21 23:27 --- Assuming problem did go away, since no response given by original poster. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35798] New: - Null Pointer Exception in InternalOutputBuffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35798. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35798 Summary: Null Pointer Exception in InternalOutputBuffer Product: Tomcat 5 Version: 5.5.9 Platform: PC OS/Version: other Status: NEW Severity: major Priority: P2 Component: Connector:HTTP AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] When the servlet output stream is pooled for future use, any writes followed with a flush to the output stream (obtained from the pool) are causing null pointer exceptions. * Same problem exists with PrintWriter. * The writes+flush to the output stream are not happening on the thread that received the initial service request. * There is a server listening on the other side of HTTP socket. * Is the original service thread cleaning up the output stream? Platform : Windows XP PRofessional Java Version : jdk 1.5.0_04 Apache Tomcat Version 5.5.9 $Id: RELEASE-NOTES,v 1.25 2005/01/19 20:30:26 remm Exp $ -stack trace- java.lang.NullPointerException at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:747) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:403) at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:305) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:978) at org.apache.coyote.Response.action(Response.java:182) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:322) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293) at org.apache.catalina.connector.CoyoteWriter.flush(CoyoteWriter.java:82) at com.xxx.ClientConnectionManager._writeToConnection(ClientConnectionManager.java:346) at java.lang.Thread.run(Thread.java:595) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35798] - Null Pointer Exception in InternalOutputBuffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35798. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35798 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2005-07-19 21:30 --- Need a war file to reproduce. When the servlet output stream is pooled for future use seems rather sketchy. It seems like a misuse of the OutputStream at the when it is no longer valid which causes the error. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35798] - Null Pointer Exception in InternalOutputBuffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35798. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35798 --- Additional Comments From [EMAIL PROTECTED] 2005-07-19 21:38 --- (In reply to comment #1) thx for the quick reply. Need a war file to reproduce. Ok. I will try sending a war file. When the servlet output stream is pooled for future use seems rather sketchy. It seems like a misuse of the OutputStream at the when it is no longer valid which causes the error. Is the output stream cleaned up by the thread servicing the original request? If that is the case i can't reuse the stream for future use. Didn't expect a NPE. If that is the case, please close the bug. I will try figure out a workaround. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35798] - Null Pointer Exception in InternalOutputBuffer
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35798. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35798 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-19 21:45 --- An OutputStream only lasts (at most) as long as the HttpServletResponse. In other words, the life of the request. Once the reponse has been sent to the request has been sent (Servlet.service is finished) - then the OutputStream is invalid. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35650] New: - ApplicationDispatcher[] Servlet.service() jasper exception and 404 error
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35650. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35650 Summary: ApplicationDispatcher[] Servlet.service() jasper exception and 404 error Product: Tomcat 4 Version: 4.1.30 Platform: Sun OS/Version: Solaris Status: NEW Severity: major Priority: P1 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] I am getting 404 error when I access the jsp page. When I look in to the logs I see the following exception. This is only happening sometimes and when we restart the server we are able to access the jsp page.We are using tomcat 4.1.30 version runing JAVA 1.4.1. 2005-07-07 10:02:26 ApplicationDispatcher[] Servlet.service() for servlet jsp th rew exception javax.servlet.ServletException: /ehs/environmental/kalamazoo.jsp at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:239) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2 95) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary .java:822) at org.apache.jsp.framework_jsp._jspService(framework_jsp.java:206) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2 95) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java: 2422) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche rValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:163) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex t.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav a:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:19 9) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ssConnection
DO NOT REPLY [Bug 35650] - ApplicationDispatcher[] Servlet.service() jasper exception and 404 error
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35650. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35650 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-07-08 00:07 --- An upgrade to 4.1.31+ should fix this. *** This bug has been marked as a duplicate of 16113 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29641] - Socket exception hangs tomcat
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29641. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29641 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-07-01 21:59 --- That it works on win2k but not on win2003 is even more indication that this is not a Tomcat bug. Please do as Yoav suggested and use the tomcat-user mailing list. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29641] - Socket exception hangs tomcat
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29641. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29641 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2005-06-26 01:29 --- I am having the same problem. We have tried this on many different machines but this problem always happens on Windows 2003. We are running axis webservices which run just fine on Win 2000 but fail as soon as we move to Windows 2003. Tried 5.0.25 5.0.27 5.0.30 and other versions; no luck :( This problem happens when the server has been sitting idle for a long time eg. overnight, the problem happens and a particular context completey freezes. (In reply to comment #1) Please discuss and debug on the mailing list first. The probabiliy of this being a tomcat bug is slim. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23325] - displaying data source for a context resource results in exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=23325. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=23325 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2005-06-11 17:53 --- This works for me. Please follow up on Tomcat user if you are still experiencing problems. A few things to note are: - In 4.1.x a context.xml in META-INF is only used by the ManagerServlet during deployment - a resource-ref in web.xml that refers to a resource that does not exist will cause an error that looks like this. I have improved the error message when this occurs so it is easier to see which resource is not properly defined. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-10 08:28 --- Check bug# 33810. Try with 5.0.30 version and see if your problem goes away. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:26 --- Created an attachment (id=15242) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=15242action=view) 1.jsp -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:26 --- Created an attachment (id=15244) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=15244action=view) 3.jsp -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:30 --- Necessary conditions: 1. Using custom errorPage 2. Using custom tags, which returned EVAL_BODY_BUFFERED from doStartTag(). 3. Using tag jsp:include. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:27 --- Created an attachment (id=15245) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=15245action=view) error.jsp -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] New: - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 Summary: Stream closed exception Product: Tomcat 5 Version: 5.0.12 Platform: PC OS/Version: Windows XP Status: NEW Keywords: ErrorMessage Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Sorry for my bad English. Sources: 1. $Header: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/ runtime/PageContextImpl.java,v 1.52 2003/09/02 21:39:59 remm Exp $ $Revision: 1.52 $ $Date: 2003/09/02 21:39:59 $ 2. $Header: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/ catalina/core/ApplicationDispatcher.java,v 1.26 2003/09/12 17:04:12 remm Exp $ $Revision: 1.26 $ $Date: 2003/09/12 17:04:12 $ Steps To Reproduce: 1. Create four JSP: - - 1.jsp - %@ page import=java.util.Vector% %@ page errorPage=error.jsp % %@ taglib prefix=logic uri=/WEB-INF/tlds/struts-logic.tld % CONTENT PAGE 1 % // SOME COLLECTION Vector someCollection1 = new Vector(1); someCollection1.add(some value); % %-- Some EVAL_BODY_BUFFERED tag --% logic:iterate id=some_id_1 collection=%= someCollection1 % jsp:include page=2.jsp / /logic:iterate CONTENT PAGE 1 - - 2.jsp - %@ page import=java.util.Vector% %@ page errorPage=error.jsp % %@ taglib prefix=logic uri=/WEB-INF/tlds/struts-logic.tld % CONTENT PAGE 2 % Vector someCollection2 = new Vector(1); someCollection2.add(some value); % %-- Some EVAL_BODY_BUFFERED tag --% logic:iterate id=some_id_2 collection=%= someCollection2 % % // Some throwable statment if(request.getParameter(not exist parameter) == null) throw new Exception(); %/logic:iterate CONTENT PAGE 2 - - 3.jsp - %@ page import=java.util.Vector% %@ taglib prefix=logic uri=/WEB-INF/tlds/struts-logic.tld % % Vector someCollection3 = new Vector(1); someCollection3.add(some value); % %-- Some EVAL_BODY_BUFFERED tag --% logic:iterate id=some_id_3 collection=%= someCollection3 % CONTENT PAGE 3 /logic:iterate - --- error.jsp --- %@ page import=java.io.PrintWriter% %@ page isErrorPage=true % pre % PrintWriter pw; pw = new PrintWriter(out); Exception exc; exc = pageContext.getException(); if(exc != null) exc.printStackTrace(pw); % /pre - 2. Deploy application. 3. Open 1.jsp. We receive a IOException instead of Exception from 2.jsp. 3. Open 3.jsp. We receive a IOException though should not receive exception. WHY: When thrown wxceptoin on 2.jsp into ApplicationDispatcher in 465 line was closes writer. Stack trace: org.apache.jasper.catalina.core.ApplicationDispatcher.doForward():465 org.apache.jasper.catalina.core.ApplicationDispatcher.forward():359 org.apache.jasper.runtime.PageContextImpl.forward():543 org.apache.jasper.runtime.PageContextImpl.handlePageException():633 org.apache.jsp._2_jsp._jspService(): if (pageContext != null) pageContext. handlePageException(t); Later at use EVAL_BODY_BUFFERED tags called method pushBody, which returns closed writer. This is reason of IOExceptions. Closed writer - is outs[depth] from PageContextImpl. Possible, condition into PageContextImpl.pushBody in line 557 must be: if (depth = outs.length || IS_CLOSED(outs[depth])), instead of if (depth = outs.length). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:26 --- Created an attachment (id=15243) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=15243action=view) 2.jsp -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 35156] - Stream closed exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35156 --- Additional Comments From [EMAIL PROTECTED] 2005-06-01 14:32 --- IOEcxeption stack trace: java.io.IOException: Stream closed at org.apache.jasper.runtime.BodyContentImpl.ensureOpen(BodyContentImpl.java: 624) at org.apache.jasper.runtime.BodyContentImpl.write(BodyContentImpl.java:179) at org.apache.jasper.runtime.BodyContentImpl.write(BodyContentImpl.java:196) at org.apache.jsp._1_jsp._jspService(_1_jsp.java:79) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: 210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain. internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain. doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. java:256) at org.apache.catalina.core.StandardValveContext. invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563) at org.apache.catalina.core.StandardContextValve. invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. java:199) at org.apache.catalina.core.StandardValveContext. invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:195) at org.apache.catalina.core.StandardValveContext. invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext. invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java: 156) at org.apache.catalina.core.StandardValveContext. invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:563) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:209) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:670) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler. processConnection(Http11Protocol.java:517) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:575) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool. java:666) at java.lang.Thread.run(Thread.java:534) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34513] - jsp exception handling
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34513 --- Additional Comments From [EMAIL PROTECTED] 2005-05-05 02:25 --- Maybe some misunderstanding. What I feel wierd about is not the JspWriter's exception(caused by the commited response) itself. I think there's something could be done under such a jsp exception(eg. output to the tomcat log). I think that may be helpful because that gives the developer some hint about the error happened in his coding. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34513] New: - jsp exception handling
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34513. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34513 Summary: jsp exception handling Product: Tomcat 5 Version: 5.0.28 Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I use the following directive %@ page errorPage=/jsp/error.jsp % to tell jsp to move to error.jsp when exception raises on the page. But I noticed the the real behavior relates to the position that the exception raises on the JSP page: 1.When it raises on the relatively front part of the page, the page is redirected correctly to /jsp/error.jsp 2.if exception raises at relatively rear position, the contenct of the /jsp/error.jsp is outputed right after the normal output of the page. 3.If at even rearer position, the result is a weird chopped page with only part of normal output. I tried to debugged the src of jasper into PageContextImpl's doHandlePageException method. Found that the situation 2 was caused by JspWriterImpl has already flushed, the situation 3 was caused by the response was already committed. I can't understand this behavior of tomcat. Isn't it puzzling to the ones that want to debug JSP page? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34396] New: - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 Summary: security exception using datasource in servlet- instance.init() Product: Tomcat 5 Version: 5.5.7 Platform: All OS/Version: Windows XP Status: NEW Severity: minor Priority: P3 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Startup Java Option added: -Djava.security.manager -Djava.security.policy=TOMCAT_HOME/conf/catalina.policy java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.org.apache.tomcat.dbcp.collections) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1512) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.init(GenericObjectPool.java:392) at org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.init(GenericObjectPool.java:258) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:795) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at it.rgi.webapp.dbms.jdbc.DataSourcePool.get(DataSourcePool.java:123) at it.rgi.webapp.dbms.jdbc.JdbcConnettoreRetry.acquisisciConnessione(JdbcConnettoreRetry.java:901) at it.rgi.webapp.dbms.jdbc.JdbcConnettoreRetry.getDatabaseInfo(JdbcConnettoreRetry.java:754) at it.rgi.webapp.dbms.jdbc.JdbcConnettoreRetry.getDatabaseInfo(JdbcConnettoreRetry.java:752) at it.rgi.webapp.admin.StartUpProcess.database(StartUpProcess.java:534) at it.rgi.webapp.admin.StartUpProcess.execStartUpProcess(StartUpProcess.java:399) at it.rgi.webapp.admin.StartUpProcess.startup(StartUpProcess.java:282) at it.rgi.webapp.admin.StartUpProcess.startup(StartUpProcess.java:254) at it.rgi.webapp.admin.ServletAdmin.single_init(ServletAdmin.java:88) at it.rgi.webapp.admin.ServletAdmin.init(ServletAdmin.java:80) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:114) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1062) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:900) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3823) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4087) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121) at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:737) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:590) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 --- Additional Comments From [EMAIL PROTECTED] 2005-04-11 11:19 --- Created an attachment (id=14677) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14677action=view) catalina.policy -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34396.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34396
--- Additional Comments From [EMAIL PROTECTED] 2005-04-11 11:21 ---
(From update of attachment 14677)
//
// catalina.corepolicy - Security Policy Permissions for Tomcat 5
//
// This file contains a default set of security policies to be enforced (by the
// JVM) when Catalina is executed with the -security option. In addition
// to the permissions granted here, the following additional permissions are
// granted to the codebase specific to each web application:
//
// * Read access to the document root directory
//
// $Id: catalina.policy,v 1.12 2004/09/15 18:57:41 jfarcand Exp $
//
// == SYSTEM CODE PERMISSIONS =
// These permissions apply to javac
grant codeBase file:${java.home}/lib/- {
permission java.security.AllPermission;
};
// These permissions apply to all shared system extensions
grant codeBase file:${java.home}/jre/lib/ext/- {
permission java.security.AllPermission;
};
// These permissions apply to javac when ${java.home] points at $JAVA_HOME/jre
grant codeBase file:${java.home}/../lib/- {
permission java.security.AllPermission;
};
// These permissions apply to all shared system extensions when
// ${java.home} points at $JAVA_HOME/jre
grant codeBase file:${java.home}/lib/ext/- {
permission java.security.AllPermission;
};
// == CATALINA CODE PERMISSIONS ===
// These permissions apply to the launcher code
grant codeBase file:${catalina.home}/bin/commons-launcher.jar {
permission java.security.AllPermission;
};
// These permissions apply to the daemon code
grant codeBase file:${catalina.home}/bin/commons-daemon.jar {
permission java.security.AllPermission;
};
// These permissions apply to the commons-logging API
grant codeBase file:${catalina.home}/bin/commons-logging-api.jar {
permission java.security.AllPermission;
};
// These permissions apply to the server startup code
grant codeBase file:${catalina.home}/bin/bootstrap.jar {
permission java.security.AllPermission;
};
// These permissions apply to the JMX server
grant codeBase file:${catalina.home}/bin/jmx.jar {
permission java.security.AllPermission;
};
// These permissions apply to the servlet API classes
// and those that are shared across all class loaders
// located in the common directory
grant codeBase file:${catalina.home}/common/- {
permission java.security.AllPermission;
};
// These permissions apply to the container's core code, plus any additional
// libraries installed in the server directory
grant codeBase file:${catalina.home}/server/- {
permission java.security.AllPermission;
};
// The permissions granted to the balancer WEB-INF/classes directory
grant codeBase file:${catalina.home}/webapps/balancer/WEB-INF/classes/- {
permission java.lang.RuntimePermission
accessClassInPackage.org.apache.tomcat.util.digester;
permission java.lang.RuntimePermission
accessClassInPackage.org.apache.tomcat.util.digester.*;
};
// == WEB APPLICATION PERMISSIONS =
// These permissions are granted by default to all web applications
// In addition, a web application will be given a read FilePermission
// and JndiPermission for all files and directories in its document root.
grant {
// Required for JNDI lookup of named JDBC DataSource's and
// javamail named MimePart DataSource used to send mail
permission java.util.PropertyPermission java.home, read;
permission java.util.PropertyPermission java.naming.*, read;
permission java.util.PropertyPermission javax.sql.*, read;
// OS Specific properties to allow read access
permission java.util.PropertyPermission os.name, read;
permission java.util.PropertyPermission os.version, read;
permission java.util.PropertyPermission os.arch, read;
permission java.util.PropertyPermission file.separator, read;
permission java.util.PropertyPermission path.separator, read;
permission java.util.PropertyPermission line.separator, read;
// JVM properties to allow read access
permission java.util.PropertyPermission java.version, read;
permission java.util.PropertyPermission java.vendor, read;
permission java.util.PropertyPermission java.vendor.url, read;
permission java.util.PropertyPermission java.class.version, read;
permission java.util.PropertyPermission java.specification.version,
read;
permission
DO NOT REPLY [Bug 34396] - security exception using datasource in servlet-instance.init()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34396. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34396 --- Additional Comments From [EMAIL PROTECTED] 2005-04-11 11:25 --- Created an attachment (id=14678) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14678action=view) catalina.policy catalina.policy (correct version) line 195 must be: // permission java.security.AllPermission; -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34390] New: - SEVERE: Exception opening database connection
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34390. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34390 Summary: SEVERE: Exception opening database connection Product: Tomcat 5 Version: 5.5.7 Platform: PC URL: http://kisslet.alphabit.org OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I was running Sun J2SDK 1.5.0 with Tomcat 5.5.4 and everything was fine. Then I tried to update to Sun J2RE 1.5.0_02 with Tomcat 5.5.7 and got the error bellow, now I'm running the new Sun J2SDK 1.5.0_02 with old Tomcat 5.5.4. With this error I cannot login users (though I have a servlet that accesses the same database using the same driver with no problem at all). here it is: Using CATALINA_BASE: /oem/java/tomcat Using CATALINA_HOME: /oem/java/tomcat Using CATALINA_TMPDIR: /oem/java/tomcat/temp Using JRE_HOME: /usr/lib/j2re1.5-sun Apr 10, 2005 2:06:19 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-443 Apr 10, 2005 2:06:19 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-80 Apr 10, 2005 2:06:19 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 2813 ms Apr 10, 2005 2:06:19 PM org.apache.catalina.core.StandardService start INFO: Starting service HTTPS public service Apr 10, 2005 2:06:19 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.7 Apr 10, 2005 2:06:19 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Apr 10, 2005 2:06:20 PM org.apache.catalina.startup.ContextConfig validateSecurityRoles INFO: WARNING: Security role name blog used in an auth-constraint without being defined in a security-role Apr 10, 2005 2:06:20 PM org.apache.catalina.realm.JAASRealm setContainer INFO: Set JAAS app name SSL public engine engine Apr 10, 2005 2:06:21 PM org.apache.catalina.startup.ContextConfig applicationWebConfig INFO: Missing application web.xml, using defaults only StandardEngine[SSL public engine engine].StandardHost[private.alphabit.org].StandardContext[/static] Apr 10, 2005 2:06:22 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-443 Apr 10, 2005 2:06:22 PM org.apache.catalina.core.StandardService start INFO: Starting service HTTP public service Apr 10, 2005 2:06:22 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.7 Apr 10, 2005 2:06:22 PM org.apache.catalina.realm.JDBCRealm start SEVERE: Exception opening database connection java.sql.SQLException: org.postgresql.Driver at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:646) at org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:720) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1003) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:440) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:683) at org.apache.catalina.startup.Catalina.start(Catalina.java:537) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409) Apr 10, 2005 2:06:22 PM org.apache.catalina.core.StandardHost start -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34390] - SEVERE: Exception opening database connection
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34390. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34390 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-04-10 15:48 --- Although the JDBC realm has severe issues in 5.5.7, this is caused by an unrelated failure to load the driver. Feel free to use 5.5.4 all you want, however ;) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34170 --- Additional Comments From [EMAIL PROTECTED] 2005-03-31 16:42 --- Could you please clarify th: 1. What is the exact nature of the bug that has been fixed? Does it depend on the Oracle version or the OS? Would moving the database to the same m/c where tomcat runs resolve the problem temporarily? 2. When is the next stable version being released with this bug fixed? (In reply to comment #1) This has already been fixed in CVS. However, I recommend using the data source realm instead, which is more robust and scalable (and setup is about the same). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34170] New: - Connection reset by peer exception while performing basic authentication (db connection pool not being used)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34170 Summary: Connection reset by peer exception while performing basic authentication (db connection pool not being used) Product: Tomcat 5 Version: 5.5.7 Platform: Macintosh OS/Version: other Status: NEW Severity: normal Priority: P1 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hi, Problem: While trying to login to our application using basic authentication, there is an sql exception being thrown. It starts working fine after tomcat is restarted. This happens periodically. I am not sure about how often users logged in between periods of failure. It is possible that there was nobody using it for may be 15 days or so. It is critical that we fix this problem asap as the users are unhappy about failures this often. What's puzzling is that while performing basic authentication, the connection should be closed after the browser is exited. So how can there be a connection reset problem!!! Environment: The basic authentication has been configured using JDBC Realm entry in context.xml of the app. The backend database is Oracle 10G that is on a different m/c from that where tomcat runs. Symptoms: The server was restarted on Feb 25 and the log below shows socket exception on Feb 27. When there was an attempt to login on Mar 15, there was an authentication error. But the socket exception doesn't show up in the logs anytime after Feb 27 although authentication failed once again on Mar 24. It is not clear why there's only one socket exception but two authentication failures between restarts of tomcat. Feb 25, 2005 3:12:48 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 5250 msFeb 27, 2005 3:52:51 AM org.apache.tomcat.util.net.PoolTcpEndpoint processSocketSEVERE: Socket error caused by remote host /60.21.206.10java.net.SocketException: Connection reset by peerat java.net.PlainSocketImpl.socketSetOption(Native Method)at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:240)at java.net.Socket.setTcpNoDelay(Socket.java:771)at org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.java:502) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:514) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:552)Mar 15, 2005 9:41:50 AM org.apache.catalina.realm.JDBCRealm getPasswordSEVERE: Exception retrieving password for evmjava.sql.SQLException: Io exception: Connection reset at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:273) at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:800) at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:912) at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:693) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:983) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2884) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2925) at org.apache.catalina.realm.JDBCRealm.getPassword(JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347) at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34170 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |critical -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34170] - Connection reset by peer exception while performing basic authentication (db connection pool not being used)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34170 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-03-25 01:08 --- This has already been fixed in CVS. However, I recommend using the data source realm instead, which is more robust and scalable (and setup is about the same). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-03-23 17:54 --- I've separated out the commit and the close in DataSourceRealm#close(Connection). Maybe that will help. I've also looked over the DataSourceRealm.java code, and it clearly looks like everywhere open is called, if the connection returned is not null, it's closed in a finally block as it should be. Please try 5.5.9 when it comes out (probably this weekend) or building from HEAD if you don't feel like waiting until the weekend to try it out. I haven't looked at JDBCRealm. As Remy suggested previously, DataSourceRealm is better and recommended. Finally: if you still get this behavior with 5.5.9, and reopen this issue, please let us know what JDK you're using. Also what DB version and driver, and if the behavior is reproducible with other DBs or drivers. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22388] - TC 5.0.* Startup Exception (ConcurrentModificationException)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=22388. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=22388 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ||.com --- Additional Comments From [EMAIL PROTECTED] 2005-03-22 16:29 --- *** Bug 34126 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 09:04 --- No. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 16:40 --- (In reply to comment #2) No. what!? You mean you don't feel this is a defect? Failures are happening and no clear reason is given, this is clearly a defect. I can fix the darn thing. Why are you closing this as wontfix? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 16:43 --- My answer to feedack please ? is no. I don't see much to clarify here. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 16:44 --- (In reply to comment #4) My answer to feedack please ? is no. I don't see much to clarify here. I understand that part, but why are you closing it as wontfix? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 16:51 --- (In reply to comment #4) My answer to feedack please ? is no. I don't see much to clarify here. root cause exception is discarded. This is a defect in any software. This obscures the reason for the failure and makes it more difficult for the user to resolve it. This needs to be fixed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 16:54 --- The issue here is that the JDBC realm is a toy realm: it doesn't scale at all, and by definition is not very robust. I would now like to keep it frozen except for actual bugfixes, to avoid any possible regression like the one that was in 5.5.7. I think you should use the data source realm instead. Please do not bother reopening this report, nor your other one. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34080.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34080
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Additional Comments From [EMAIL PROTECTED] 2005-03-19 17:24 ---
Ahhh, thank you for that information. That makes more sense. So this reaml is
probably on track for deprecation then? Which realm precisely are you referring
to? My project is still using 5.0.28 and I can't change that until the
Standards Committee gets around to approving 5.5.
Please understand that I'm a quality freak and I have a hard time seeing stuff
like that and letting it go. Also, I jacked around with this for a few hours
before I discovered that I was getting this exception because I didn't install
the jar file globally.
Also, another posible solution, although kinda ugly, is just to throw a new
SQLException(Can't load driver class) { public Throwable getCause() { return
e; } }; That would leave the exception type the same and pass the root cause.
Or if we don't want the anonymous ugly thing, we can at least throw new
SQLException(Can't load driver class: + e.class() + + e.getMessege());
Daniel
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 [EMAIL PROTECTED] changed: What|Removed |Added CC|[EMAIL PROTECTED] | --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 19:20 --- The data source realm is DataSourceRealm. http://jakarta.apache.org/tomcat/tomcat-5.5-doc/realm-howto.html#DataSourceRealm Note that it has a regression in 5.5.7 caused by the addition of digest auth support, so you should be using the realm from either 5.5.4 or 5.5.8. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] New: - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34080.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34080
Summary: JDBCRealm looses original exception, fabricates
exception type
Product: Tomcat 5
Version: Nightly Build
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]
naughty, naughty programmer ditches the original exception. See line 684 of
current nightly build of org.apache.catalina.realm.JDBCRealm.java
// Instantiate our database driver if necessary
if (driver == null) {
try {
Class clazz = Class.forName(driverName);
driver = (Driver) clazz.newInstance();
} catch (Throwable e) {
throw new SQLException(e.getMessage());
}
}
As you can see, only the message of the exception is retained which is usually
meaningless without knowning the exception it's self. The original stack trace
is also lost. To make matters worse, SQLException doesn't take a rootCause to
show you this because it expects this to come from a DBMS and not a driver class
loading routine.
The issues surrounding this catch Throwable is that Class.forName() can throw
some nasty errors and we dont want a bad JDBC realm configuration to bring down
Tomcat. The possible Throwables from this try block are:
LinkageError
ExceptionInInitializerError
ClassNotFoundException
ClassCastException
Additionally, ExceptionInInitializerError can contain an exception from the
static initializer of the driver class that failed to load, compounding the
original lost exception issue. This presents a diverse array of possible
problems.
I propose we throw a LifeCycleException, but catch it in the start() method. If
I understand the logic correctly, we want to let the app start up if they aren't
using authentication, even though they don't have their realm configured
correctly.
Feedback please?
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34080] - JDBCRealm looses original exception, fabricates exception type
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34080. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34080 --- Additional Comments From [EMAIL PROTECTED] 2005-03-19 05:41 --- Actually, the open() method is called from several places, looks like it may be better to have a RealmException class or even an internal mechanism or private static innerclass or something. Feedback please? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JDBC Realm exception
Hi, I was able to get my JDBC basic authentication realm working fine. I left my server running overnight (session would have timed out) and when I tried to access my resource this morning I was getting this. I'm still looking into it, but I can reproduce it and will post details soon. This is a major show stopper for me. Any thoughts guys? Thank you!! Darren PS. Uses MD5 password hashing. Like I said, it works but at some point starts throwing this exception (I think after session expire). Mar 6, 2005 10:04:33 AM org.apache.catalina.realm.JDBCRealm getPassword SEVERE: Exception retrieving password for architect java.sql.SQLException: Connection.close() has already been called. Invalid operation in this state. at com.mysql.jdbc.Connection.getMutex(Connection.java:2086) at com.mysql.jdbc.PreparedStatement.executeQuery PreparedStatement.java:1508) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JDBC Realm exception
Yep. It definitely hoses up when the session times out. In fact, the JDBC realm adaptor is blown for all valid user accounts in the RDBMS server, not just the session that timed out. Here is a slightly different but easily repeated exception. It may be within the MySQL driver, but I somehow doubt it. My 5.025 tomcat did not have this problem I believe. Only restarting Tomcat corrects this, but only until the session times out. Mar 6, 2005 5:48:25 PM org.apache.catalina.realm.JDBCRealm getPassword WARNING: Exception retrieving password for guest Mar 6, 2005 5:48:25 PM org.apache.catalina.connector.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.NullPointerException at com.mysql.jdbc.PreparedStatement.setString (PreparedStatement.java:1254) at org.apache.catalina.realm.JDBCRealm.credentials (JDBCRealm.java:497) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:525) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) On Sun, 2005-03-06 at 10:19 -0500, Darren Govoni wrote: Hi, I was able to get my JDBC basic authentication realm working fine. I left my server running overnight (session would have timed out) and when I tried to access my resource this morning I was getting this. I'm still looking into it, but I can reproduce it and will post details soon. This is a major show stopper for me. Any thoughts guys? Thank you!! Darren PS. Uses MD5 password hashing. Like I said, it works but at some point starts throwing this exception (I think after session expire). Mar 6, 2005 10:04:33 AM org.apache.catalina.realm.JDBCRealm getPassword SEVERE: Exception retrieving password for architect java.sql.SQLException: Connection.close() has already been called. Invalid operation in this state. at com.mysql.jdbc.Connection.getMutex(Connection.java:2086) at com.mysql.jdbc.PreparedStatement.executeQuery PreparedStatement.java:1508) at org.apache.catalina.realm.JDBCRealm.getPassword (JDBCRealm.java:526) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:399) at org.apache.catalina.realm.JDBCRealm.authenticate (JDBCRealm.java:347) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate (BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:446) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) - 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]
DO NOT REPLY [Bug 17178] - if user-agent sends cookies that add up more than 4K SocketInputStream throws an exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=17178. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=17178 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-03-01 21:56 --- The HTTP connector has been deprecated. Use the Coyote connector instead. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22869] - under liveDeploy a webapp may throw an exception on restart. if some files are soft links
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=22869. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=22869 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-02-28 22:02 --- *** This bug has been marked as a duplicate of 21818 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - [PATCH] Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 [EMAIL PROTECTED] changed: What|Removed |Added Summary|Page context not fully |[PATCH] Page context not |populated for Exception if |fully populated for |using app-wide error page |Exception if using app-wide ||error page Version|Unknown |5.5.7 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 --- Additional Comments From [EMAIL PROTECTED] 2005-02-25 10:51 --- (In reply to comment #3) Maybe this helps: connectionURL=jdbc:mysql://projekt1:3306/elmar?autoReconnect=true I had tried it on Tomcat 5.5.8 and it did not work. Thanks! -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - [PATCH] Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 --- Additional Comments From [EMAIL PROTECTED] 2005-02-25 18:44 --- Created an attachment (id=14363) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14363action=view) Alternative patch Alternative patch used to fix the issue. This patch leverages JspRuntimeLibrary.getThrowable(), which already checks for javax.servlet.error.exception and javax.servlet.jsp.jspException, in this order. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - [PATCH] Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31204] - Tomcat exits on null pointer exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31204. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31204 --- Additional Comments From [EMAIL PROTECTED] 2005-02-18 17:17 --- Have recently seen this issue in a production environment under load. Appears to occur randomly via Apache 2.0.50/jk2.0.4 to Tomcat 5.0.27. Our application servlet nevers sees the text/xml POST. Tomcat does not crash however, just never sees or processes the message. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25273] - Exception processing TLD at resource path - say where it is really looking for this file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25273. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25273 --- Additional Comments From [EMAIL PROTECTED] 2005-02-15 23:34 --- Changing this to an enhancement request. It doesn't seem unreasonable to me to expect a sysadmin to know where the docBase is for the /myApp context. Additionally, since Context.getDocBase() may return an absolute pathname, a relative pathname or a URL displaying the real location correctly in all of these circumstances seems like a lot of work for relatively little benefit. That said, patches will always be considered. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25273] - Exception processing TLD at resource path - say where it is really looking for this file
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25273. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25273 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement --- Additional Comments From [EMAIL PROTECTED] 2005-02-15 23:35 --- Actually changing the severity this time... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 --- Additional Comments From [EMAIL PROTECTED] 2005-02-12 11:21 --- Maybe this helps: connectionURL=jdbc:mysql://projekt1:3306/elmar?autoReconnect=true -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JspC exception
Hi all, I am doing compilation using JspC.It is giving ClassCastException. parentClassLoader = (URLClassLoader)Thread.currentThread().getContextClassLoader() getContextClassLoader() will return AntClassLoader which is incompatible with URLClassLoader. Is this a bug? If so, does it has a fix? Please, anybody has a solution for this. help me out. Thanks, Jagga __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: JspC exception
Jagadeesha T wrote: Hi all, I am doing compilation using JspC.It is giving ClassCastException. parentClassLoader = (URLClassLoader)Thread.currentThread().getContextClassLoader() getContextClassLoader() will return AntClassLoader which is incompatible with URLClassLoader. Is this a bug? If so, does it has a fix? Please, anybody has a solution for this. help me out. I know you are probably trying to save our time reading by making your message shorter, but could you instead: - post to tomcat-user - post the full stack trace - mention which version you are using Thanks :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20217] - Exception invoking method storeConfig
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=20217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=20217 [EMAIL PROTECTED] changed: What|Removed |Added Summary|restartContext doesn't work |Exception invoking method |when a context configuration|storeConfig |file maps a path to two | |levels. | Version|5.0.2 |5.0.28 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 --- Additional Comments From [EMAIL PROTECTED] 2005-01-12 20:52 --- I have the same issue with 5.5.5. After restart realm login works for a while then it stops working and logs the same message. Now I migrated to datasource realm, and it seems login works now, but only if I setup DBCP to recover abandoned connections. Specifically, this happened: First I setup the datasource using the default parameters recommended in the tomcat-5.5-doc/jndi-datasource-examples-howto.html document, but with maxActive=3 maxIdle=1. In thic case the first login was sucessful, the second (if I remember well) was failed. The log entry was this: SEVERE: Exception performing authentication org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool exhausted... Caused by: java.util.NoSuchElementException: Timeout waiting for idle object Next I switched on abandoned resource removal (using removeAbandoned=true removeAbandonedTimeout=5 logAbandoned=true). In this case the following appears in the log after each (successful) login attempts: DBCP object created 2005-01-12 20:37:09 by the following code was never closed: java.lang.Exception at org.apache.tomcat.dbcp.dbcp.AbandonedTrace.setStackTrace(AbandonedTrace.java:157) at org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:76) at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at org.apache.catalina.realm.DataSourceRealm.open(DataSourceRealm.java:407) at org.apache.catalina.realm.DataSourceRealm.getRoles(DataSourceRealm.java:538) at org.apache.catalina.realm.DataSourceRealm.authenticate(DataSourceRealm.java:360) at org.apache.catalina.realm.DataSourceRealm.authenticate(DataSourceRealm.java:284) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:181) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30063] - tomcat suddenly terminated with following messages - Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=80] ignored exception:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30063. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30063 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2005-01-07 16:49 --- This is fixed in 4.1.31 *** This bug has been marked as a duplicate of 27315 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Socket Exception - Heavy load
Windows is notorious for holding the socket binding for some time after the close is done. I expected that you would see a BindException, not a SocketException. This exception is thrown if a socket cannot be created and bound to the requested port. However, your error looks like the receiver dropped the connection. If the OutputStream was closed after you finished sending (before you started receiving), that's the cause of your problem, since closing the OutputStream also closes the socket. In any event it's the client that is closing the socket connection. BTW, 1.2.8 refers to a JK version not JK2 unless there is some really old version of JK2 of which I'm not aware. Perhaps Mladen Turk (JK expert) can help. -Original Message- From: shyam [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:17 PM To: 'Tomcat Users List' Subject: RE: Socket Exception - Heavy load Hi Mark, Thanks. I would remember this . Thanks shyam -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:10 PM To: Tomcat Users List Subject: Re: Socket Exception - Heavy load Please do not hijack another message thread. If you wish to post to the list create a new message and send it. DO NOT reply to a list message and change the subject. Thread aware mail clients still recognise this as a reply and do not show it as a new message. Mark [EMAIL PROTECTED] shyam wrote: Hi All, I am doing some performance tests. Under heavy load I get socket exceptions in my tomcat logs SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:556) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:494) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 614) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool java:644) at java.lang.Thread.run(Unknown Source) I guess it has something to do with jk2 and the sockets. It would be helpful if someone can explain this and why it is happening? My configuration is Apache 2.0.52 Tomcat 5.0.29 Jk2 - 1.2.8 Thanks shyam - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Socket Exception - Heavy load
Sorry, I thought you had a socket write error. Looks like a read error. -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:35 PM To: Tomcat Users List Cc: Tomcat Developers List Subject: RE: Socket Exception - Heavy load Windows is notorious for holding the socket binding for some time after the close is done. I expected that you would see a BindException, not a SocketException. This exception is thrown if a socket cannot be created and bound to the requested port. However, your error looks like the receiver dropped the connection. If the OutputStream was closed after you finished sending (before you started receiving), that's the cause of your problem, since closing the OutputStream also closes the socket. In any event it's the client that is closing the socket connection. BTW, 1.2.8 refers to a JK version not JK2 unless there is some really old version of JK2 of which I'm not aware. Perhaps Mladen Turk (JK expert) can help. -Original Message- From: shyam [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:17 PM To: 'Tomcat Users List' Subject: RE: Socket Exception - Heavy load Hi Mark, Thanks. I would remember this . Thanks shyam -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:10 PM To: Tomcat Users List Subject: Re: Socket Exception - Heavy load Please do not hijack another message thread. If you wish to post to the list create a new message and send it. DO NOT reply to a list message and change the subject. Thread aware mail clients still recognise this as a reply and do not show it as a new message. Mark [EMAIL PROTECTED] shyam wrote: Hi All, I am doing some performance tests. Under heavy load I get socket exceptions in my tomcat logs SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:556) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:494) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 614) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool java:644) at java.lang.Thread.run(Unknown Source) I guess it has something to do with jk2 and the sockets. It would be helpful if someone can explain this and why it is happening? My configuration is Apache 2.0.52 Tomcat 5.0.29 Jk2 - 1.2.8 Thanks shyam - 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] - 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: Socket Exception - Heavy load
What is your wait_timeout set to? ContactInfo NameDerrick Koes/Name TitleSenior Software Engineer/Title Company name=SkillSoft url=http://www.skillsoft.com/ AIMcodeauthor2001/AIM Email[EMAIL PROTECTED]/Email Phone(603) 821-3260/Phone Cell(603) 305-1753/Cell Fax/ Quote attributedTo=YodaNo, try not, do or do not, there is no try./Quote /ContactInfo -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:38 PM To: Tomcat Developers List; Tomcat Users List Subject: RE: Socket Exception - Heavy load Sorry, I thought you had a socket write error. Looks like a read error. -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:35 PM To: Tomcat Users List Cc: Tomcat Developers List Subject: RE: Socket Exception - Heavy load Windows is notorious for holding the socket binding for some time after the close is done. I expected that you would see a BindException, not a SocketException. This exception is thrown if a socket cannot be created and bound to the requested port. However, your error looks like the receiver dropped the connection. If the OutputStream was closed after you finished sending (before you started receiving), that's the cause of your problem, since closing the OutputStream also closes the socket. In any event it's the client that is closing the socket connection. BTW, 1.2.8 refers to a JK version not JK2 unless there is some really old version of JK2 of which I'm not aware. Perhaps Mladen Turk (JK expert) can help. -Original Message- From: shyam [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:17 PM To: 'Tomcat Users List' Subject: RE: Socket Exception - Heavy load Hi Mark, Thanks. I would remember this . Thanks shyam -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:10 PM To: Tomcat Users List Subject: Re: Socket Exception - Heavy load Please do not hijack another message thread. If you wish to post to the list create a new message and send it. DO NOT reply to a list message and change the subject. Thread aware mail clients still recognise this as a reply and do not show it as a new message. Mark [EMAIL PROTECTED] shyam wrote: Hi All, I am doing some performance tests. Under heavy load I get socket exceptions in my tomcat logs SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:556) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:494) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 614) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool java:644) at java.lang.Thread.run(Unknown Source) I guess it has something to do with jk2 and the sockets. It would be helpful if someone can explain this and why it is happening? My configuration is Apache 2.0.52 Tomcat 5.0.29 Jk2 - 1.2.8 Thanks shyam - 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] - 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]
RE: Socket Exception - Heavy load
Sorry, it's socket_timeout, not wait_timeout. -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:43 PM To: Tomcat Developers List; Tomcat Users List Subject: RE: Socket Exception - Heavy load What is your wait_timeout set to? ContactInfo NameDerrick Koes/Name TitleSenior Software Engineer/Title Company name=SkillSoft url=http://www.skillsoft.com/ AIMcodeauthor2001/AIM Email[EMAIL PROTECTED]/Email Phone(603) 821-3260/Phone Cell(603) 305-1753/Cell Fax/ Quote attributedTo=YodaNo, try not, do or do not, there is no try./Quote /ContactInfo -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:38 PM To: Tomcat Developers List; Tomcat Users List Subject: RE: Socket Exception - Heavy load Sorry, I thought you had a socket write error. Looks like a read error. -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:35 PM To: Tomcat Users List Cc: Tomcat Developers List Subject: RE: Socket Exception - Heavy load Windows is notorious for holding the socket binding for some time after the close is done. I expected that you would see a BindException, not a SocketException. This exception is thrown if a socket cannot be created and bound to the requested port. However, your error looks like the receiver dropped the connection. If the OutputStream was closed after you finished sending (before you started receiving), that's the cause of your problem, since closing the OutputStream also closes the socket. In any event it's the client that is closing the socket connection. BTW, 1.2.8 refers to a JK version not JK2 unless there is some really old version of JK2 of which I'm not aware. Perhaps Mladen Turk (JK expert) can help. -Original Message- From: shyam [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:17 PM To: 'Tomcat Users List' Subject: RE: Socket Exception - Heavy load Hi Mark, Thanks. I would remember this . Thanks shyam -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, January 07, 2005 2:10 PM To: Tomcat Users List Subject: Re: Socket Exception - Heavy load Please do not hijack another message thread. If you wish to post to the list create a new message and send it. DO NOT reply to a list message and change the subject. Thread aware mail clients still recognise this as a reply and do not show it as a new message. Mark [EMAIL PROTECTED] shyam wrote: Hi All, I am doing some performance tests. Under heavy load I get socket exceptions in my tomcat logs SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:556) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:494) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 614) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool java:644) at java.lang.Thread.run(Unknown Source) I guess it has something to do with jk2 and the sockets. It would be helpful if someone can explain this and why it is happening? My configuration is Apache 2.0.52 Tomcat 5.0.29 Jk2 - 1.2.8 Thanks shyam - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 --- Additional Comments From [EMAIL PROTECTED] 2005-01-06 12:35 --- I've just added logging of the exception to get more details. This code section doesn't access the session, so I don't see why it would fail. I recommend migrating to the datasource realm, BTW. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement OS/Version|Windows XP |All Version|5.0.28 |Unknown -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-01-03 19:32 --- Closing per Torsten's comments -- thanks. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 --- Additional Comments From [EMAIL PROTECTED] 2004-12-25 23:00 --- Created an attachment (id=13843) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13843action=view) Patch against -r1.62 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 31659] - Page context not fully populated for Exception if using app-wide error page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31659 --- Additional Comments From [EMAIL PROTECTED] 2004-12-25 23:01 --- Patch with extended PageContextImpl.getException() to look also for javax.servlet.error.exception. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 --- Additional Comments From [EMAIL PROTECTED] 2004-12-25 23:52 --- JSP 2.0 Spec, 2.3.4 EL-Operators [] and .: Otherwise (a JavaBeans object), coerce value-b to String If value-b is a readable property of value-a, as per the JavaBeans specification: If getter throws an exception: error Otherwise: return result of getter call Otherwise: error. Boo/Foo are invalid javabeans properties. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32707] - Exception when response.getOutputStream is used in JSP-Page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32707 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-12-14 23:56 --- The fact that you're calling reset doesn't change the fact that you still have a pointer to the writer. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32707] - Exception when response.getOutputStream is used in JSP-Page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32707 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2004-12-15 00:15 --- The JSP-Page !-- $Id: index.jsp,v 1.39 2004/10/31 20:45:29 sven Exp $ -- %@ page import=java.io.* % %@ page import=java.util.* % % response.reset(); response.setContentType(text/html); OutputStream os = response.getOutputStream(); os.write(wurst.getBytes()); os.close(); return; % works as expected, the client will get 5 bytes of content. Only the cleanup-code in a finally-block in the compiled JSP-Page causes the exception. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32707] - Exception when response.getOutputStream is used in JSP-Page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32707 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-12-15 00:20 --- If you want to discuss fine points in the specification (such as JSP's usage of a writer), you should IMO try somewhere other than bugzilla. Thank you, and please do not reopen the report. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22388] - TC 5.0.* Startup Exception (ConcurrentModificationException)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=22388. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=22388 --- Additional Comments From [EMAIL PROTECTED] 2004-12-14 19:21 --- I get the same problem on a newly extracted 5.0.28 updated for SSL as discussed in http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html under Solaris 2.5.1 with JDK 1.4.2_06 and Solaris 2.8 with JDK 1.4.1_03. I can work around it by disabling JMX support at the top of my server.xml. Is there another way to fix this without losing JMX support? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22388] - TC 5.0.* Startup Exception (ConcurrentModificationException)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=22388. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=22388 --- Additional Comments From [EMAIL PROTECTED] 2004-12-14 20:22 --- I followed the steps in http://issues.apache.org/bugzilla/show_bug.cgi?id=29056 to replace Tomcat's JMX jar with Sun's JMX 1.2.1 reference implementation. Works like a champ. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32707] New: - Exception when response.getOutputStream is used in JSP-Page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32707 Summary: Exception when response.getOutputStream is used in JSP- Page Product: Tomcat 5 Version: 5.5.6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The Exception below is produced by this JSP-Page: !-- $Id: index.jsp,v 1.39 2004/10/31 20:45:29 sven Exp $ -- %@ page import=java.io.* % % response.reset(); OutputStream os = response.getOutputStream(); os.write(0); os.close(); % The Exception: Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: getOutputStream() has already been called for t his response at org.apache.catalina.connector.Response.getWriter(Response.java:596) at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:186) at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:124) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:117) at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:191) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75) at org.apache.jsp.test.index_jsp._jspService(org.apache.jsp.test.index_jsp:61) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at de.djh.servlet.filter.SetDates.doFilter(SetDates.java:80) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Unknown Source) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32646] New: - Serious: Exception retrieving password for username
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32646. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32646 Summary: Serious: Exception retrieving password for username Product: Tomcat 5 Version: 5.5.5 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Dear there, When I tried to update the Web AP from 5.0.28 to 5.5.5, I had the following error. It was OK for the first login but when the session timeout, it had the following error. And could not login again. 2004/12/7 ãß 10:22:50 org.apache.catalina.realm.JDBCRealm getPassword Serious: Exception retrieving password for username But there is no such problem for 5.0.28 for Mysql JDBCRealm Realm className=org.apache.catalina.realm.JDBCRealm driverName=org.gjt.mm.mysql.Driver connectionURL=jdbc:mysql://localhost/mydb connectionName=user connectionPassword=password digest=SHA userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name / Is that a bug for 5.5.5. Thanks in advance. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 [EMAIL PROTECTED] changed: What|Removed |Added Component|Servlet JSP API |Jasper --- Additional Comments From [EMAIL PROTECTED] 2004-12-09 17:20 --- Changing components to Jasper. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] New: - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32589.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32589
Summary: getter Exception where setter has the wrong signature
Product: Tomcat 5
Version: 5.5.4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Servlet JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I defined a bean with a getter that return a type A and with a setter with the
same suffix but the signature doesn't take an argument of type A. It seems that
the getter cannot be called with a el expression any more with tomcat5.5. It
worked fine with tomcat5.0.
I noticed the same thing with a bean with two getters (the method getBar()).
I found a workaround but I'd like to know if it is a real bug or if my bean
doesn't respect the el documentation.
Thanks in advance !
Fabrice.
This jsp :
-
%@ taglib uri=/tags/struts-bean prefix=bean %%@
taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
%
net.witbe.business.Foo fa = new net.witbe.business.Foo();
request.setAttribute(FooAttribute,fa);
%
The foo string is @${FooAttribute.foo}@
-
calling this bean :
-
package net.witbe.business;
public class Foo {
public long getFoo() {
return 1;
}
public void setFoo(int bh,long countm) {
// nop
}
public long getBar() {
return 5;
}
public long getBar(int num) {
return 6;
}
}
-
provoque an Exception :
-
exception
javax.servlet.ServletException: Unable to find a value for foo in object of
class net.witbe.business.Foo using operator .
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:845)
...
cause mère
javax.servlet.jsp.el.ELException: Unable to find a value for foo in object of
class net.witbe.business.Foo using operator .
org.apache.commons.el.Logger.logError(Logger.java:481)
org.apache.commons.el.Logger.logError(Logger.java:498)
...
-
Fabrice.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 --- Additional Comments From [EMAIL PROTECTED] 2004-12-08 18:10 --- Thanks for the obligatory killer argument It worked fine with tomcat5.0., which, given the implementation details, makes your bug report probably invalid. Please provide a ready to test war if you'd like us to examine this further. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32591] New: - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32591.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32591
Summary: getter Exception where setter has the wrong signature
Product: Tomcat 5
Version: 5.5.4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Servlet JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I defined a bean with a getter that return a type A and with a setter with the
same suffix but the signature doesn't take an argument of type A. It seems that
the getter cannot be called with a el expression any more with tomcat5.5. It
worked fine with tomcat5.0.
I noticed the same thing with a bean with two getters (the method getBar()).
I found a workaround but I'd like to know if it is a real bug or if my bean
doesn't respect the el documentation.
Thanks in advance !
Fabrice.
This jsp :
-
%@ taglib uri=/tags/struts-bean prefix=bean %%@
taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
%
net.witbe.business.Foo fa = new net.witbe.business.Foo();
request.setAttribute(FooAttribute,fa);
%
The foo string is @${FooAttribute.foo}@
-
calling this bean :
-
package net.witbe.business;
public class Foo {
public long getFoo() {
return 1;
}
public void setFoo(int bh,long countm) {
// nop
}
public long getBar() {
return 5;
}
public long getBar(int num) {
return 6;
}
}
-
provoque an Exception :
-
exception
javax.servlet.ServletException: Unable to find a value for foo in object of
class net.witbe.business.Foo using operator .
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:845)
...
cause mère
javax.servlet.jsp.el.ELException: Unable to find a value for foo in object of
class net.witbe.business.Foo using operator .
org.apache.commons.el.Logger.logError(Logger.java:481)
org.apache.commons.el.Logger.logError(Logger.java:498)
...
-
Fabrice.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 --- Additional Comments From [EMAIL PROTECTED] 2004-12-08 18:43 --- *** Bug 32591 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32591] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32591. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32591 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2004-12-08 18:43 --- *** This bug has been marked as a duplicate of 32589 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32591] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32591. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32591 --- Additional Comments From [EMAIL PROTECTED] 2004-12-08 18:52 --- Created an attachment (id=13684) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13684action=view) The war with the bug. The URL to test is : http://localhost:8080/minimal/foo.jsp Fabrice. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 32589] - getter Exception where setter has the wrong signature
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32589. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32589 --- Additional Comments From [EMAIL PROTECTED] 2004-12-08 18:54 --- Created an attachment (id=13685) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13685action=view) The war with the bug. The URL to call is : http://localhost:8080/minimal/foo.jsp Fabrice. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25217 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25217 [EMAIL PROTECTED] changed: What|Removed |Added Version|4.1.29 |4.1.31 --- Additional Comments From [EMAIL PROTECTED] 2004-12-02 11:21 --- I have the same issue with tomcat 4.1.30 and 4.1.31 on win XP And I have some suspicions of McAfee Viruscan On-Access scan. By the way, we dont get this error on tomcat 5.5.4. This is the log : 2004-12-02 11:37:09 ContextConfig[/admin] IOException processing JAR at resource path /WEB-INF/lib/struts.jar javax.servlet.ServletException: IOException processing JAR at resource path /WEB-INF/lib/struts.jar at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:875) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:809) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:587) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:181) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3523) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:774) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:548) at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:653) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1567) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:338) at org.apache.catalina.core.StandardHost.install(StandardHost.java:772) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:395) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:352) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:671) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1149) at org.apache.catalina.core.StandardHost.start(StandardHost.java:707) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143) at org.apache.catalina.startup.Catalina.start(Catalina.java:463) at org.apache.catalina.startup.Catalina.execute(Catalina.java:350) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at
DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25217 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2004-12-03 00:08 --- The admin app works for me on a clean install of 4.1.31. This is a configuration error. Bugzilla is not the right forum for these issues. Please follow this up on the tomcat-user mailing list. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18233] - CoyoteOuputStream throws exception when closing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=18233. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=18233 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] OS/Version||AIX Version|4.1.18 |4.0.1 Final --- Additional Comments From [EMAIL PROTECTED] 2004-11-30 19:29 --- (In reply to comment #0) Whilst printing a String to the ServletOuputStream, if the user presses the 'stop' button on their browser then an IOException is thrown. It is standard practice to try and close resources when an error occurs but when I try to close the stream I get another IOException (Connection reset by peer) because the close() method is trying to flush the stream. Now, either it is standard practice to not call close() or to ignore the exception but either of these means that the client is not confident that all the resources around the stream were cleaned up. I consider this a usability bug and possibly a functional bug, I don't really have time to investigate in the code any further to see whether the stream not being cleaned up causes any problems. Below is the stack trace that is thrown when trying to call close() on the ServletOuputStream using Tomcat 4.1.18, Java 1.4.1_02 under Windows 2K SP3: java.net.SocketException: Connection reset by peer: socket write error 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.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite (InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite (ChunkedOutputFilter.java:166) at org.apache.coyote.http11.InternalOutputBuffer.doWrite (InternalOutputBuffer.java:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes (OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer (ByteChunk.java:360) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:338) at org.apache.tomcat.util.buf.IntermediateOutputStream.write (C2BConverter.java:273) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes (StreamEncoder.java:334) at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer (StreamEncoder.java:402) at sun.nio.cs.StreamEncoder$CharsetSE.implFlush (StreamEncoder.java:406) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:150) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213) at org.apache.tomcat.util.buf.WriteConvertor.flush (C2BConverter.java:222) at org.apache.tomcat.util.buf.C2BConverter.flushBuffer (C2BConverter.java:165) at org.apache.coyote.tomcat4.OutputBuffer.realWriteChars (OutputBuffer.java:580) at org.apache.tomcat.util.buf.CharChunk.flushBuffer (CharChunk.java:388) at org.apache.coyote.tomcat4.OutputBuffer.close (OutputBuffer.java:313) at org.apache.coyote.tomcat4.CoyoteOutputStream.close (CoyoteOutputStream.java:125) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
