[esb-issues] [JBoss JIRA] Closed: (JBESB-1023) DefaultESBPropertiesSetter setExpiration should calculate the TTL from the JMSExpiration value

Daniel Bevenius (JIRA) jira-events at lists.jboss.org
Sun Sep 16 09:40:10 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBESB-1023?page=all ]

Daniel Bevenius closed JBESB-1023.
----------------------------------

    Resolution: Done

Committed with revision 15152.

> DefaultESBPropertiesSetter setExpiration should calculate the TTL from the JMSExpiration value
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBESB-1023
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1023
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2.1 IR1
>            Reporter: Daniel Bevenius
>         Assigned To: Daniel Bevenius
>            Priority: Trivial
>             Fix For: 4.2.1 IR1
>
>
> I saw the method setJMSExpiration and thought that an application could set the JMSExpiration time before sending the message. This is not true. The ttl is specified via the method send(Message message,int deliveryMode,int priority,long timeToLive) and the message provider sets the JMSExpiration value. The default behaviour in the ESB is to pass the value of getJMSExpiration as a property within the ESB, and upon leaving again setting the JMSExpiration.
> The task should involve calculating the TTL from the JMSExpiration. And also use the send method described above so pass along the TTL. The last change also something needed for JBESB-646

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

        



More information about the esb-issues mailing list