GRIZZLY0013: Exception during FilterChain execution

[Максим Саяпин]

When using payara 171 and payara 172 such error occurs. When using payara 163 there is no error. Apparently the case in the version grizzlly.

[2017-06-22T20:23:14.586+0300] [Payara 4.1] [INFO] [] [ru.ritm.idp.connector.IDPConnector] [tid: ThreadID=1480 ThreadName=concurrent/__defaultManagedThreadFactory-Thread-15 SelectorRunner] [timeMillis: 1498152194586] [levelValue: 800] [[

  -- Accepted IDP connection: /10.78.8.82:48041]]

[2017-06-22T20:23:14.596+0300] [Payara 4.1] [WARNING] [] [org.glassfish.grizzly.filterchain.DefaultFilterChain] [tid: ThreadID=1487 ThreadName=concurrent/__defaultManagedThreadFactory-Thread-22] [timeMillis: 1498152194596] [levelValue: 900] [[

  GRIZZLY0013: Exception during FilterChain execution

java.lang.IllegalArgumentException

 at java.nio.Buffer.limit(Buffer.java:275)

 at org.glassfish.grizzly.memory.Buffers.setPositionLimit(Buffers.java:291)

 at org.glassfish.grizzly.memory.HeapBuffer.toByteBuffer0(HeapBuffer.java:1042)

 at org.glassfish.grizzly.memory.HeapBuffer.toStringContent(HeapBuffer.java:863)

 at org.glassfish.grizzly.memory.HeapBuffer.toStringContent(HeapBuffer.java:842)

 at org.glassfish.grizzly.utils.StringDecoder.parseWithLengthPrefix(StringDecoder.java:146)

 at org.glassfish.grizzly.utils.StringDecoder.transformImpl(StringDecoder.java:115)

 at org.glassfish.grizzly.utils.StringDecoder.transformImpl(StringDecoder.java:60)

 at org.glassfish.grizzly.AbstractTransformer.transform(AbstractTransformer.java:73)

 at org.glassfish.grizzly.filterchain.AbstractCodecFilter.handleRead(AbstractCodecFilter.java:71)

 at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)

 at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:284)

 at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:201)

 at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:133)

 at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:112)

 at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)

 at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:539)

 at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)

 at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)

 at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:56)

 at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:137)

 at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:593)

 at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:573)

 at java.lang.Thread.run(Thread.java:745)

 at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)

]]

[2017-06-22T20:23:14.597+0300] [Payara 4.1] [INFO] [] [ru.ritm.idp.connector.IDPConnector] [tid: ThreadID=1487 ThreadName=concurrent/__defaultManagedThreadFactory-Thread-22] [timeMillis: 1498152194597] [levelValue: 800] [[

  -- Connection lost: /10.78.8.82:48041]]

[Mike Croft]

Can you check if you have this property in your domain.xml?

<jvm-options>-Dorg.glassfish.grizzly.DEFAULT_MEMORY_MANAGER=org.glassfish.grizzly.memory.HeapMemoryManager</jvm-options>

If you are upgrading your domain from 163, then it's likely that it won't be there and will need to be added. It was due to a change in Grizzly where they changed the default memory manager, so we have to have this property to change it back.

[Максим Саяпин]

Temporarily used the old version. Thanks, I'll try with this option.

пятница, 21 июля 2017 г., 11:39:20 UTC+3 пользователь Mike Croft написал:

[Максим Саяпин]

Yes, this parameter helped. Many thanks to Mike Croft!

пятница, 21 июля 2017 г., 11:39:20 UTC+3 пользователь Mike Croft написал:

Can you check if you have this property in your domain.xml?