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

Routing Exceptions in 1.7 channel

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

  • Routing Exceptions in 1.7 channel

    I'm getting a set of Java exceptions in one of my channels - looks like it's trying to route to a null endpoint. (Channel receives LLP and sends the transformed/filtered message to several other channels.) This happened in 36 out of 1864 messages today... The tail end of the error made me think I had a typo somewhere, but I can't find anything wrong.

    This is on 1.7.0.3285. Don't remember seeing anything like this while testing 1.6 and the 1.7 betas, but I could be wrong.

    Any ideas?

    Thanks, Mike

    ERROR 2008-02-01 20:39:40,507 [6ab65093-6a3c-473f-9329-1c87ef6a0376_source_connector._mllpEndpoint#168929 3931.receiver.9] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: 6ab65093-6a3c-473f-9329-1c87ef6a0376: org.mule.umo.routing.RoutingException: Failed to route event via endpoint: null. Message payload is of type: com.webreach.mirth.model.MessageObject
    org.mule.umo.routing.RoutingException: Failed to route event via endpoint: null. Message payload is of type: com.webreach.mirth.model.MessageObject
    at org.mule.routing.outbound.OutboundMessageRouter.ro ute(OutboundMessageRouter.java:84)
    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:244)
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$TcpWorker.processHL7Data(MllpMessageReceiver. java:440)
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$TcpWorker.processData(MllpMessageReceiver.jav a:416)
    at com.webreach.mirth.connectors.mllp.MllpMessageRece iver$TcpWorker.run(MllpMessageReceiver.java:340)
    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(Thread.java:595)
    Caused by: org.mule.umo.routing.CouldNotRouteOutboundMessageE xception: Failed to route event via endpoint: ImmutableMuleEndpoint{connector=com.webreach.mirth [email protected], endpointUri=vm://1dce3c4f-8c03-4563-a1a8-6cc2c660b4a3, transformer=Transformer{name='6ab65093-6a3c-473f-9329-1c87ef6a0376_destination_1_transformer', returnClass=false, returnClass=false, sourceTypes=[]}, name='_vmEndpoint#-1661793906', type='sender', properties={}, transactionConfig=org.mule.impl.MuleTransactionCon [email protected], filter=null, deleteUnacceptedMessages=false, initialised=true, securityFilter=null, synchronous=true, initialState=started, createConnector=0}. Message payload is of type: com.webreach.mirth.model.MessageObject
    at org.mule.routing.outbound.FilteringMulticastingRou ter.route(FilteringMulticastingRouter.java:111)
    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)
    ... 16 more
    Caused by: org.mule.umo.provider.DispatchException: Failed to route event via endpoint: ImmutableMuleEndpoint{connector=com.webreach.mirth [email protected], endpointUri=vm://1dce3c4f-8c03-4563-a1a8-6cc2c660b4a3, transformer=Transformer{name='6ab65093-6a3c-473f-9329-1c87ef6a0376_destination_1_transformer', returnClass=false, returnClass=false, sourceTypes=[]}, name='_vmEndpoint#-1661793906', type='sender', properties={}, transactionConfig=org.mule.impl.MuleTransactionCon [email protected], filter=null, deleteUnacceptedMessages=false, initialised=true, securityFilter=null, synchronous=true, initialState=started, createConnector=0}. Message payload is of type: com.webreach.mirth.model.MessageObject
    at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:179)
    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)
    ... 19 more
    Caused by: org.mule.umo.transformer.TransformerException:
    CHANNEL: SLAB Results
    CONNECTOR: Client HL7
    SCRIPT SOURCE:
    LINE NUMBER: 1
    DETAILS: TypeError: error: Unexpected character encountered (lex state 9): '1' (com.webreach.mirth.server.MirthJavascriptTransfor merException)
    at com.webreach.mirth.server.mule.transformers.JavaSc riptTransformer.evaluateScript(JavaScriptTransform er.java:406)
    at com.webreach.mirth.server.mule.transformers.JavaSc riptTransformer.transform(JavaScriptTransformer.ja va:307)
    at org.mule.transformers.AbstractEventAwareTransforme r.doTransform(AbstractEventAwareTransformer.java:4 8)
    at org.mule.transformers.AbstractTransformer.transfor m(AbstractTransformer.java:197)
    at org.mule.impl.MuleEvent.getTransformedMessage(Mule Event.java:251)
    at com.webreach.mirth.server.controllers.MessageObjec tController.getMessageObjectFromEvent(MessageObjec tController.java:507)
    at com.webreach.mirth.connectors.vm.VMMessageDispatch er.doSend(VMMessageDispatcher.java:249)
    at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:166)
    ... 23 more
    Caused by: com.webreach.mirth.server.MirthJavascriptTransform erException:
    CHANNEL: SLAB Results
    CONNECTOR: Client HL7
    SCRIPT SOURCE:
    LINE NUMBER: 1
    DETAILS: TypeError: error: Unexpected character encountered (lex state 9): '1'
    at com.webreach.mirth.server.mule.transformers.JavaSc riptTransformer.evaluateScript(JavaScriptTransform er.java:397)
    ... 30 more



    Post edited by: mnowlin, at: 02/02/2008 01:27

  • #2
    Re:Routing Exceptions in 1.7 channel

    Did you export, install a fresh copy of Mirth, and then import all of your channels? if so, some of the channels may have new unique ID's. Because of this, you will have to go into your channels, reselect the channel it is supposed to be routing to, and resave.
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare

    sigpic

    Comment


    • #3
      Re:Routing Exceptions in 1.7 channel

      Just did the export/reinstall/import process (even wiped and rebuilt the PG database), then the channel reselection as you suggested.

      (I was about to say something like "it's processed 1000+ messages w/o error" but...)

      I just looked back at it - getting the same errors.... Grrrrr....

      I'll poke at it some more - will try retouching pretty much everything.

      Thanks - Mike

      Comment


      • #4
        Re:Routing Exceptions in 1.7 channel

        Look at this error:

        Code:
        CHANNEL: SLAB Results
        CONNECTOR: Client HL7
        SCRIPT SOURCE:
        LINE NUMBER: 1
        DETAILS: TypeError: error: Unexpected character encountered (lex state 9): '1'
        There is some error parsing the message (possibly an XML conversion issue). What type of connector is Client HL7?
        Chris Lang

        Comment

        Working...
        X