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...@apache.org> on 2006/03/28 04:15:34 UTC
[jira] Created: (AMQ-664) Messages sent via STOMP don't have a
correct JMSTimestamp.
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 RC1
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
[jira] Closed: (AMQ-664) Messages sent via STOMP don't have a
correct JMSTimestamp.
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-664?page=all ]
Nathan Mittler closed AMQ-664:
------------------------------
Resolution: Fixed
The broker now assigns the current time as the JMSTimestamp to all incoming stomp messages.
> 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
> Reporter: Bruce Mitchener
> Assignee: Nathan Mittler
> Priority: Minor
> Fix For: 4.1
>
>
> 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
[jira] Commented: (AMQ-664) Messages sent via STOMP don't have a
correct JMSTimestamp.
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (AMQ-664) Messages sent via STOMP don't have a
correct JMSTimestamp.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-664?page=all ]
Hiram Chirino updated AMQ-664:
------------------------------
Fix Version: 4.1
Version: 4.0
(was: 4.0 RC2)
I think option 1 is the best option and is simple enough to get get done for a 4.1 release.
> 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
> Reporter: Bruce Mitchener
> Priority: Minor
> Fix For: 4.1
>
>
> 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
[jira] Assigned: (AMQ-664) Messages sent via STOMP don't have a
correct JMSTimestamp.
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-664?page=all ]
Nathan Mittler reassigned AMQ-664:
----------------------------------
Assign To: Nathan Mittler
> 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
> Reporter: Bruce Mitchener
> Assignee: Nathan Mittler
> Priority: Minor
> Fix For: 4.1
>
>
> 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