Mirth Connect 4.3.0 Released!

Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

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

  • Filter
  • Time
  • Show
Clear All
new posts

  • JMS Writer for 1.4


    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 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 (
    at er.configure(MuleXm
    at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:163)
    at com.webreach.mirth.server.Mirth.restartMule(Mirth. java:145)
    at )
    Caused by: org.mule.config.ConfigurationException: MuleManager Failed to initial
    at er.configure(MuleXm
    at er.configure(MuleXm
    ... 3 more
    Caused by: org.mule.umo.lifecycle.InitialisationException: Failed to create Jms
    at com.webreach.mirth.server.mule.providers.jms.JmsCo nnector.doInitialis
    at org.mule.providers.AbstractConnector.initialise(Ab stractConnector.jav
    at org.mule.MuleManager.initialiseConnectors(MuleMana
    at org.mule.MuleManager.initialise( 52)
    at org.mule.MuleManager.start(
    at er.configure(MuleXm
    ... 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
    at com.webreach.mirth.server.mule.providers.jms.JmsCo nnector.doInitialis
    ... 9 more
    Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFac
    at$ Source)
    at Method)
    at 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 Lang


    • #3
      Re: JMS Writer for 1.4


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

      Jörg Orlowski