You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Bruce Mitchener (JIRA)" <ji...@activemq.org> on 2006/03/21 22:11:25 UTC

[jira] Created: (AMQ-649) Error frames are not pushed out immediately

Error frames are not pushed out immediately
-------------------------------------------

         Key: AMQ-649
         URL: http://jira.activemq.org/jira//browse/AMQ-649
     Project: ActiveMQ
        Type: Bug

  Components: Transport  
    Versions: 4.0 M4    
    Reporter: Bruce Mitchener


If you send a malformed SEND frame to the server (like having a newline after your payload and before the NULL when using a content-length header), you don't get the ERROR frame back from the server immediately as you did with 3.2.2.  With both 4.0M4 and the SNAPSHOT from March 20, I had to send another message to the server to see the ERROR frame.

This was quite confusing when implementing a new STOMP client.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-649) Error frames are not pushed out immediately

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/AMQ-649?page=all ]
     
Hiram Chirino resolved AMQ-649:
-------------------------------

    Fix Version: 4.1
     Resolution: Fixed
      Assign To: Hiram Chirino

Fixed in trunk revision 418602.

> Error frames are not pushed out immediately
> -------------------------------------------
>
>          Key: AMQ-649
>          URL: https://issues.apache.org/activemq/browse/AMQ-649
>      Project: ActiveMQ
>         Type: Bug

>   Components: Transport
>     Versions: 4.0 M4
>     Reporter: Bruce Mitchener
>     Assignee: Hiram Chirino
>      Fix For: 4.1

>
>
> If you send a malformed SEND frame to the server (like having a newline after your payload and before the NULL when using a content-length header), you don't get the ERROR frame back from the server immediately as you did with 3.2.2.  With both 4.0M4 and the SNAPSHOT from March 20, I had to send another message to the server to see the ERROR frame.
> This was quite confusing when implementing a new STOMP client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira