Hi Gert,
I changed all the the jbi endpoints to in-out mep's. Now it is working.
Thanks.
Regards,
Ganesh
navigator09 wrote:
>
> Hi Gert,
>
>
> I have done the necessary changes in the configuration as suggested.
> Between service invocations I get the following error
>
>
> 9:23:01,859 | DEBUG | pool-flow.seda.servicemix-jsr181-thread-2 |
> DeliveryChannelImpl | .messaging.DeliveryChannelImpl 710 | Notifying
> exchange ID:10.20.3.92-11e430d9feb-3:0(cd3bec) in
> DeliveryChannel{servicemix-camel} from processInboundSynchronousExchange
> 09:23:01,859 | DEBUG | pool-flow.seda.servicemix-camel-thread-1 |
> DeliveryChannelImpl | .messaging.DeliveryChannelImpl 704 | Notified:
> ID:10.20.3.92-11e430d9feb-3:0(cd3bec) in DeliveryChannel{servicemix-camel}
> from sendSync
> 09:23:01,890 | ERROR | pool-flow.seda.servicemix-camel-thread-1 |
> DeadLetterChannel | .apache.camel.processor.Logger 143 | On
> delivery attempt: 0 caught: org.apache.camel.RuntimeCamelException:
> javax.xml.transform.TransformerException: java.io.IOException: Stream
> closed
> org.apache.camel.RuntimeCamelException:
> javax.xml.transform.TransformerException: java.io.IOException: Stream
> closed
>
> Regards,
> Ganesh
>
>
> Gert Vanthienen wrote:
>>
>> Ganesh,
>>
>> Could you change your Camel route to include a log: endpoint between
>> both service invocations. This will make it a lot easier to figure out
>> what's going on.
>> By the way, you can just add all the steps in your pipeline with simple
>> to(...) calls in your Camel route -- there's no real need for the
>> explicit pipeline call here.
>>
>> Another thing you can check is the MEPs being used for invoking the
>> services. Just enable DEBUG logging in ServiceMix and check if
>> everything uses InOut MEPs as you expect. If not, you can always force
>> the MEP by appending mep=in-out to the URI.
>>
>> Regards,
>>
>> Gert
>>
>> navigator09 wrote:
>>> Hi,
>>>
>>> I am trying to configure a camel pipeline component which needs to
>>> pipe
>>> input data to a jsr181 component and the output of this component to a
>>> eventprocessor. The input sent to the jsr181 component is successfully
>>> processed and a successful output is obtained but the input to the
>>> event
>>> processor is blank. Because of this the pipeline component resends the
>>> user
>>> input to the eventprocessor also, which is not desired.
>>>
>>> I tried testing the jsr 181 component in isolation, exposing it using
>>> http
>>> component and noting the output. It works perfectly well. Only in the
>>> pipeline pattern its output is null. Is this some kind of a
>>> incompatability
>>> issue between the output of jsr181 and the i/p to eventprocessor within
>>> the
>>> context of pipeline pattern?
>>>
>>>
>>>
>>>
>>> from("jbi:endpoint:http://foo.bar.org/PipeLine/Endpoint";).
>>> to("log:routingslip1").
>>> convertBodyTo(String.class).
>>>
>>> pipeline("jbi:endpoint:http://www.icenigrid.org/service/gridsam/JobSubmission/JobSubmission";,
>>>
>>> "jbi:endpoint:http://foo.bar.org/EventProcessor/MyEndpoint";);
>>>
>>>
>>> Regards,
>>> Ganesh
>>>
>>
>>
>>
>> -----
>> ---
>> Gert Vanthienen
>> http://gertvanthienen.blogspot.com
>>
>
>
--
View this message in context:
http://www.nabble.com/Camel-pipeline-component-and-jsr181-tp21011542p21047160.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
