Hi Jon,
> I'm load testing an application with Apache JMeter. I'm PUTting a 1MB file and GETting in the next step.
>
> I'm getting exceptions like the following, which is deadlocking my JVM:
>
> WARNING: Unexpected exception occurred fireIOEvent().connection=org.glassfish.grizzly.nio.transport.TCPNIOConnection_at_2b39d891 event=WRITE
> java.lang.IllegalArgumentException: Position exceeds a limit: 74546>71090
> at org.glassfish.grizzly.memory.BuffersBuffer.setPosLim(BuffersBuffer.java:1547)
> at org.glassfish.grizzly.memory.BuffersBuffer.position(BuffersBuffer.java:261)
> at org.glassfish.grizzly.memory.BuffersBuffer.position(BuffersBuffer.java:57)
> at org.glassfish.grizzly.nio.transport.TCPNIOAsyncQueueWriter.write0(TCPNIOAsyncQueueWriter.java:125)
> at org.glassfish.grizzly.nio.AbstractNIOAsyncQueueWriter.processAsync(AbstractNIOAsyncQueueWriter.java:344)
> at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:127)
> at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:76)
> at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:63)
> at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:823)
> at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)
> at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:116)
> at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$000(WorkerThreadIOStrategy.java:55)
> at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$1.run(WorkerThreadIOStrategy.java:98)
> at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:508)
> at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:488)
> at java.lang.Thread.run(Thread.java:680)
>
> I'm not sure what to adjust here.
Which Grizzly version are you using? Is it one taken from the trunk or
2.1.1?
Again would be easier, if I'd be able to reproduce this on a simple test.
Thanks.
WBR,
Alexey.
> Thanks!
>
> Jon Brisbin
>
> http://jbrisbin.com
> Twitter: @j_brisbin
>
>