Troubleshooting
Problem
An error is returned when 'NonPagedQueryMaxSize' in FileNet Enterprise Manager is set to a large value, for example, 100,000 bytes, by other applications for better throughput, such as bulk declaration, and you are running AutoDestroy on WebLogic 10.3 and Oracle 11g using EJB transport.
Symptom
When the Content Engine 'NonPagedQueryMaxSize' value set in FileNet Enterprise Manager, is set to a large number, like 100,000 bytes, and you configure Disposition Sweep to use EJB transport and use WebLogic 10.3 and Oracle 11g, and you run auto destroy, you will get the following error:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
Resolving The Problem
There are two workarounds that can be made to correct this issue:
Go to FileNet Enterprise Manager in Content Engine and reduce the value of the 'NonPagedQueryMaxSize' to less than 50,000 bytes.
or
Modify the disposition sweep batch file (.sh or .bat) to add the following parameter:
-Dweblogic.MaxMessageSize=20000000
For example, in the RecordsManagerSweep.bat file, you can add the parameter as in the following example:
:AutoDelSweep
%JAVA_EXE% -cp %CLASS_PATH% -Xmx1024m %TOOL_ARGS% -Dweblogic.MaxMessageSize=20000000 -Dwasp.location=../CommonFiles/CE_API/wsi %MainClass% AutoDelete %3 %4 %5 %6 %7
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21506498