{"id":4574,"date":"2015-04-23T17:05:30","date_gmt":"2015-04-23T09:05:30","guid":{"rendered":"http:\/\/rmohan.com\/?p=4574"},"modified":"2015-04-23T17:05:30","modified_gmt":"2015-04-23T09:05:30","slug":"t3-protocol","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=4574","title":{"rendered":"T3 Protocol"},"content":{"rendered":"

Handling weblogic T3 protocol message size issues<\/p>\n

Do not be surprised when you see an error like below in weblogic server logs.<\/p>\n

Incoming message of size: ‘10000080’ bytes exceeds the configured maximum of: ‘10000000’ bytes for protocol: ‘t3<\/strong><\/p>\n

In nutshell, above error happens when weblogic server is trying to process a message of size more than 10MB.<\/p>\n

Most of the times it is JMS message processing of course, it\u00a0 need not be always JMS.<\/p>\n

First lets understand what is T3 and how it works.<\/p>\n

T3 is a\u00a0proprietary communication protocol being\u00a0used by WLS to handle data traffic between java to java applications or JVM to JVM<\/p>\n

WLS has a mechanism to keep track of JVMs with which it is connected and always creates just one connection to the connected JVM.<\/p>\n

These connected JVMs could be server JVM to server JVM or client JVM to server JVM.<\/p>\n

For example, if a Java client accesses JSP page\u00a0 and a JDBC connection pool on WebLogic Server, a single network connection is established between the WebLogic Server JVM and the client JVM.\u00a0This eliminates the need of creating multiple connections and managing them.T3 protocol also does multiplexing data\u00a0packets invisibly\u00a0on the single connection<\/p>\n

Features of T3 protocol<\/p>\n