Announcement

Collapse
No announcement yet.

Bad ACK messages

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

  • Bad ACK messages

    These show up on every other message. Somehow are related to the combination of preprocessor statements in use. If all a represent the channels works fine but every other ACK is bad. If the statements to remove the formatter routine ID are not in place the channel blows. If the conversion to pipes and carets are not in there is a different error. See section from log file at end for example of bad ACKs returned to sending system.

    Preprocessor statements:
    // Modify the message variable below to pre process data

    // removesw version 41 formatter id
    message = message.replace(/;41:/g,':'
    // removes version 42 formatter id
    message = message.replace(/;42:/g,':'
    // change all semicolons to ^
    message = message.replace(/\;/g, '^'

    // change all colons to pipes
    message = message.replace(/\:/g, '|'
    return message;

    Input data:
    MSH:;~\&:STAR:A:CAI:A:200209080200::ADT;A03;41:306 31362:2.2:30631362::AL::
    EVN:A03:200209080200::
    PID::02030669:0001446316;;;A:1800;A2280:MERGETWO;J UDIE;;::19520915:F::1:45357 BLACK OAK LANE;;ST LOUIS;MO;63141;US;C;MO189:MO189314)555-1212::;;:M:;:0221900001;;;A:101-01-1001:
    NK1:1:MERGETWO;DALE:H;;:45357 BLACK OAK LANE;;ST LOUIS;MO;63141;US314)555-1212
    PV1::O:;;;A;;;:3:::10398;BRIGHTFIELD;KENNETH;R:::I MG::::1:EF:10398;BRIGHTFIELD;KENNETH;R:SER;;A:0221900001;; ;A:S::::::::::::::::A:::A:::::200208070834:2002090 72359::::
    ZCA:::;;;
    ZCV:5::JES::::SER:0
    ZLC:MDB
    ZB0:020908-020022
    

    MSH:;~\&:STAR:A:CAI:A:200209080200::ADT;A03;41:306 31363:2.2:30631363::AL::
    EVN:A03:200209080200::
    PID::02030578:0001446241;;;A:880;A3880:TEST;BED;;: MILLER:19750306:M::1:98 JADE LANE;;LABADIE;MO;63055;;C;MO071:MO071314)742-3656800)662-8439:;;:S:;:0224900001;;;A:500-12-9889:
    NK1:1:GORDON;FLASH:F;;:;;;;;:
    PV1::I:;;;A;;;:3:::10004;ABELE;FREDERICK;A:::AIC:: ::2:EF:10004;ABELE;FREDERICK;A:IP;;A:0224900001;;;A:C: :::::::::::::::1:::A:::::200209061645:200209080001 ::::
    ZCA:::;;;
    ZCV:8::::::IP:
    ZLC:ONES
    ZB0:020908-020024
    


    Log file with bad ACKs:
    12/28/2006 09:42:37 11645 opening data file...hl7.save
    12/28/2006 09:42:37 11645 Received < MSH:;~\&:A:200209080200:A:CAI:20061228094245.264-0600::ACK:30631362:2.2
    MSA:CA:30631362
    
    >

    12/28/2006 09:42:37 11645 Received < [email protected]
    >

    12/28/2006 09:42:37 11645 Received < MSH:;~\&:A:200209080200:A:CAI:20061228094245.508-0600::ACK:30631363:2.2
    MSA:CA:30631363
    
    >

    12/28/2006 09:42:37 11645 Received < [email protected]
    >

    12/28/2006 09:42:37 11645 AT end of file....
    12/28/2006 09:42:37 11645 Read 4 Records...

  • #2
    Re: Bad ACK messages

    What is your channel setup like? LLP Listener to...?
    Chris Lang

    Comment


    • #3
      Re: Bad ACK messages

      We&#039;ve identified this as a bug in the LLP sender and will schedule a fix ASAP.

      Thanks!
      -Chris
      Chris Lang

      Comment


      • #4
        Re: Bad ACK messages

        I am also seeing an exception thrown on a broken pipe. This is when my tcp feeder closes the socket. See Mirth log below:

        ERROR 2006-12-28 17:51:21,887 [a326147f-26c5-47d8-934f-ab2a83fbd4d5_source_connector._tcpEndpoint#2041163 710.receiver.2] org.mule.impl.DefaultComponentExceptionStrategy: Caught exception in Exception Strategy for: a326147f-26c5-47d8-934f-ab2a83fbd4d5: java.net.SocketException: Broken pipe
        java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(Unknown Source)
        at java.net.SocketOutputStream.write(Unknown Source)
        at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
        at java.io.BufferedOutputStream.flush(Unknown Source)
        at java.io.DataOutputStream.flush(Unknown Source)
        at org.mule.providers.tcp.protocols.LlpProtocol.write (LlpProtocol.java:160)
        at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.generateACK(TcpMessageReceiver.java:324)
        at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.processData(TcpMessageReceiver.java:307)
        at org.mule.providers.tcp.TcpMessageReceiver$TcpWorke r.run(TcpMessageReceiver.java:274)
        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)
        ~


        {}

        Comment


        • #5
          Re: Bad ACK messages

          This should be fixed with 1.3.2.
          Chris Lang

          Comment

          Working...
          X