activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: Not receiving errors for incorrect message headers
Date Tue, 24 Oct 2006 19:49:13 GMT
This has been fixed in activemq-trunk and activemq 4.0.2.  I just ran your
test case against trunk and I get:
chirino@wireless ~/tmp/incubator-activemq-fuse-4.1.0-SNAPSHOT/example
$ telnet localhost 61613
Trying ::1...
Connected to localhost.
Escape character is '^]'.
CONNECT

^@
CONNECTED
session:ID:wireless.hiram.chirino-59937-1161719186028-3:0


BEGIN
session:ID:wireless.hiram.chirino-59937-1161719186028-3:0
receipt: mymessage-002

^@
ERROR
receipt-id:mymessage-002
message:Must specify the transaction you are beginning

org.apache.activemq.transport.stomp.ProtocolException: Must specify the
transaction you are beginning
        at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompBegin(
ProtocolConverter.java:255)
        at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(
ProtocolConverter.java:143)
        at
org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(
StompTransportFilter.java:64)
        at org.apache.activemq.transport.TransportSupport.doConsume(
TransportSupport.java:84)
        at org.apache.activemq.transport.tcp.TcpTransport.run(
TcpTransport.java:136)
        at java.lang.Thread.run(Thread.java:613)



On 10/24/06, David Jones <david.jones@ingenta.com> wrote:
>
>
> Hi,
>
> Not sure if this is now a moot point after the discussion on this post
> (http://www.nabble.com/Stomp-Receipts-tf2145063.html), but I've been
> enhancing (read, "messing") the original Perl Stomp modules found on
> Codehaus. After a bit of to- and fro-ing, I connected up to an ActiveMQ
> 4.0.1 server as a publisher using Telnet, and had my suspicions confirmed
> --
> you don't get errors for malformed messages as they happen.
> More specifically, there is no reply to a malformed BEGIN message and this
> strikes me as something which might be important. The original code had no
> 'transaction' specified in the header, and this was obviously incorrect --
> although less obvious given that the ERROR frame was not received until
> attempting to SEND a message to the server.
>
> My conversation with the server went like this (server output in bold):
>
> Connected to scratch3.catchword.com (194.129.29.211).
> Escape character is '^]'.
> CONNECT
>
> ^@
> CONNECTED
> session:ID:scratch3.ingenta.com-40420-1161359286422-3:9
>
>
> BEGIN
> session:ID:scratch3.ingenta.com-40420-1161359286422-3:9
> receipt: mymessage-002
>
> ^@
>
> SEND
> session:ID:scratch3.ingenta.com-40420-1161359286422-3:9
> receipt: mymessage-003
>
> This is a message! I should have gotten an error AGES ago..
> ^@
> ERROR
> message:Must specify the transaction you are beginning
>
>
> DISCONNECT
>
> ^@
> Connection closed by foreign host.
> --------------
>
> Is this because of the asynchronous behaviour of the messaging system? Are
> there any other surprises like this which aren't obvious without
> tinkering?
> --
> View this message in context:
> http://www.nabble.com/Not-receiving-errors-for-incorrect-message-headers-tf2502995.html#a6978067
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message