activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Pasch (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3686) Http Tunnel Servlet: Connection reset on the client
Date Sun, 11 Mar 2012 16:01:59 GMT

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

Thomas Pasch updated AMQ-3686:
------------------------------

           Regression: Regression
    Affects Version/s: 5.4.1
                       5.4.2
                       5.4.3
                       5.5.1
               Labels: http-tunneling servlet  (was: )

This is to bold that this is a regression: The 5.3.x branch hasn't this problem at all. As
I work for an open source company, it is possible to get access to java sources were this
problem manifest. Somebody interested?
                
> Http Tunnel Servlet: Connection reset on the client
> ---------------------------------------------------
>
>                 Key: AMQ-3686
>                 URL: https://issues.apache.org/jira/browse/AMQ-3686
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.4.0, 5.4.1, 5.4.2, 5.4.3, 5.5.0, 5.5.1
>         Environment: Ubuntu 11.10
>            Reporter: Thomas Pasch
>              Labels: http-tunneling, servlet
>
> We are using the tunnel servlet for a long time now in our application. There were no
problems with the 5.3.x versions of ActiveMQ. However, with newer versions (5.5.0) we observe
clients connection resets after 10 to 30 minutes.
> 2012-01-27 13:18:44,794 INFO  [org.springframework.jms.listener.SimpleMessageListenerContainer]
Trying to recover from JMS Connection exception: javax.jms.JMSException: Could not post command:
KeepAliveInfo {} due to: java.net.SocketException: Connection reset
> 2012-01-27 13:18:44,799 ERROR [org.springframework.jms.listener.SimpleMessageListenerContainer]
Encountered non-recoverable JMSException
> javax.jms.JMSException: Could not post command: KeepAliveInfo {} due to: java.net.SocketException:
Connection reset
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1841)
> at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1858)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:126)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:101)
> at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:265)
> at org.apache.activemq.transport.InactivityMonitor$3.run(InactivityMonitor.java:156)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.io.IOException: Could not post command: KeepAliveInfo {} due to: java.net.SocketException:
Connection reset
> at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
> at org.apache.activemq.transport.http.HttpClientTransport.oneway(HttpClientTransport.java:103)
> at org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:254)
> at org.apache.activemq.transport.InactivityMonitor$3.run(InactivityMonitor.java:154)
> ... 3 more
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:168)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
> at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
> at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
> at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
> at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
> at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
> at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at org.apache.activemq.transport.http.HttpClientTransport.oneway(HttpClientTransport.java:91)
> ... 5 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message