[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40189
]
koti reddy commented on SM-1035:
Hi Guillaume,
Do you have a fix for this? B'cause of this continuation problem we are having
errors below in our production system
javax.xml.stream.XMLStreamException
at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteStartTag(BaseNsStreamWriter.java:501)
at
com.ctc.wstx.sw.BaseNsStreamWriter.writeStartElement(BaseNsStreamWriter.java:305)
at
org.apache.servicemix.jbi.jaxp.XMLStreamHelper.writeStartElement(XMLStreamHelper.java:110
)
at
org.apache.servicemix.jbi.jaxp.XMLStreamHelper.copy(XMLStreamHelper.java:59)
at
org.apache.servicemix.soap.marshalers.SoapWriter.writeContents(SoapWriter.java:198)
at
org.apache.servicemix.soap.marshalers.SoapWriter.writeSoapEnvelope(SoapWriter.java:190)
at
org.apache.servicemix.soap.marshalers.SoapWriter.writeSimpleMessage(SoapWriter.java:99)
at
org.apache.servicemix.soap.marshalers.SoapWriter.write(SoapWriter.java:82)
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:24
4)
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:2
11)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:281)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:372)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at
org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector
.java:489)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> 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
>
> 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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40085
]
Guillaume Nodet commented on SM-1035:
-
URL: http://svn.apache.org/viewvc?rev=573248&view=rev
> 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.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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40007
]
George Gastaldi commented on SM-1035:
-
Jorge,
Did that statement solved your problem ? Anybody seen any problem using this ?
If not, I´ll update and commit this file.
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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39989
]
Jorge Rodríguez Pedrianes commented on SM-1035:
---
You think that a client invoke a service that insert a element in a DDBB but
this process it's very long, when jetty try to retry a request you insert two
times. Its better that invoke a service only once. If you increment
connectorMaxIdle property only delay this, but may happen later.
> 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.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39988
]
Thomas Termin commented on SM-1035:
---
You can adjust the behavoiur with a higher connectorMaxIdleTime and
consumerProcessorSuspendTime (The later should be higher) for long processing
requests. Why should it be wrong to retry a request?
> 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.
