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.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web8

  • via Unknown by Bik*********L,
  • via Unknown by Navin Sidhaye,
  • via Unknown by Anuj Vohra,
  • Stack trace

    • 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(FEManager.java:289) at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548) at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961) at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184) at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287) at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59) at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192) at weblogic.jms.client.JMSSession.createTopic(JMSSession.java:2427) at oracle.tip.adapter.jms.JMS.JMSDestination.getTopic(JMSDestination.java:108) at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:547) at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497) at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342) at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:914) at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:864) at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163) at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:106)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.