JMS queue and IM/IC Log Analytics Error Messages, JMS queue stopped working.
(Doc ID 2120702.1)
Last updated on JANUARY 09, 2019
Applies to:Oracle Knowledge - Version 8.5 and later
Information in this document applies to any platform.
JMS queue is not accepting Analytics events and their are many errors in the IM/IC logs.
SEVERE: Caught:weblogic.jms.common.JMSException: One-phase transaction BEA1-47E3AAA55A4B8889E697-574C53746F72655F70726F645F646F6D61696E5F5175657565 for resource WLStore_prod_domain_Queue is in an unknown state.:commit failure, Could not log to the JMS queue for [List of 1 events]
weblogic.jms.common.JMSException: One-phase transaction BEA1-47E3AAA55A4B8889E697-574C53746F72655F70726F645F646F6D61696E5F5175657565 for resource WLStore_prod_domain_Queue is in an unknown state.:commit failure
Caused by: weblogic.store.PersistentStoreException: weblogic.store.PersistentStoreFatalException: [Store:280032]The persistent store suffered a fatal error and it must be re-opened
... 20 more
This can cause slowness on the IM/IC servers and the JMS routing is not working.
If the JMS queue has never been working before see this KM first to make sure that the JMS queue and event router are installed correctly.
Tips for enabling (or disabling) the new Analytics JMS event logging for Search, IM/IC/IMWS and AnswerFlow instances? (Doc ID 1507510.1)
The Event router or the JMS queue can stop working. If there are weblogic procedures that interupt the JMS queue working or a patch was installed and the Event router is not deployed correctly the queue or router could stop functioning.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document