You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "薛诚颉 (JIRA)" <ji...@apache.org> on 2009/01/11 13:20:59 UTC

[jira] Created: (AMQ-2059) transport via http protocol is unreliable

transport via http protocol is unreliable
-----------------------------------------

                 Key: AMQ-2059
                 URL: https://issues.apache.org/activemq/browse/AMQ-2059
             Project: ActiveMQ
          Issue Type: Bug
          Components: Transport
    Affects Versions: 5.2.0
         Environment: windows xp ,jdk 6.0 ,activemq 5.2
            Reporter: 薛诚颉


i'm using activemq 5.2.
the transportation is very reliable when i use tcp protocol.but it's always unreliable via http protocol.
and i get the exception like this:

java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:168)
	at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:384)
	at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:107)
	at org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:198)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:287)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:407)
	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:235)
	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:526)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Created: (AMQ-2059) transport via http protocol is unreliable

Posted by Petter Nordlander <Pe...@enfo.se>.
It’s tunneling AMQ data through XML over HTTP so it’s pretty much expected to be slower than the binary tcp based transport.

Do you believe something is wrong or just expect the same performance for HTTPS tunneling?

> 12 dec 2015 kl. 04:43 skrev neo.li <ne...@arcserve.com>:
> 
> hello,
>     I did not encounter such a fatal error. but I find AMQ using http/htpps
> is slower than using tcp.
> I do not how to optimize it.  can u help me?
> 
> thank you
> Neo
> 
> 
> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-2059-transport-via-http-protocol-is-unreliable-tp2387028p4704909.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


Re: [jira] Created: (AMQ-2059) transport via http protocol is unreliable

Posted by "neo.li" <ne...@arcserve.com>.
hello,
     I did not encounter such a fatal error. but I find AMQ using http/htpps
is slower than using tcp.
I do not how to optimize it.  can u help me?

thank you
Neo



--
View this message in context: http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-2059-transport-via-http-protocol-is-unreliable-tp2387028p4704909.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] Resolved: (AMQ-2059) transport via http protocol is unreliable

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2059.
-----------------------------

    Resolution: Cannot Reproduce

seems more like a comment than a bug report. Check out 5.4 in any event, there has been a bunch of work on the http transport.

> transport via http protocol is unreliable
> -----------------------------------------
>
>                 Key: AMQ-2059
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2059
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>         Environment: windows xp ,jdk 6.0 ,activemq 5.2
>            Reporter: 薛诚颉
>             Fix For: 5.4.0
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> i'm using activemq 5.2.
> the transportation is very reliable when i use tcp protocol.but it's always unreliable via http protocol.
> and i get the exception like this:
> java.net.SocketException: Connection reset
> 	at java.net.SocketInputStream.read(SocketInputStream.java:168)
> 	at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:384)
> 	at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:107)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:198)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:287)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:407)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:235)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:526)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-2059) transport via http protocol is unreliable

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-2059:
----------------------------

    Fix Version/s: 5.4.0

> transport via http protocol is unreliable
> -----------------------------------------
>
>                 Key: AMQ-2059
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2059
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.2.0
>         Environment: windows xp ,jdk 6.0 ,activemq 5.2
>            Reporter: 薛诚颉
>             Fix For: 5.4.0
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> i'm using activemq 5.2.
> the transportation is very reliable when i use tcp protocol.but it's always unreliable via http protocol.
> and i get the exception like this:
> java.net.SocketException: Connection reset
> 	at java.net.SocketInputStream.read(SocketInputStream.java:168)
> 	at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:384)
> 	at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:107)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:198)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:287)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:407)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:235)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:526)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.