After Purge is Run, JMS Queues Not Starting with Javax.jms.JMSException: Destination Not Found

(Doc ID 2231254.1)

Last updated on FEBRUARY 22, 2018

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


On : version, Fabric

After purge was run and SOA servers restarted, JMS queues are not starting as expected.

The error below is seen in soa_server1-diagnostic.log

[2017-02-06T22:10:06.487-05:00] [SOA_Server1] [WARNING] [SDP-25730] [oracle.sdpinternal.messaging.jms.QueueWorker] [tid: DaemonWorkThread: '0' of WorkManager: 'default'] [userId: ] [ecid: 77567cad-59c4-4da0-84ef-08fb4bb835ed-00000d6b,0] [APP: usermessagingserver] QueueWorker got exception.[[
javax.jms.JMSException: Destination not found UMSJMSSystemResource!dist_OraSDPM/Queues/OraSDPMEngineSndQ1_auto
  at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(
  at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(
  at weblogic.jms.client.JMSSession.consumerCreate(
  at weblogic.jms.client.JMSSession.setupConsumer(

The error below is seen in soa_server1.log

####<Feb 6, 2017 3:46:58 PM EST> <Emergency> <Store> <SOA_Server1> <Thread-49> <> <> <f97de91f-5e3b-4a26-97ea-09809f2c549b-00000002> <1486414018201> <BEA-280060> <The store "JMSFileStore_1" encountered a fatal error, and it must be shut down: [Store:280029]The store record 535,667 could not be found. [Store:280029]The store record 535,667 could not be found.



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