activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <>
Subject [jira] [Closed] (AMQ-3228) Fail to send message with HTTPS connector and slow connection
Date Tue, 25 Oct 2011 21:40:32 GMT


Timothy Bish closed AMQ-3228.

    Resolution: Cannot Reproduce

Not able to reproduce this one, recommend trying the latest SNAPSHOT build which many Http
fixes and updates.  A JUnit test case to reproduce the problem would help to investigate if
the problem is still present.  
> Fail to send message with HTTPS connector and slow connection
> -------------------------------------------------------------
>                 Key: AMQ-3228
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.4.2
>         Environment: Linux www-dev 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009
x86_64 GNU/Linux
> java version "1.6.0_12"
> Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
>            Reporter: Antoine L.
> Sending a message (mixed data, including bytearray; ~1-2MB) with the HTTPS connector
will fail after 2-3 mins if the connection used is slow.
> Exception : Failed to perform GET on: Reason: null
> On previous version (5.3.x), there was no such problem (may be related to the recent
upgrade to Jetty 7.x ?)
> By googling at Jetty, there is a default timeout (called max idle timeout) of 220000

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message