UM delivering old subscribed documents

, ,
1

After restart of the environment last night, UM 9.8 puked on us and started delivering old messages as old as 10 days ago. We are using native pub/sub. Never had any of these issue with Broker. Now UM is sitting at constant 12% CPU and filling 100MB log files every 30 secs with Null pointer exceptions. This is the log lines during startup, I could quickly capture before it filled the log files and rolled it over.

[Mon Dec 19 16:31:36 EST 2016],Startup: Setting automatic maintenance for E:\webMethods98FMA\UniversalMessaging\server\fmaprodumserver\data\namedsubqueues\wm\is\PtcPleBillingTmFmaStg01\docs\abcChargesProc\docStartAbcChargesCust\NamedSubscriber191ba52f49ca02f77.mem
[Mon Dec 19 16:31:36 EST 2016],Startup: Setting automatic maintenance for E:\webMethods98FMA\UniversalMessaging\server\fmaprodumserver\data\namedsubqueues\wm\is\PtcGlbBillingTmToFma01\docs\docGBFMLBBWSStartTrans\NamedSubscriber198d14b1cb43eb827.mem
[Mon Dec 19 16:31:36 EST 2016],Startup: Recovering any uncommitted events from Queues
[Mon Dec 19 16:31:36 EST 2016],Startup: Recovering any uncommitted events from clustered Queues
[Mon Dec 19 16:31:36 EST 2016],Startup: Loading and initialising additionally supported wire protocols

[Mon Dec 19 16:31:36 EST 2016],class java.lang.NullPointerException
java.lang.NullPointerException
at com.pcbsys.nirvana.server.store.cUnCommittedEventManager$nEventRepublisher.run(cUnCommittedEventManager.java:795)
at com.pcbsys.foundation.threads.fThread.localRun(fThread.java:213)
at com.pcbsys.foundation.threads.hThread.run(hThread.java:93)
at java.lang.Thread.run(Thread.java:745)

[Mon Dec 19 16:31:36 EST 2016],class java.lang.NullPointerException
java.lang.NullPointerException
at com.pcbsys.nirvana.server.store.cUnCommittedEventManager$nEventRepublisher.run(cUnCommittedEventManager.java:795)
at com.pcbsys.foundation.threads.fThread.localRun(fThread.java:213)
at com.pcbsys.foundation.threads.hThread.run(hThread.java:93)
at java.lang.Thread.run(Thread.java:745)

2

Hi,

this is a known issue and it is resolved in UM 9.8 Fix 9 (and higher). Please apply that UM server fix and the associated UM client, shared lib and common bundle fix to IS.

3

Which one is the known issue that is fixed in Fix 9 and higher, Null pointer exception or re-delivery of the old acknowledged documents? Thanks!

4

The old document redelivery is what is in that fix, but the NPE may be related, as your error messages relate to cUnCommittedEventManager$nEventRepublisher