MainServer1's log file grows rapidly (into the tens of GB) due to a repeating NullPointerException tied to IfsWebStreamsTopicBean/JMS Streams messages, eventually filling the disk — what's actually causing this and how is it stopped?

All FAQ questions / Platform, Aurena, and customization

Answer

This is typically caused by failed JMS Stream messages being retried indefinitely — check the WebLogic Admin Console for any failed messages sitting in the Streams JMS topic and delete them first. The more durable fix is changing the 'Redelivery Limit' setting on that topic: in the Middleware Server Admin Console, go to Common > JMS Modules > StreamJMSModule > StreamsJMSTopic, and change Redelivery Limit from its default of -1 (meaning unlimited retries) to a bounded value like 5, then restart the Middleware Server. If the excessive logging continues after that, stop MainServer1, delete the .dat files under wls_domain\<INSTANCE_NAME>\servers\MainServer1\data\store\default and ...\data\store\diagnostics, then restart — this clears out the underlying persistent store backing the stuck messages.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions