hi james;
I found the reason..My receiver application already sending an ack
response, what im doing is generating the ack message again from that ack
response:)..
Now sorted out... thanks fro your help.
regds
-ratha
On 1 May 2013 00:53, vijayaratha vijayasingam wrote:
> hi jmaes..
> thanks fo
hi jmaes..
thanks for helping me out...Still i couldn't find the reason why this MSA
and MSH fields are swapped..
What im doing is;
- Sending a raw HL7 message to the server.
- Waiting for response from the backend application. (putting a
thread.sleep)
- Once received a response, im pu
Hi Ratha,
No, your understanding is exactly correct. Your XML response is a correct
response, and HAPI should be fine with it. If you look at the log you
provided however:
INFO app.Receiver: Unexpected Message Received:
MSH|^~\&|20130424171523.303+0530||ACK|335|P|2.1
[java] MSA|AA|208
..th
Hi james,
That also i noted,
i receive above xml response from my backend server, after receiving that
xml message i generate an ack message as follows;
hl7Msg.generateACK();
I dont know why it is changed at client end..
You can see my xml response contains 12345 and
208
.
I found reference from
It looks to me like your server isn't actually sending back that particular
response. If you look at the log line in [2], a response message is
received, but if you look at the value of MSA-2 it doesn't match the value
of "12345" in the message [1], which is what the client is actually
expecting to
Hi all;
I send a hl7 message with a messgeid=12345 and receives XML response[1]
with same messageID.( check the MSA field ; ie:12345)
In the request message's MSH_10 header and the response's MSA.2 filed
values are matching..
But why do i get the timeout exception[2]?
I store the response [1] in a
6 matches
Mail list logo
