[esb-issues] [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

Wed Sep 19 06:12:11 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12377552 ] 

Daniel Bevenius commented on JBESB-646:
---------------------------------------

Mark made me aware that Persistent, TTL, and Priority are QoS aspects and should not go into the JMSEpr.

So, I've been poking around and the found that the JMSCourier is created with an instance of a JMSEpr. So I need some other way of making such QoS aspects available to the the courier. 
I'm getting the feeling that this might be a bigger issue then the original jira was intended for. A QoS config should be usable will all types of transports. The properties above are easily mapped to JMS but for other transports like ftp something has to be put in place.

Any thought on this?

I've implemented the three configuration properties above for JMSRouter and NotifyJMS which are independent of the solution for the JMSCourier above. Would it be alright to check this in or should I create a separate JIRA for one of these issues?

Thanks

/Daniel

> NON_PERSISTENT JMS messaging.
> -----------------------------
>
>                 Key: JBESB-646
>                 URL: http://jira.jboss.com/jira/browse/JBESB-646
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2 Milestone Release 2
>            Reporter: Daniel Bevenius
>         Assigned To: Daniel Bevenius
>            Priority: Blocker
>             Fix For: 4.2.1 IR1
>
>
> The current classes that deal with sending JMS messages, like JMSCourier, do not specify a delivery mode when sending messages. The default is then that the messages are sent with a delivery mode of persistent. 
> The request (see forum reference) is to be able have the delivery mode configurable so one can avoid the persisting to stable storage.

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