dev@glassfish.java.net

Re: exception while debugging

From: Tim Quinn <Timothy.Quinn_at_Sun.COM>
Date: Thu, 30 Apr 2009 11:23:27 -0500

Hi, Jennifer.

I've seen this occasionally too. I am not sure, but i think it happens
when I take a really long time in the debugger and Grizzly seems to grow
tired of waiting for the request/response exchange to complete between
the admin CLI and the admin adapter.

Jean-Francois, is that a possibility?

- Tim

Jennifer Chou wrote:
> While debugging in Netbeans I saw the following exception when I
> deploy simple hello.war. It doesn't happen when debug-enabled=false.
> C:\gfv3_1005\v3\distributions\web\target\glassfishv3\glassfish\bin>asadmin
> deplo
> y c:\samples\hello.war
> remote failure: Invalid chunk header
>
> Command deploy failed.
>
> and in the server.log
>
> SEVERE: service exception
> java.lang.RuntimeException: ClientAbortException:
> java.nio.channels.ClosedChann
> elException
> at
> com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:21
> 2)
> at
> com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java
> :165)
> at
> com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java
> :100)
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(Container
> Mapper.java:202)
> at
> com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:7
> 40)
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:631)
> at
> com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:900)
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFil
> ter.java:162)
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultPro
> tocolChain.java:136)
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
> a:103)
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
> a:89)
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java
> :76)
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextT
> ask.java:53)
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.
> java:57)
> at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: ClientAbortException:
> java.nio.channels.ClosedChannelException
> at
> com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.doFlush(GrizzlyOutputB
> uffer.java:437)
> at
> com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.flush(GrizzlyOutputBuf
> fer.java:403)
> at
> com.sun.grizzly.tcp.http11.GrizzlyOutputStream.flush(GrizzlyOutputStr
> eam.java:138)
> at
> com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:20
> 9)
> ... 17 more
> Caused by: java.nio.channels.ClosedChannelException
> at
> sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:1
> 26)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324)
> at
> com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:106)
>
> at
> com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:73)
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flushChannel(SocketCha
> nnelOutputBuffer.java:309)
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flushBuffer(SocketChan
> nelOutputBuffer.java:374)
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flush(SocketChannelOut
> putBuffer.java:352)
> at
> com.sun.grizzly.http.ProcessorTask.action(ProcessorTask.java:1125)
> at com.sun.grizzly.tcp.Response.action(Response.java:257)
> at
> com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.doFlush(GrizzlyOutputB
> uffer.java:432)
> ... 20 more
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>