You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2007/10/24 11:36:27 UTC

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

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

Freeman Fang updated SM-1035:
-----------------------------

    Fix Version/s:     (was: 3.2)
                   3.2.1

> 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
>            Assignee: Guillaume Nodet
>             Fix For: 3.2.1
>
>   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.