Announcement

Collapse

Mirth Connect 4.1.0 Released!

Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several 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

JMS Writer for 1.4

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

  • JMS Writer for 1.4

    Hi,

    I configured JBoss Messaging and I am trying to setup the JMS Writer. I configured the channel with

    Provider URL: jnp://localhost:1099
    Initial Context Factory: org.jnp.interfaces.NamingContextFactory
    Factory JNDI Name: org.jboss.namingrg.jnp.interfaces
    Destination: queue/testQueue

    However when I deploy the channel I get the stack trace below. Do I need some jars on Mirths classpath?

    Mirth 1.4.0 (March 22, 2007) server successfully started: Tue Apr 03 00:08:05 ED
    T 2007
    This product includes software developed by SymphonySoft Limited (http://www.sym
    phonysoft.com) and its contributors.
    Running Java 1.6.0 on Windows XP (5.1, x86)
    WARN 2007-04-03 00:10:25,796 [Thread-0] com.webreach.mirth.server.Mirth: Error
    deploying channels.
    org.mule.config.ConfigurationException: MuleManager Failed to initialise (org.mu
    le.config.ConfigurationException)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXm
    lConfigurationBuilder.java:196)
    at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:163)
    at com.webreach.mirth.server.Mirth.restartMule(Mirth. java:145)
    at com.webreach.mirth.server.Mirth.run(Mirth.java:101 )
    Caused by: org.mule.config.ConfigurationException: MuleManager Failed to initial
    ise
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXm
    lConfigurationBuilder.java:209)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXm
    lConfigurationBuilder.java:194)
    ... 3 more
    Caused by: org.mule.umo.lifecycle.InitialisationException: Failed to create Jms
    Connector
    at com.webreach.mirth.server.mule.providers.jms.JmsCo nnector.doInitialis
    e(JmsConnector.java:137)
    at org.mule.providers.AbstractConnector.initialise(Ab stractConnector.jav
    a:233)
    at org.mule.MuleManager.initialiseConnectors(MuleMana ger.java:776)
    at org.mule.MuleManager.initialise(MuleManager.java:6 52)
    at org.mule.MuleManager.start(MuleManager.java:721)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXm
    lConfigurationBuilder.java:207)
    ... 4 more
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: org
    .jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundE
    xception: org.jnp.interfaces.NamingContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(U nknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unkn own Source)
    at javax.naming.InitialContext.init(Unknown Source)
    at javax.naming.InitialContext.<init>(Unknown Source)
    at com.webreach.mirth.server.mule.providers.jms.JmsCo nnector.initJndiCon
    text(JmsConnector.java:159)
    at com.webreach.mirth.server.mule.providers.jms.JmsCo nnector.doInitialis
    e(JmsConnector.java:116)
    ... 9 more
    Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFac
    tory
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at com.sun.naming.internal.VersionHelper12.loadClass( Unknown Source)
    ... 15 more

  • #2
    Re: JMS Writer for 1.4

    You will need to drop all of the JMS jars into the "Custom" folder (under lib) in the main Mirth directory. Be sure to restart the server.

    -Chris
    Chris Lang

    Comment


    • #3
      Re: JMS Writer for 1.4

      Hello,

      can you please tell me if your JMS-Writer is now working?
      Because i have problems too.

      Thanks
      Jörg Orlowski

      Comment

      Working...
      X