Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

weblogic.socket.MaxMessageSizeExceededException from T3S in SSLFIlter

10 views
Skip to first unread message

Timothy Farrell

unread,
Feb 14, 2002, 10:49:28 AM2/14/02
to
We are seeing stack traces that complain about 10MB message sizes on the
T3S protocol stream. These stack traces go to standard out and are not
recorded in the Weblogics Server all.log and they are not time stamped.
Is this a bug in the native code of the socket muxer perhaps ?

We are running WL 6.1 sp1 with Oracle 8i using the thin Oracle 8.1.7
driver all running in a Sun 1.3.1_02 JVM on Red Hat Linux release 6.2
(Zoot). We do send a lot of JMS messages between the client and the
server over T3S, most of these messages are pretty small ( <100 bytes ).
Any ideas or help or patches appreciated, thanks.


weblogic.socket.MaxMessageSizeExceededException: [Incoming message of
size 10000022 bytes exceeds the configured maximum of 10000000 bytes for
T3S protocol]
at
weblogic.socket.SSLFilter.incrementBufferOffset(SSLFilter.java:160)
at
weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:528)
at
weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:446)
at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:378)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Tim Farrell Laurel Networks, Inc

Tom Barnes

unread,
Feb 20, 2002, 10:50:22 AM2/20/02
to Timothy Farrell
Do contact customer support.
Meanwhile tune up your "MaxT3MessageSize" setting on your server
to 2000000000 (the max value) - which should defer the problem
by a factor of 200. Or give https a shot instead (this is of course slower).
0 new messages