Any new tips?
I've a easy way to test the reset problem on OpenCMS right now:
1) Open browser, login (
http://localhost:8080/opencms/opencms/system/login)
2) Right click any page, and choose "edit"
3) Editor page has frames, and bottom frame shows username and some
statistics. This frame is auto-reloaded from time-to-time to avoid
session timeout. Just wait a few moments, after 4 or 5 reloads, content
of the frame changes to login page, and session was reset (and the
"encoding" error are on the server log).
Richter
Edson Carlos Ericksson Richter escreveu:
> I've been out for a week on an business event. Yesterday I've tried
> your suggestion (increasing from 30 to 90), but no changes - still
> session reset (either in OpenCMS and in JSF+JPA app made with NetBeans
> 5.5).
>
>
> Thanks,
>
> Richter
>
>
>
> Jeanfrancois Arcand escreveu:
>>
>>
>> Edson Carlos Ericksson Richter wrote:
>>> Duh, instead "don't throw new warning", I want to mean "don't throw
>>> this warning". The right phrase bellow:
>>>
>>> To prove my theory (that the character encoding is not the reason),
>>> why my 2.5 spec JSF application that don't throw this warning has
>>> been reset too? Should I uninstall completely Sun App Server and
>>> install again?
>>>
>>> Both throws "connection reset by peer". Yesterday I've tried a
>>> remote machine over slow link, and result is exactly same.
>>
>> Interesting. Can you change, in domain.xml, the value:
>>
>> <keep-alive max-connections="250" thread-count="1"
>> timeout-in-seconds="30"/>
>>
>> and increase timeout-in-seconds="30"
>>
>> I doubt "connection reset by peer" is the problem. There is an
>> exception swallowed somewhere. The problem is OPenCMS is a big
>> application and it is difficult to find what is causing the problem.
>> If you can isolate a test case, that will be easier. On my side, I
>> will deploy openCMS and see if I can reproduce the problem.
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> Richter
>>>
>>> Edson Carlos Ericksson Richter escreveu:
>>>> Me too. IMHO, there is something else - I suspect on the
>>>> "connection reset by peer" problem. But anyway, if the connection
>>>> is reset by peer is not motive to kill the session - or is it? So,
>>>> I think there is a bug somewhere, over the rainbow ;-)
>>>>
>>>> To prove my theory (that the character encoding is not the reason),
>>>> why my 2.5 spec JSF application that don't throw new warning has
>>>> been reset too? Should I uninstall completely Sun App Server and
>>>> install again?
>>>>
>>>>
>>>> TIA,
>>>>
>>>> Richter
>>>>
>>>>
>>>>
>>>>
>>>> Jan Luehe escreveu:
>>>>>
>>>>>
>>>>> Jan Luehe wrote On 06/30/06 09:42,:
>>>>>
>>>>>>
>>>>>>
>>>>>> Jeanfrancois Arcand wrote On 06/29/06 07:05,:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Edson Carlos Ericksson Richter wrote:
>>>>>>>
>>>>>>>> Ok, after changing parameter to 65535,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I recommend you don't use that high value for header :-) I think
>>>>>>> the real exception is:
>>>>>>>
>>>>>>> [#|2006-06-28T16:15:05.343-0300|WARNING|sun-appserver-pe9.0|org.apache.coyote.tomcat5.CoyoteRequest|_ThreadID=12;_ThreadName=http8080-Processor2;_RequestID=65f31d69-0aad-44ae-83d0-d0c5954a1a53;|Unable
>>>>>>> to set character encoding UTF-8 because request parameters have
>>>>>>> already been read, or ServletRequest.getReader() has been called|#]
>>>>>>>
>>>>>>> I need to take a look at the spec history change to see if that
>>>>>>> requirement is new in Servlet 2.5. Stay tuned :-)
>>>>>>
>>>>>>
>>>>>>
>>>>>> The above exception is the result of:
>>>>>>
>>>>>> https://servlet-spec-eg.dev.java.net/issues/show_bug.cgi?id=18
>>>>>>
>>>>>> which was added as a clarification to Servlet 2.5.
>>>>>
>>>>>
>>>>> Actually, the above message is not an exception, but just a
>>>>> warning. ;-)
>>>>>
>>>>> As it turned out, requiring ServletRequest.setCharacterEncoding()
>>>>> to throw an
>>>>> IllegalStateException would have broken too many existing webapps.
>>>>>
>>>>> Therefore, the final version of the Servlet 2.5 spec has withdrawn
>>>>> the
>>>>> requirement for ServletRequest.setCharacterEncoding() to throw an
>>>>> IllegalStateException.
>>>>>
>>>>> Instead, the spec now mentions that this method *has no effect* if
>>>>> called after
>>>>> - request parameters have been read, or
>>>>> - ServletRequest.getReader() has been called.
>>>>>
>>>>> In addition, GlassFish issues the above warning. I don't think this
>>>>> is responsible for the issue you're experiencing.
>>>>>
>>>>>
>>>>> Jan
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> Jan
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> -- Jeanfrancois
>>>>>>>
>>>>>>> take lot's of time working, then
>>>>>>>
>>>>>>>> following thread (and session reset):
>>>>>>>>
>>>>>>>> [#|2006-06-28T16:04:11.796-0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=11;_ThreadName=http8080-Processor4;_RequestID=2ce2d4e8-26ab-46ed-a7da-bd8a43e417f1;|ApplicationDispatcher[/opencms]
>>>>>>>> Servlet.service() for servlet jsp threw exception
>>>>>>>> java.lang.NullPointerException
>>>>>>>> at
>>>>>>>> org.opencms.file.CmsRequestContext.getAdjustedSiteRoot(CmsRequestContext.java:147)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.file.CmsRequestContext.removeSiteRoot(CmsRequestContext.java:387)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.db.CmsDbContext.removeSiteRoot(CmsDbContext.java:169)
>>>>>>>> at
>>>>>>>> org.opencms.db.CmsSecurityManager.readResource(CmsSecurityManager.java:3867)
>>>>>>>>
>>>>>>>> at org.opencms.file.CmsObject.readResource(CmsObject.java:2702)
>>>>>>>> at
>>>>>>>> org.opencms.workplace.editors.CmsEditorHandler.getEditorUri(CmsEditorHandler.java:86)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.workplace.editors.CmsEditorSelector.getSelectedEditorUri(CmsEditorSelector.java:127)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.jsp.WEB_002dINF.jsp.offline.system.workplace.editors.editor_005fmain_jsp._jspService(editor_005fmain_jsp.java:56)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
>>>>>>>>
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>> at
>>>>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:353)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:409)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:317)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:850)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:697)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:654)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:568)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.flex.CmsFlexRequestDispatcher.includeExternal(CmsFlexRequestDispatcher.java:194)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatcher.java:170)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.loader.CmsJspLoader.service(CmsJspLoader.java:433)
>>>>>>>> at
>>>>>>>> org.opencms.flex.CmsFlexRequestDispatcher.includeInternalWithCache(CmsFlexRequestDispatcher.java:423)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.flex.CmsFlexRequestDispatcher.include(CmsFlexRequestDispatcher.java:174)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.loader.CmsJspLoader.dispatchJsp(CmsJspLoader.java:467)
>>>>>>>> at org.opencms.loader.CmsJspLoader.load(CmsJspLoader.java:412)
>>>>>>>> at
>>>>>>>> org.opencms.loader.CmsResourceManager.loadResource(CmsResourceManager.java:719)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.opencms.main.OpenCmsCore.showResource(OpenCmsCore.java:1332)
>>>>>>>> at
>>>>>>>> org.opencms.main.OpenCmsServlet.doGet(OpenCmsServlet.java:151)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
>>>>>>>>
>>>>>>>> at
>>>>>>>> com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
>>>>>>>>
>>>>>>>> at
>>>>>>>> com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:706)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:626)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:548)
>>>>>>>>
>>>>>>>> at
>>>>>>>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:653)
>>>>>>>>
>>>>>>>> at java.lang.Thread.run(Thread.java:595)
>>>>>>>> |#]
>>>>>>>>
>>>>>>>> [#|2006-06-28T16:15:05.343-0300|WARNING|sun-appserver-pe9.0|org.apache.coyote.tomcat5.CoyoteRequest|_ThreadID=12;_ThreadName=http8080-Processor2;_RequestID=65f31d69-0aad-44ae-83d0-d0c5954a1a53;|Unable
>>>>>>>> to set character encoding UTF-8 because request parameters have
>>>>>>>> already been read, or ServletRequest.getReader() has been
>>>>>>>> called|#]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Richter
>>>>>>>>
>>>>>>>>
>>>>>>>> Jeanfrancois Arcand escreveu:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Edson Carlos Ericksson Richter wrote:
>>>>>>>>>
>>>>>>>>>> At this point, I do prefer test everything than stop 6
>>>>>>>>>> installations of Glassfish in course...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> OK then change, in domain.xml, the value:
>>>>>>>>>
>>>>>>>>> <request-processing header-buffer-length-in-bytes="4096"
>>>>>>>>>
>>>>>>>>> and see what you are getting.
>>>>>>>>>
>>>>>>>>> -- Jeanfrancois
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Richter
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Jeanfrancois Arcand escreveu:
>>>>>>>>>>
>>>>>>>>>>> To avoid that problem, you need to increase the header
>>>>>>>>>>> buffer. This problem has been fixed after FCS:
>>>>>>>>>>>
>>>>>>>>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=646
>>>>>>>>>>>
>>>>>>>>>>> Just take a look and increase the header buffer to a larger
>>>>>>>>>>> number. But I suspect there will be other problems....
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> -- Jeanfrancois
>>>>>>>>>>>
>>>>>>>>>>> Edson Carlos Ericksson Richter wrote:
>>>>>>>>>>>
>>>>>>>>>>>> And this, regarding a problem related to Tomcat 5.0.28:
>>>>>>>>>>>>
>>>>>>>>>>>> http://jira.atlassian.com/browse/JRA-8843
>>>>>>>>>>>>
>>>>>>>>>>>> May be same version we are using on Glassfish (since I
>>>>>>>>>>>> didn't suffered this problem on Tomcat 5.5.17 with OpenCMS)?
>>>>>>>>>>>>
>>>>>>>>>>>> Richter
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> users-help_at_glassfish.dev.java.net
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> users-help_at_glassfish.dev.java.net
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net