Salesforce

11.7.3.005: "Error handling message from mprosrv" exceptions on Replication Enabled databases

Printable View
« Go Back

Information

 
Title11.7.3.005: "Error handling message from mprosrv" exceptions on Replication Enabled databases
URL NameError-handling-message-from-mprosrv-exceptions-after-applying-Hotfix-11-7-3-005-on-Replication-Enabled-databases
Article Number000165337
EnvironmentProduct: OpenEdge
Version: 11.7.3.005, 11.7.3.006, 11.7.3.007, 11.7.3.008, 11.7.3.009
OS: Windows
Question/Problem Description
After applying Hotfix 11.7.3.005, whenever a replication enabled database is started the following errors and exceptions are written to the admserv.log and ads0.exp files respectively:

 [*UnexpectedError*]   * recorded as exception #xxxxx in file ads0.exp.

and the error in ads0.exp file is:

   Exception at <date & time>: java.lang.NullPointerException
   Message (throw): Error handling message from mprosrv
   Message (excp):  null

When OpenEdge Management is installed, the "Error handling message from mprosrv" exceptions are also thrown every POLL interval. 
Steps to Reproduce
Clarifying Information
Error Message   Exception at <date & time>: java.lang.NullPointerException
   Message (throw): Error handling message from mprosrv
   Message (excp):  null
   Stack Trace:
java.lang.NullPointerException
    at java.lang.String.<init>(String.java:566)
    at com.progress.juniper.admin.JAProtocol.handle(JAProtocol.java:303)
    at com.progress.juniper.admin.ConfigListener.handle(ConfigListener.java:92)
    at com.progress.common.comsock.nio.NIORead.run(NIORead.java:57)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Defect NumberDefect ADAS-8290
Enhancement Number
Cause
Message communication between AdminServer and Replication Agent is not being handled properly for all message codes. In these cases, no data is sent but the AdminServer tries to log this data. This was introduced after a database fix for replication (OCTA-3736). Refer to Article:
Resolution
Upgrade to OpenEdge 11.7.4, 12.0 or later where the AdminServer logs the correct data for RPLS and RPLA communication messages.
Workaround
Start OpenEdge Replication enabled databases unmanaged through the commandline.

Examples:
proserve source -B 10000 -S 4500 -L 1000000 -spin 16000 -pica 8192 -bibufs 30 -aibufs 45 -aistall -DBService replserv
proserve target -S 4501 -B 10000 -L 1000000 -spin 1 -bibufs 50 -Mf 180 -DBService replagent

 
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:06 AM
Powered by