Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Maximum message size exceeds for protocol: t3

629349Oct 13 2010 — edited Dec 11 2010

Hi,
I have a scenario where in ODI job picks an XML message from the weblogic JMS queue and loads a database table.

For payload, <=10 MB, the underlying protocol t3 is able to dispatch the message from the queue.
But then for payloads >10MB, I get the below error.

7000 : null : java.sql.SQLException: weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: 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'

Despite changing this values on the server side from servers-->myserver-->protocol to <custom size>, it didn't seem to help.

A couple of blogs state to change the pass the client java args -DWeblogic.MaxMessageSize to <custom size>,

How would I do that in ODI, I am using wlfullclient.jar for connecting to weblogic.
Any insight on this would really help.

Thanks,
Manoj Nair.

Edited by: ManojNair, Wipro on Oct 13, 2010 3:50 AM

Locked Post

New comments cannot be posted to this locked post.

Locked on Jan 8 2011

Added on Oct 13 2010

#business-intelligence-applications, #data-integrator, #odi, #system-management-and-integration, #weblogic

2 comments

1,506 views