[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport
10:14 a.m.
[
https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-2835:
------------------------------------
I thought that was the issue, but it ends with a time out issue, that appears, probably,
to be mac related.
Feb 3, 2014 4:10:54 PM org.teiid.net.socket.SocketServerConnectionFactory$1 run
WARNING: Error performing keep-alive ping
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at java.io.DataInputStream.readInt(DataInputStream.java:370)
at
org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:97)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:343)
at
org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:109)
at
org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:116)
at
org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:96)
at
org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:271)
at
org.teiid.net.socket.SocketServerConnectionFactory$1.run(SocketServerConnectionFactory.java:201)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Feb 3, 2014 4:10:55 PM org.teiid.logging.JavaLogger log
WARNING: TEIID40114 Unhandled exception, closing client instance: Connection reset by
peer
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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3929
days inactive
3929
days old
0 comments
1 participants
participants (1)
-
Van Halbert (JIRA)