activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-664) Messages sent via STOMP don't have a correct JMSTimestamp.
Date Mon, 12 Jun 2006 11:18:51 GMT
    [ https://issues.apache.org/activemq/browse/AMQ-664?page=comments#action_36281 ] 

Nathan Mittler commented on AMQ-664:
------------------------------------

There are a couple ways we could fix this:

1) I guess a quick fix would be to add a timestamp when the broker receives the message that
is whatever "now" is.
2) Add a "timestamp" header to the stomp messages that can be assigned by the client.  The
broker could just pass this through.





> Messages sent via STOMP don't have a correct JMSTimestamp.
> ----------------------------------------------------------
>
>          Key: AMQ-664
>          URL: https://issues.apache.org/activemq/browse/AMQ-664
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Transport
>     Versions: 4.0 RC2
>     Reporter: Bruce Mitchener
>     Priority: Minor

>
>
> Messages sent via STOMP have no correct JMSTimestamp specified.  (Or that's what jconsole
indicates)

-- 
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


Mime
View raw message