[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr

[Guillaume Nodet (JIRA)]

    [ 
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40010
 ] 

Guillaume Nodet commented on SM-1035:
-------------------------------------

I agree with Jorge.
I think the NMR should ensure that the exchange is delivered to the target 
endpoint and I don't think it should retry by itself.  If the request times 
out, the client may retry at a later time if needed.

> Continuation problems when Max Idle Time ocurr
> ----------------------------------------------
>
>                 Key: SM-1035
>                 URL: https://issues.apache.org/activemq/browse/SM-1035
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-http
>         Environment: Servicemix 3.1
>            Reporter: Jorge Rodríguez Pedrianes
>             Fix For: 3.1.2, 3.2
>
>   Original Estimate: 2 minutes
>  Remaining Estimate: 2 minutes
>
> HI!
>     I saw in Http binding component, that if my service work too time, the 
> http endpoint retry the current request. but this it's wrong. I think that in 
> ConsumerProcessor class it's better to do this: 
> {code:title=ConsumerProcessor java|borderStyle=solid}
> ...
>  public void process(HttpServletRequest request, HttpServletResponse 
> response) throws Exception {
>    ....
>    // If the continuation is not a retry
>    if (!cont.isPending() && cont.isNew()) {
>           ...
> }
> {code}
> Whith this we avoid put the request two times in the bus.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.