On Tue, Aug 4, 2009 at 11:42 AM, raulvk.soa<[email protected]> wrote:
>
> Hi Claus,
> Your suggestion seems contradictory to Ganesh's.
>
> He suggests removing the convertBodyTo(String.class) and the log step
> afterwards from the flow, whereas you suggest adding a
> convertBodyTo(String.class) at the beginning.
>
> Could you please clarify? It would be helpful to know what is the actual
> underlying issue.

Ahh i actually depends where the stream is closed exception occurs.

If it occurred in Camel then you could have converted the payload to a
String as it can be re-read multiple times.
However if it occurs afterwards in SMX then it might be an idea to
leave Camel without touching the payload.

However Camel have stream caching that tries to remedy this issue. But
it has been a bit flaky in older versions of Camel.
http://camel.apache.org/stream-caching.html


>
> Many thanks,
> Raul.
>
>
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> I think you can solve it by adding the
>>     .convertBodyTo(String.class).
>>
>> To your camel route just after the first from XXX
>>
>>
>> On Tue, Aug 4, 2009 at 2:05 AM, raulvk.soa<[email protected]> wrote:
>>>
>>> Hi Ganesh,
>>>
>>> We are facing the exact same problem here.
>>> My question is: Were you able to make it work without upgrading to
>>> 2009.01?
>>> In my case, we are using v3.2.2 and it is unfeasible right now to upgrade
>>> the component.
>>>
>>> Or was it necessary to upgrade to 2009.01?
>>>
>>> Many thanks,
>>> Raul.
>>>
>>>
>>> navigator09 wrote:
>>>>
>>>> Gert,
>>>>
>>>>   I was able to solve the problem by commenting the following two lines
>>>> in
>>>> the flow
>>>>           convertBodyTo(String.class).
>>>>           to("log:jobsubstringinput").
>>>>
>>>>   Now the stream closed exception doesn't occur.  when I am done with my
>>>> current project, I plan to write a blog describing how convenient it was
>>>> to use servicemix-camel component  in our project. Thank you for the
>>>> support.
>>>>
>>>> Regards,
>>>> Ganesh
>>>>
>>>> navigator09 wrote:
>>>>>
>>>>> Gert,
>>>>>
>>>>>
>>>>>   I was able to create a servicemix-camel 2009 snapshot jar and was
>>>>> able
>>>>> to deploy it successfully in servicemix 3.2.2.But when I try to deploy
>>>>> the servicemix routes I get the following error
>>>>>
>>>>> <loc-message>org.apache.camel.NoSuchEndpointException: No endpoint
>>>>> could
>>>>> be found for :
>>>>> "jbi:endpoint:http://www.jobsubmission/service//RoutingSlip/Endpoint?mep=in-out";,
>>>>> please check your classpath contains the needed camel component
>>>>> jsr</loc-message>
>>>>>
>>>>>  I tried adding camel-jetty dependency to the camel routes SU. But I
>>>>> still keep getting the errors.
>>>>>
>>>>> Regards,
>>>>> Ganesh
>>>>>
>>>>>
>>>>>
>>>>> Gert Vanthienen wrote:
>>>>>>
>>>>>> Ganesh,
>>>>>>
>>>>>> What environment are you using (Maven/Java version, OS, ....) to do
>>>>>> this
>>>>>> build?
>>>>>> As a workaround, you can run Maven with the -Dmaven.test.skip=true
>>>>>> flag to skip the unit tests.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Gert Vanthienen
>>>>>> ------------------------
>>>>>> Open Source SOA: http://fusesource.com
>>>>>> Blog: http://gertvanthienen.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2009/2/26 navigator09 <[email protected]>:
>>>>>>>
>>>>>>> Gert,
>>>>>>>
>>>>>>> It gets stuck at this point "Running
>>>>>>> org.apache.servicemix.camel.JbiInOutCamelErrorHandlingTest"
>>>>>>>
>>>>>>> Regards,
>>>>>>> Ganesh
>>>>>>>
>>>>>>> Gert Vanthienen wrote:
>>>>>>>>
>>>>>>>> Ganesh,
>>>>>>>>
>>>>>>>> Normally, Maven should be able to deal with those dependencies on
>>>>>>>> itself.  For the shared libraries, there are some snapshots
>>>>>>>> available
>>>>>>>> on-line as well so there's no real need to build these yourself.
>>>>>>>> Could you tell us what problems you're experiencing do a mvn
>>>>>>>> install?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Gert Vanthienen
>>>>>>>> ------------------------
>>>>>>>> Open Source SOA: http://fusesource.com
>>>>>>>> Blog: http://gertvanthienen.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2009/2/25 navigator09 <[email protected]>:
>>>>>>>>>
>>>>>>>>> Gert,
>>>>>>>>>
>>>>>>>>>  I was able to checkout the servicemix-camel component. However a
>>>>>>>>> mvn
>>>>>>>>> install requires a dependent jar files with versions specified
>>>>>>>>> inside
>>>>>>>>> pom.xml. It also requires building latest shared-libraries. Is
>>>>>>>>> there
>>>>>>>>> any
>>>>>>>>> link which can help me do this successfully.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Ganesh
>>>>>>>>>
>>>>>>>>> Gert Vanthienen wrote:
>>>>>>>>>>
>>>>>>>>>> Ganesh,
>>>>>>>>>>
>>>>>>>>>> Sorry, my mistake.  The URL is for ViewVC -- useful for browsing
>>>>>>>>>> but
>>>>>>>>>> obviously not for checking out the source.
>>>>>>>>>> You should be using
>>>>>>>>>> http://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-camel/trunk/
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Gert
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> navigator09 wrote:
>>>>>>>>>>> Gert,
>>>>>>>>>>>
>>>>>>>>>>>  when I try to check-out the above repository using I get the
>>>>>>>>>>> following
>>>>>>>>>>> error
>>>>>>>>>>>
>>>>>>>>>>> '/viewvc/servicemix/components/engines/servicemix-camel/trunk/';
>>>>>>>>>>> please
>>>>>>>>>>> relocate
>>>>>>>>>>>
>>>>>>>>>>> what do I do?
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Ganesh
>>>>>>>>>>>
>>>>>>>>>>> Gert Vanthienen wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ganesh,
>>>>>>>>>>>>
>>>>>>>>>>>> Could you give this a try with a locally built SNAPSHOT version
>>>>>>>>>>>> of
>>>>>>>>>>>> the
>>>>>>>>>>>> component, using Camel 1.6.0?  We have recently fixed quite a
>>>>>>>>>>>> few
>>>>>>>>>>>> problems with StreamSource handling in ServiceMix and I suspect
>>>>>>>>>>>> this
>>>>>>>>>>>> particular problem will get solved as well by using the latest
>>>>>>>>>>>> version.
>>>>>>>>>>>>
>>>>>>>>>>>> To build the component locally:
>>>>>>>>>>>> - do an svn checkout from
>>>>>>>>>>>> http://svn.eu.apache.org/viewvc/servicemix/components/engines/servicemix-camel/trunk/
>>>>>>>>>>>> - change the version of camel in the pom.xml to 1.6.0 and do a
>>>>>>>>>>>> mvn
>>>>>>>>>>>> install
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Gert Vanthienen
>>>>>>>>>>>> ------------------------
>>>>>>>>>>>> Open Source SOA: http://fusesource.com
>>>>>>>>>>>> Blog: http://gertvanthienen.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/2/24 navigator09 <[email protected]>:
>>>>>>>>>>>>
>>>>>>>>>>>>> Gert,
>>>>>>>>>>>>>
>>>>>>>>>>>>>  In production environments , these issues can lead to
>>>>>>>>>>>>> rejection
>>>>>>>>>>>>> of
>>>>>>>>>>>>> the
>>>>>>>>>>>>> solution. Camel component is a powerful solution with good ease
>>>>>>>>>>>>> of
>>>>>>>>>>>>> use,
>>>>>>>>>>>>> I
>>>>>>>>>>>>> would definately want to use and promote it. Pls help us in the
>>>>>>>>>>>>> matter.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Ganesh
>>>>>>>>>>>>>
>>>>>>>>>>>>> navigator09 wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Gert<
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>   I have pasted the routes below
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>   Namespaces ns = new Namespaces("jobsubmission",
>>>>>>>>>>>>>> "http://www.jobsubmission/service/";);
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> from("jbi:endpoint:http://www.jobsubmission/service//RoutingSlip/Endpoint?mep=in-out";).
>>>>>>>>>>>>>>               convertBodyTo(String.class).
>>>>>>>>>>>>>>               to("log:jobsubstringinput").
>>>>>>>>>>>>>>               convertBodyTo(DOMSource.class).
>>>>>>>>>>>>>>               to("log:pipeline").
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> choice().when().xpath("/jobsubmission:submitJob",ns).
>>>>>>>>>>>>>>                               to("log:submitjob").
>>>>>>>>>>>>>>                               convertBodyTo(DOMSource.class).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> to("jbi:endpoint:http://www.jobsubmission/service/JobSubmission/JobSubmission?mep=in-out";).
>>>>>>>>>>>>>>                               to("log:jobsubmissionoutput").
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> to("jbi:endpoint:http://www.jobsubmission/service/EventProcessor/EventProcessorendpoint";).
>>>>>>>>>>>>>>               otherwise().
>>>>>>>>>>>>>>                               to("log:other").
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> to("jbi:endpoint:http://www.jobsubmission/service/JobSubmission/JobSubmission?mep=in-out";);
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Ganesh
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Gert Vanthienen wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Ganesh,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Could you post us some of the routes you are using?  It's
>>>>>>>>>>>>>>> very
>>>>>>>>>>>>>>> hard
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> figure out what's going from the stacktraces alone...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Gert
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> navigator09 wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi ,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>  I am using camel to route messages to different service end
>>>>>>>>>>>>>>>> points.
>>>>>>>>>>>>>>>> Sometimes when I redeploy servicemix camel, I get the
>>>>>>>>>>>>>>>> streamclosed
>>>>>>>>>>>>>>>> error. I
>>>>>>>>>>>>>>>> have gone through the servicemix website. So i am posting
>>>>>>>>>>>>>>>> full
>>>>>>>>>>>>>>>> stack
>>>>>>>>>>>>>>>> trace
>>>>>>>>>>>>>>>> of the problem here. Pls let me know how to solve the
>>>>>>>>>>>>>>>> problem.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>> Ganesh
>>>>>>>>>>>>>>>> http://www.nabble.com/file/p22032147/servicemix.log
>>>>>>>>>>>>>>>> servicemix.log
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -----
>>>>>>>>>>>>>>> ---
>>>>>>>>>>>>>>> Gert Vanthienen
>>>>>>>>>>>>>>> http://gertvanthienen.blogspot.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>> http://www.nabble.com/Stream-closed-exception-in-servicemix-camel-tp22032147p22176185.html
>>>>>>>>>>>>> Sent from the ServiceMix - User mailing list archive at
>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> -----
>>>>>>>>>>>> ---
>>>>>>>>>>>> Gert Vanthienen
>>>>>>>>>>>> http://gertvanthienen.blogspot.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -----
>>>>>>>>>> ---
>>>>>>>>>> Gert Vanthienen
>>>>>>>>>> http://gertvanthienen.blogspot.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> View this message in context:
>>>>>>>>> http://www.nabble.com/Stream-closed-exception-in-servicemix-camel-tp22032147p22197974.html
>>>>>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----
>>>>>>>> ---
>>>>>>>> Gert Vanthienen
>>>>>>>> http://gertvanthienen.blogspot.com
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Stream-closed-exception-in-servicemix-camel-tp22032147p22220416.html
>>>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> -----
>>>>>> ---
>>>>>> Gert Vanthienen
>>>>>> http://gertvanthienen.blogspot.com
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Stream-closed-exception-in-servicemix-camel-tp22032147p24800267.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>>
>
> --
> View this message in context: 
> http://www.nabble.com/Stream-closed-exception-in-servicemix-camel-tp22032147p24805375.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Reply via email to