Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Error while connecting to JMS topic

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error while connecting to JMS topic

    Hi all,

    I am trying to connect to JMS topic and writer messages to the same.
    My JMS writer configurations are:

    Provider URL: jnp://localhost:2099
    Initial Context Factory: org.jnp.interfaces.NamingContextFactory
    Connection Factory: java:/ConnectionFactory

    Destination: topic/testTopic


    But I get the following error when I deploy the channel:

    [2008-06-28 13:23:07,140] ERROR (org.mule.impl.DefaultComponentExceptionStrategy:9 5): Caught exception in Exception Strategy for: a5e73624-80ed-4d2c-88af-0bb30cfe6e1c: org.jboss.mq.SpyJMSException: Cannot get the Queue from the provider; - nested throwable: (javax.jms.JMSException: This destination does not exist !)
    org.jboss.mq.SpyJMSException: Cannot get the Queue from the provider; - nested throwable: (javax.jms.JMSException: This destination does not exist !)
    at org.jboss.mq.SpyConnection.createQueue(SpyConnecti on.java:258)
    at org.jboss.mq.SpySession.createQueue(SpySession.jav a:783)
    at com.webreach.mirth.connectors.jms.Jms11Support.cre ateDestination(Jms11Support.java:131)
    at com.webreach.mirth.connectors.jms.JmsMessageDispat cher.dispatchMessage(JmsMessageDispatcher.java:126 )
    at com.webreach.mirth.connectors.jms.JmsMessageDispat cher.doSend(JmsMessageDispatcher.java:260)
    at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:166)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:191)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:130)
    at org.mule.routing.outbound.AbstractOutboundRouter.s end(AbstractOutboundRouter.java:85)
    at org.mule.routing.outbound.FilteringMulticastingRou ter.route(FilteringMulticastingRouter.java:89)
    at org.mule.routing.outbound.OutboundMessageRouter$1. doInTransaction(OutboundMessageRouter.java:78)
    at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:48)
    at org.mule.routing.outbound.OutboundMessageRouter.ro ute(OutboundMessageRouter.java:82)
    at org.mule.impl.model.DefaultMuleProxy.onCall(Defaul tMuleProxy.java:247)
    at org.mule.impl.model.seda.SedaComponent.doSend(Seda Component.java:209)
    at org.mule.impl.model.AbstractComponent.sendEvent(Ab stractComponent.java:277)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:201)
    at org.mule.routing.inbound.InboundMessageRouter.send (InboundMessageRouter.java:161)
    at org.mule.routing.inbound.InboundMessageRouter.rout e(InboundMessageRouter.java:128)
    at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR eceiver.java:493)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:272)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:231)
    at com.webreach.mirth.connectors.file.FileMessageRece iver.processFile(FileMessageReceiver.java:236)
    at com.webreach.mirth.connectors.file.FileMessageRece iver.poll(FileMessageReceiver.java:138)
    at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:118)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
    at java.lang.Thread.run(Unknown Source)Caused by: javax.jms.JMSException: This destination does not exist !
    at org.jboss.mq.server.JMSDestinationManager.createQu eue(JMSDestinationManager.java:690)
    at org.jboss.mq.server.JMSServerInterceptorSupport.cr eateQueue(JMSServerInterceptorSupport.java:149)
    at org.jboss.mq.server.TracingInterceptor.createQueue (TracingInterceptor.java:314)
    at org.jboss.mq.server.JMSServerInvoker.createQueue(J MSServerInvoker.java:149)
    at org.jboss.mq.il.uil2.ServerSocketManagerHandler.ha ndleMsg(ServerSocketManagerHandler.java:111)
    at org.jboss.mq.il.uil2.SocketManager$ReadTask.handle Msg(SocketManager.java:361)
    at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java :377)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(PooledExecutor.java:748)
    at java.lang.Thread.run(Thread.java:534)



    But using the same configurations I am able to connect and
    send a message to the topic using a simple JAVA program.

    If I also change to any deployed queue name as destination
    still MIRTH is able to deliver the message to the queue.

    Where am I going wrong. Waiting for reply,


    Thanks in advance,
    Raj.

  • #2
    Re:Error connecting to JMS topic. Any solution???

    Hi all,

    I am not able to find any solution for this problem. I tried using
    the topic name as "//topic:testTopic" rather than "topic/testTopic", as
    suggested in some posts in the forum. Still I am getting the error
    given below.


    ERROR (org.mule.impl.DefaultComponentExceptionStrategy:9 5): Caught exception in Exception Strategy for: a5e73624-80ed-4d2c-88af-0bb30cfe6e1c: org.jboss.mq.SpyJMSException: Cannot get the Topic from the provider; - nested throwable: (javax.jms.JMSException: This destination does not exist !)
    org.jboss.mq.SpyJMSException: Cannot get the Topic from the provider; - nested throwable: (javax.jms.JMSException: This destination does not exist !)
    at org.jboss.mq.SpyConnection.createTopic(SpyConnecti on.java:222)
    at org.jboss.mq.SpySession.createTopic(SpySession.jav a:795)
    at com.webreach.mirth.connectors.jms.Jms11Support.cre ateDestination(Jms11Support.java:137)
    at com.webreach.mirth.connectors.jms.JmsMessageDispat cher.dispatchMessage(JmsMessageDispatcher.java:126 )
    at com.webreach.mirth.connectors.jms.JmsMessageDispat cher.doSend(JmsMessageDispatcher.java:260)
    at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:166)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:191)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:130)
    at org.mule.routing.outbound.AbstractOutboundRouter.s end(AbstractOutboundRouter.java:85)
    at org.mule.routing.outbound.FilteringMulticastingRou ter.route(FilteringMulticastingRouter.java:89)
    at org.mule.routing.outbound.OutboundMessageRouter$1. doInTransaction(OutboundMessageRouter.java:78)
    at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:48)
    at org.mule.routing.outbound.OutboundMessageRouter.ro ute(OutboundMessageRouter.java:82)
    at org.mule.impl.model.DefaultMuleProxy.onCall(Defaul tMuleProxy.java:247)
    at org.mule.impl.model.seda.SedaComponent.doSend(Seda Component.java:209)
    at org.mule.impl.model.AbstractComponent.sendEvent(Ab stractComponent.java:277)
    at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:201)
    at org.mule.routing.inbound.InboundMessageRouter.send (InboundMessageRouter.java:161)
    at org.mule.routing.inbound.InboundMessageRouter.rout e(InboundMessageRouter.java:128)
    at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR eceiver.java:493)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:272)
    at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:231)
    at com.webreach.mirth.connectors.file.FileMessageRece iver.processFile(FileMessageReceiver.java:236)
    at com.webreach.mirth.connectors.file.FileMessageRece iver.poll(FileMessageReceiver.java:138)
    at org.mule.providers.PollingMessageReceiver.run(Poll ingMessageReceiver.java:118)
    at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
    at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
    at java.lang.Thread.run(Unknown Source)Caused by: javax.jms.JMSException: This destination does not exist !
    at org.jboss.mq.server.JMSDestinationManager.createQu eue(JMSDestinationManager.java:690)
    at org.jboss.mq.server.JMSServerInterceptorSupport.cr eateQueue(JMSServerInterceptorSupport.java:149)
    at org.jboss.mq.server.TracingInterceptor.createQueue (TracingInterceptor.java:314)
    at org.jboss.mq.server.JMSServerInvoker.createQueue(J MSServerInvoker.java:149)
    at org.jboss.mq.il.uil2.ServerSocketManagerHandler.ha ndleMsg(ServerSocketManagerHandler.java:111)
    at org.jboss.mq.il.uil2.SocketManager$ReadTask.handle Msg(SocketManager.java:361)
    at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java :377)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(PooledExecutor.java:748)
    at java.lang.Thread.run(Thread.java:534)


    Is anything else needed to be configured in MIRTH so as
    to connect to "topics" rather than "queues". Appreciate any
    help. Thanking in advance,

    Raj.

    Comment


    • #3
      Re:Error connecting to JMS topic. Any solution???

      I can't offer much help, but there is another user who has had some JMS issues. I don't know if he has solved them yet.

      http://www.mirthproject.org/index.ph...d=6704&catid=2
      Jon Bartels

      Zen is hiring!!!!
      http://consultzen.com/careers/
      Talented healthcare IT professionals wanted. Engineers to sales to management.
      Good benefits, great working environment, genuinely interesting work.

      Comment


      • #4
        Re:Error connecting to JMS topic. (Solved)

        Hi all,

        The above problem got solved for me. I just re-installed the MIRTH
        (1.7.1) and the JMS read/write channels are working fine now. I cannot make
        out what was wrong earlier. Please find the sample channles in the thread:

        http://www.mirthproject.org/index.ph...2&id=7494#7494



        regards,
        Raj.

        Post edited by: gshenoy, at: 10/16/2008 03:51

        Comment

        Working...
        X