Hi Have you tried upgrading to a newer Camel release?
Are you using the IPF platform by any chance? http://gforge.openehealth.org/gf/project/ipf/ I spotted the ghl7 which I think is part of that framework. If so you may wanna ask in that community. On Thu, Feb 10, 2011 at 6:39 AM, hoopzhou <hoopz...@gmail.com> wrote: > > Hello! > I use Camel HL7 component. And I've a problem with below scenario (Camel > 2.1.0): > > from("mina:tcp://0.0.0.0:5800?sync=true&codec=#hl7MLLPCodec").unmarshal().ghl7().to(XXXXXXX) > > Scenario I: > Create connection > send HL7 message A to my route > Release connection. > > Create connection: > send HL7 message B to my route > Release connection. > > Scenario II: > Create connection: > send HL7 message A to my route > send HL7 message B to my route > Release connection. > > Scenario I success, but scenario II fail. > > From log, I found that in Scenario II the first message is handled > successfully, but the second message failed. It is because that when message > A received, the content in Body is message A, but when message B received, > the content in Body is message 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.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
