MaxMessageSizeExceededException Error in connection with JMS queue

Technote (troubleshooting)


Problem(Abstract)

JMS Queue Adapter throws MaxMessageSizeExceededException Error

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


Cause

This error actually comes from Weblogic code rather than from Sterling Integrator. Below are
some articles that should be reviewed together with the Weblogic administrator.
http://www.otmfaq.com/forums/f28/weblogic-socket-maxmessagesizeexceededexception-3395/
http://forums.oracle.com/forums/thread.jspa?threadID=841226

Diagnosing the problem

This error actually comes from Weblogic rather than from Sterling Integrator. Below are
some articles that should be reviewed together with the Weblogic administrator.

http://www.otmfaq.com/forums/f28/weblogic-socket-maxmessagesizeexceededexception-3395/
http://forums.oracle.com/forums/thread.jspa?threadID=841226

Resolving the problem

The following third party jars should be imported into the dynamicclasspath.cfg in SI using the
install3rdParty script:
wlclient.jar
weblogic.jar

For example, use the command syntax
./install3rdParty.sh weblogic 10 -j /MyFilePath/weblogic/wlclient.jar
./install3rdParty.sh weblogic 10 -j /MyFilePath/weblogic/weblogic.jar

Please make a backup of the dynamicclasspath.cfg file before running the
install3rdParty script.

Rate this page:

(0 users)Average rating

Document information


More support for:

Sterling B2B Integrator
Adapters

Software version:

5.2.3

Operating system(s):

All

Reference #:

1621970

Modified date:

2013-01-14

Translate my page

Machine Translation

Content navigation