[teiid-issues] [JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport
Steven Hawkins (JIRA)
issues at jboss.org
Thu Aug 21 11:37:59 EDT 2014
[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins resolved TEIID-2835.
-----------------------------------
Resolution: Out of Date
> After switch to use io.netty, getting exception in TestJDBCSocketTransport
> --------------------------------------------------------------------------
>
> Key: TEIID-2835
> URL: https://issues.jboss.org/browse/TEIID-2835
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7
> Environment: Running build on mac
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> When building off of master (which I see there's been a change to io.netty), I get the following error:
> Running org.teiid.transport.TestJDBCSocketTransport
> Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log
> SEVERE: TEIID40113 Unhandled exception, aborting operation
> org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded
> at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417)
> at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405)
> at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320)
> at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with:
> =========== DEFAULT ===========2097152
> =========== Int Max ===========2147483647
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the teiid-issues
mailing list