m/HL7-component-release-connection-problem-tp3378827p3382359.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Looks like you're using the wrong charset. Your example message says
that it is encoded with ISO-IR-87 but the Camel's HL7 codec by default
the system's default charset. Configure the HL7 codec again with the
ISO-IR-87 charset and try again.
Does that help?
Am 11.02.11 10
Ok thanks, I'll take a look as soon as I can. Please let me know how it
works with another client.
Cheers,
Martin
Am 11.02.11 10:01, schrieb hoopzhou:
Hi
Thanks for your quick reply.
I use b) .
Sorry. I am not a user of Jira. I just attached the message for quick.
http://camel.465427.n5.nabb
before. So I did not doubt this tool:)
I will try to write new client to verify this again.
Thank you and best wishes
zhou nan
--
View this message in context:
http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3380820.html
Sent from the Camel - Users mailing list
Hi,
sorry for jumping in so late on this issue. To investigate this problem
further, please
- attach the HL7 messages (files) you use for testing to the JIRA issue
(maybe there's a problem with the line endings)
- describe how the message is sent (what client is used, provide some
code if po
out.write(body);
> // Avoid redelivery of scanned message
> state.reset();
> } catch (CharacterCodingException e) {
> throw new RuntimeException(e);
> }
> }"
>
> It seems to write all bytebuffer to body. Is it the
// Avoid redelivery of scanned message
state.reset();
} catch (CharacterCodingException e) {
throw new RuntimeException(e);
}
}"
It seems to write all bytebuffer to body. Is it the cause? Sorry for that I
am not very familiar with Java NIO.
--
View this m
his message in context:
> http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3379201.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesou
Ok. Thanks for you help. I will post the question to IPF google groups.
--
View this message in context:
http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3379201.html
Sent from the Camel - Users mailing list archive at Nabble.com.
quot;message A + message B" not "message B"
> as I described above without release connection.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3379166.html
> Sent from the
e connection.
--
View this message in context:
http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3379166.html
Sent from the Camel - Users mailing list archive at Nabble.com.
sage A+ message B not message B.
>
> Is there any options to configure it or I should split the message by
> myself?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3378827.h
sage in context:
http://camel.465427.n5.nabble.com/HL7-component-release-connection-problem-tp3378827p3378827.html
Sent from the Camel - Users mailing list archive at Nabble.com.
13 matches
Mail list logo