Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <48CA71E5.5080000@apache.org>
Date: Fri, 12 Sep 2008 09:43:01 -0400
From: Donald Woods <dwoods@apache.org>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: [DISCUSS] Release Geronimo Server 2.1.3 RC1
References: <48C824A4.4070503@apache.org> <48C990FC.5020407@earthlink.net>
 <48C9C9D5.7090705@apache.org> <48C9DCBC.6060707@earthlink.net>
In-Reply-To: <48C9DCBC.6060707@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

OK, sounds like something we should address in the 2.1.4 and 2.2 
releases, since its been around.  Need to get these security fixes out 
ASAP....


-Donald


Joe Bohn wrote:
> Donald Woods wrote:
>> Which browser, OS and JDK?
> 
> Firefox (but I doubt that matters), MacOSx, Java version 1.5.0_13
> 
>>
>> I installed several of the Sample plugins on the Tomcat-jee5 assembly 
>> on MacOSX, Apple 1.5.0_13 JDK and FF3 and didn't encounter this.
> 
> It a jetty only problem so you won't see it with Tomcat.  If you install 
> plugins in jetty via the admin console you are likely to see it.
> 
>>
>>
>> -Donald
>>
>>
>> Joe Bohn wrote:
>>>
>>> I only noticed one problem when installing plugins in the jetty 
>>> server.  It's been around for a while (I know it was in 2.1.2) but it 
>>> seems to be getting a bit worse.  Given that the problem was in 2.1.2 
>>> I don't think it merits a "-1" ...
>>>
>>> DWR is involved so I wonder if the upgrade to 2.0.5 has made it 
>>> worse. It's been previously described in this JIRA:
>>>
>>> https://issues.apache.org/jira/browse/GERONIMO-3942
>>>
>>> The problem seems to be happening more frequently and now it seems 
>>> that there are times it send the admin console into fits.  In the 
>>> past it was just a message that we saw stream out on the command 
>>> console.  Now it appears that it sometimes results in a frozen admin 
>>> console panel or even errors in the portlet (I've seen that once or 
>>> twice) ... perhaps also a result of the DWR updates.
>>>
>>> I included the exception below.
>>>
>>> Joe
>>>
>>>
>>>
>>> 12:54:01,276 ERROR [log] /console/dwr4/call/plainpoll/ReverseAjax.dwr
>>> java.lang.IllegalStateException: Committed
>>>     at org.mortbay.jetty.Response.resetBuffer(Response.java:995)
>>>     at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:211)
>>>     at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
>>>     at 
>>> org.apache.geronimo.console.servlet.ContextForwardServlet.doPost(ContextForwardServlet.java:71) 
>>>
>>>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>>>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>>>     at 
>>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>>>     at 
>>> org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:65) 
>>>
>>>     at 
>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>>>     at 
>>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:114) 
>>>
>>>     at 
>>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>>>     at 
>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
>>>     at 
>>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>>>     at 
>>> org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(TwistyWebAppContext.java:40) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(TwistyWebAppContext.java:65) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47) 
>>>
>>>     at 
>>> org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle(TwistyWebAppContext.java:59) 
>>>
>>>     at 
>>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206) 
>>>
>>>     at 
>>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) 
>>>
>>>     at 
>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>>>     at org.mortbay.jetty.Server.handle(Server.java:324)
>>>     at 
>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>>>     at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:374)
>>>     at 
>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) 
>>>
>>>     at 
>>> org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:506) 
>>>
>>>     at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
>>>     at 
>>> org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) 
>>>
>>>     at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 
>>>
>>>     at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 
>>>
>>>     at java.lang.Thread.run(Thread.java:613)
>>>
>>
> 
>