weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.

Oracle Community | Bik*********L | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Durable Subscription

    Oracle Community | 6 years ago | Bik*********L
    weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
  2. 0

    Queue look up failure.

    Google Groups | 2 decades ago | Navin Sidhaye
    weblogic.jms.common.JMSException: Invalid destination name: weblogic.jms.MyJ MSQueue
  3. 0

    JMS and Clusters

    Google Groups | 2 decades ago | Anuj Vohra
    weblogic.jms.common.JMSException: Invalid destination name: STATUS_NOTIFICATION
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Error creating Destination from within a Stateless (Unable to resolve 'weblogic.jms.backend.jms' )

    Oracle Community | 1 decade ago | 3004
    weblogic.jms.common.JMSException: Error creating destination
  6. 0

    JMS failover

    Oracle Community | 1 decade ago | 3004
    weblogic.jms.common.JMSException: Invalid destination name: >javax.jms.testQ > at >weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:194) > >

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. weblogic.jms.common.JMSException

      [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.

      at weblogic.jms.frontend.FEManager.destinationCreate()
    2. weblogic.jms.frontend
      FEManager.invoke
      1. weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:289)
      2. weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
      2 frames
    3. weblogic.messaging.dispatcher
      DispatcherImpl.dispatchSyncNoTran
      1. weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
      2. weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
      3. weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
      3 frames
    4. weblogic.jms.dispatcher
      DispatcherAdapter.dispatchSyncNoTran
      1. weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
      1 frame
    5. weblogic.jms.client
      JMSSession.createTopic
      1. weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
      2. weblogic.jms.client.JMSSession.createTopic(JMSSession.java:2427)
      2 frames
    6. oracle.tip.adapter
      JmsEndpoint.run
      1. oracle.tip.adapter.jms.JMS.JMSDestination.getTopic(JMSDestination.java:108)
      2. oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:547)
      3. oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
      4. oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
      5. oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:914)
      6. oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:864)
      7. oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
      7 frames
    7. oracle.integration.platform
      WorkManagerExecutor$1.run
      1. oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:106)
      1 frame