[ https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40009 ]
Jorge RodrÃguez Pedrianes commented on SM-1035: ----------------------------------------------- Yes this solved my problem. BTW, at first, i refered to the file "ConsumerProcessor" (this is used whith HttpEndpoint, now I use servicemix 3.1 and this new enpoint appear in trunk version) but I see that in "HttpConsumerEndpoint" happen the same problem. Thanks > 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 > > 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.