JMS queue and IM/IC Log Analytics Error Messages, JMS queue stopped working.
Last updated on SEPTEMBER 25, 2017
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.
The reason this occured is unknown. But it did occur on a weekend and that suggests that there was some system change that interrupted the JMS queue function and could have corrupted the JMS queue deployment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms