Invalid value can be set in setJMSExpiration method of Message class

[glassfishrobot]

-1 can be set for setJMSExpiration(long expiration) method of Message class. When -1 is set and executed, no exception or error is displayed. Should it cause exception when an invalid value is set?

Environment

Glassfish 4.0.1 b02 07/24/2013
Windows

[glassfishrobot]

@glassfishrobot Commented
Reported by tak09

[glassfishrobot]

@glassfishrobot Commented
@nigeldeakin said:
A negative timestamp has no meaning, so it would be helpful if MQ threw an exception when an attempt was made to set a negative value. The JMS specification does not require that the exception that is thrown is a JMSException, but this seems to be the most appropriate exception to throw.

Note that this method is not intended for use by client applications and any value set by the client application will always be overridden (see the javadoc):

This method is for use by JMS providers only to set this field when a message is sent. This message cannot be used by clients to configure the expiration time of the message. This method is public to allow a JMS provider to set this field when sending a message whose implementation is not its own.

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA MQ-333

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/openmq/issues/333
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @edbratt

[pzygielo]

• Exception is thrown since Fix #214 Add check to validate the value of time-to-live #1199.