MaxMessageSize limit reached while building workspace cache (Doc ID 1268594.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 5.5.11 to 10.3
Information in this document applies to any platform.

Symptoms

What is the cause of this exception that we get?

Caused by: Incoming message of size: '1000008' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'

fuego.papi.impl.EngineExecutionException: Server execution error.
at fuego.papi.impl.j2ee.EJBProcessControlHandler.doInvoke(EJBProcessControlHandler.java:153)
at fuego.papi.impl.j2ee.EJBProcessControlHandler.invoke(EJBProcessControlHandler.java:66)
at $Proxy11.getInstancesForCache(Unknown Source)
at fuego.papi.impl.j2ee.J2EEInstanceCacheFiller.beginFill(J2EEInstanceCacheFiller.java:60)
at fuego.papi.impl.InstanceCache.checkFill(InstanceCache.java:311)
at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.java:514)
at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms