weblogic.socket.MaxMessageSizeExceededException in OSB11g

Problem: Whenever we have a long running two-way OSB-DB API call...it takes much time to complete. It will show us the weblogic.socket.MaxMessageSizeExceededException in sbconsole debug console.
Cause: weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'



Solution:

1. Go to servers--->protocols--->general--->max message size--->change the value to sufficient memory (Do this for both the admin and the osb/soa)
Note: Do it for all the OSB/SOA nodes in the cluster

2. Go to servers--->configuration--->server start--->arguments--->-Dweblogic.MaxMessageSize = 20000000

3. Restart all the servers.

Hope this will help you to resolve this issue.

Comments

Post a Comment

Popular posts from this blog

Difference between Route, Service Callout, Publish

When you are first starting with OSB it can be a little tricky to determine when to use a Route, Service Callout or a Publish node.  All three can be used to call either a Business service or a local Proxy service.  You can use the following lists to determine which will best fit your needs. Route Last node in request processing.  It can be thought of as a bridge between request pipeline processing and the response pipeline processing. You can only execute one route in your Proxy Service. Can only be created in a route node. OSB will wait for the Route call to finish before continuing to process. If you are calling a Business service  and  you specify  Best Effort  for QoS (Quality of Service), then OSB will release the thread it is holding while the business service executes. If you are calling a Business service  and  you specify  Exactly Once  or  At Least Once  for QoS, then OSB will hold onto the thread while the business service executes. If you are calling a l
Read more

OSB actions in proxy service

Image
In this post we will see about different types of actions to message flows using the Oracle Service Bus Administration Console, such as route, publish, service callout, transport headers, conditional actions, error actions, and message transformation actions. Actions are the elements of pipeline stages, error handler stages, route nodes, and branch nodes that define how messages are to be defined as they flow through a pipeline            Action                           Description                     Dynamic Publish Publish a message to a service identified by an XQuery expression                          Publish Publish a message to a statically specified service.                        Publish Table Publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publis
Read more

XQuery functions that supported by OSB

NAMESPACES ------------------------------------------------------------------------ xml=http://www.w3.org/XML/1998/namespace fn=http://www.w3.org/2004/07/xpath-functions op=http://www.w3.org/2004/07/xpath-operators err=http://www.w3.org/2004/07/xqt-errors fn-bea=http://www.bea.com/xquery/xquery-functions op-bea=http://www.bea.com/xquery/xquery-operators dt-bea=http://www.bea.com/xquery/xquery-datatypes var-bea=http://www.bea.com/xquery/xquery-variables xf-aug02=http://www.w3.org/2002/08/xquery-function op-aug02=http://www.w3.org/2002/08/xquery-operators xs=http://www.w3.org/2001/XMLSchema xsd=http://www.w3.org/2001/XMLSchema xdt=http://www.w3.org/2004/07/xpath-datatypes local=http://www.w3.org/2004/07/xquery-local-functions declare default function namespace "http://www.w3.org/2004/07/xpath-functions XQUERY FUNCTIONS ------------------------------------------------------------------------ fn:node-name($arg as node()?) as xs:QName? fn:
Read more