[
https://issues.apache.org/jira/browse/SMXCOMP-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970143#action_12970143
]
Ge@@ru commented on SMXCOMP-831:
--------------------------------
I do another test where instead of use smx-bean and smx-camel components i used
only smx-bean components with only 2 threads for pool and i see that requests
are enqueue correctly and handled yet if there are few threads available.
While, with smx-camel this doesn't work. So I confirm that there is a bug on
use correctly unqueue of the requests when there are more request of the
threads pool size.
Increase size of the pool is a workaround and not a final solution that it
works like for smx-bean.
> Problem on call servicemix-bean service from camel route with concurrent
> requests
> ---------------------------------------------------------------------------------
>
> Key: SMXCOMP-831
> URL: https://issues.apache.org/jira/browse/SMXCOMP-831
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2010.02
> Reporter: Ge@@ru
> Priority: Blocker
> Attachments: test_route.tar.bz2
>
>
> I found a problem on use servicemix-camel with servicemix-bean. In
> particular, in a scenario like this:
> - a cxf-bc that expose a ws and that send exchange to cxf-se service;
> - cxf-se service call a servicemix-camel route1;
> - servicemix-camel route1 call a camel route2 (to jbi component)
> - servicemix-camel route2 call a servicemix bean service (with a thread
> sleep inside);
> - a second client call cxf-bc service when first client wait for
> response;
> - and at this point last camel route that wait for a reply from
> servicemix-bean service became broken yet after when servicemix-bean
> close exchange correctly.
> With debug i see that exchange is sent to smx-bean service (in state
> Active) and answer is returned by always with state Active, it seems
> that exchange don't change to Done and it is handled correctly by
> servicemix-camel module.
> This problem happens only when there are 2 route camel and second route
> call smx-bean, while, if i try to call directly smx-bean from first
> camel route all works fine.
> I add a smx-bean before second camel route by problem is always present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
