Symptom

Large files to process. JMS Queue Adapter throws MaxMessageSizeExceededException Error

ERROR <JmsQueueAdapterServerImpl-MY_JMS_RECEIVE_ADAPTER-2008500276>
From ExceptionListener:
ERROR [1355758430921] java.lang.Exception:
weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message
of size: '10000080' bytes exceeds the configured maximum of: '10000000'
bytes for protocol: 't3'
ERRORDTL
[1355758430921]weblogic.jms.common.LostServerException:
java.lang.Exception: weblogic.rjvm.PeerGoneException: ; nested
exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message
of size: '10000080' bytes exceeds the configured maximum of: '10000000'
bytes for protocol: 't3'
at
weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:
1436)
at
weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapp
erState.java:692)
at
weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(Dispat
cherWrapperState.java:617)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at
weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:2
1)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: java.lang.Exception: weblogic.rjvm.PeerGoneException: ;
nested exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message
of size: '10000080' bytes exceeds the configured maximum of: '10000000'
bytes for protocol: 't3'
at
weblogic.messaging.dispatcher.DispatcherWrapperState.onDisconnect(Dispat
cherWrapperState.java:396)
at
weblogic.rjvm.RJVMImpl$DisconnectEventDeliverer.run(RJVMImpl.java:1647)
... 3 more