[JBoss JIRA] Created: (JBESB-646) NON_PERSISTENT JMS messaging.

[JBoss JIRA] Created: (JBESB-1084)...

[JBoss JIRA] Created: (JBESB-1142)...

Daniel Bevenius (JIRA)

Monday, 25 June 2007 Mon, 25 Jun '07

6:58 a.m.

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 Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor 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

Show replies by date

Mark Little (JIRA)

Monday, 25 June Mon, 25 Jun

7:14 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12366634 ] Mark Little commented on JBESB-646: ----------------------------------- I think we need to fix this, because it will affect performance. Is this something that could be specified in the EPR, for instance?

...

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 Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor 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

Mark Little (JIRA)

Wednesday, 4 July Wed, 4 Jul

5:28 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Mark Little updated JBESB-646: ------------------------------ Fix Version/s: 4.2 Milestone Release 3 Affects Version/s: 4.2 Milestone Release 2 Assignee: Daniel Bevenius (was: Mark Little)

...

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: Minor Fix For: 4.2 Milestone Release 3 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.

Mark Little (JIRA)

6:54 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Mark Little updated JBESB-646: ------------------------------ Fix Version/s: 4.2 (was: 4.2 Milestone Release 3)

...

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: Minor Fix For: 4.2 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.

Mark Little (JIRA)

Friday, 13 July Fri, 13 Jul

6:42 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Mark Little updated JBESB-646: ------------------------------ Priority: Critical (was: Minor)

...

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: Critical Fix For: 4.2 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.

Burr Sutter (JIRA)

8:10 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12368858 ] Burr Sutter commented on JBESB-646: ----------------------------------- Assuming this has a jboss-esb.xml impact. Would we change the jms-bus? <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_business_service_Request" persist="true"  /> </jms-bus> OR Could it be an out-of-the-box action that marks the message as needing to be persisted? OR something else entirely different?

...

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: Critical Fix For: 4.2 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.

Kurt Stam (JIRA)

8:14 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12368859 ] Kurt Stam commented on JBESB-646: --------------------------------- My preference would be to configure in the jboss-esb.xml.

...

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: Critical Fix For: 4.2 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.

Mark Little (JIRA)

9:59 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12368874 ] Mark Little commented on JBESB-646: ----------------------------------- This should be defined within the EPR. If we're creating the EPR from the jboss-esb.xml then I agree.

...

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: Critical Fix For: 4.2 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.

Mark Little (JIRA)

6:15 p.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12368947 ] Mark Little commented on JBESB-646: ----------------------------------- BTW, this has everything to do with sending and receiving reliably versus unreliably. So far JMS is our only reliable transport and yet reliability is something we're not exposing to the end user: it just happens because we've implemented our JMS usage that way. I'm not suggesting we make this change for 4.2, but in 5.0 (and the original pre-rosetta architecture) we had an API to sendReliable and sendUnreliable. Then it's not in the EPR, but in the service contract.

...

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: Critical Fix For: 4.2 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.

Daniel Bevenius (JIRA)

Monday, 16 July Mon, 16 Jul

2:45 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12369050 ] Daniel Bevenius commented on JBESB-646: --------------------------------------- The JMS delivery mode can be set on the MessageProducer but can also be specified when sending messages like this: send(Message message, int deliveryMode, int priority, long timeToLive) So maybe we should be checking the message in question to see if it should be sent persistent/non-persistent. One could still specify a default delivery mode for the jms-bus in the configuration which would be used if the message has no delivery mode specified. But I'm not sure if there is any thing in the (ESB) Message object that indicates if the message should be stored persistently. Just a thought...

...

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: Critical Fix For: 4.2 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.

Mark Little (JIRA)

Saturday, 21 July Sat, 21 Jul

2:30 p.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12369649 ] Mark Little commented on JBESB-646: ----------------------------------- After having looked at what's involved to change this within the current codebase, I agree with Kurt: let's just specify this within the config. I think the default (if not specified) should be persistent simply because of backward compatibility issues, i.e., that's what we've been giving users so far.

...

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: Critical Fix For: 4.2 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.

Mark Little (JIRA)

Wednesday, 1 August Wed, 1 Aug

9:24 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Mark Little updated JBESB-646: ------------------------------ Fix Version/s: 4.2.1 (was: 4.2)

...

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: Critical Fix For: 4.2.1 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.

Mark Little (JIRA)

Tuesday, 21 August Tue, 21 Aug

5:14 p.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Mark Little updated JBESB-646: ------------------------------ Priority: Blocker (was: Critical)

...

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

Daniel Bevenius (JIRA)

Friday, 7 September Fri, 7 Sep

9:59 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12375894 ] Daniel Bevenius commented on JBESB-646: --------------------------------------- So should this persistent property be added to JMSEpr in the same way that the destinationType, message selector etc, are? I'll go through and check the pointer where we are sending JMS messages. This one I currently know about are: 1. JMSCourier 2. JMSRouter 3. NotifyQueues 4. NotifyTopics Any others I should know about?

...

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

Daniel Bevenius (JIRA)

Saturday, 8 September Sat, 8 Sep

9:45 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Work on JBESB-646 started by Daniel Bevenius.

...

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

Mark Little (JIRA)

11:16 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12375997 ] Mark Little commented on JBESB-646: ----------------------------------- Yes, modify JMSEpr to support it. Make the default value whatever we have at the moment though, for backwards compatibility.

...

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

Kevin Conner (JIRA)

Tuesday, 11 September Tue, 11 Sep

7:06 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Kevin Conner updated JBESB-646: ------------------------------- Fix Version/s: 4.2.1 IR1 (was: 4.2.1)

...

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.

Daniel Bevenius (JIRA)

Wednesday, 12 September Wed, 12 Sep

6:41 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12376348 ] Daniel Bevenius commented on JBESB-646: --------------------------------------- While we are doing this should we also add the ability to specify a priority and a time-to-live for the epr's outgoing messages? It not specified they could default to : javax.jms.Message.DEFAULT_DEFAULT_PRIORITY javax.jms.Message.DEFAULT_DEFAULT_TIME_TO_LIVE

...

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.

Daniel Bevenius (JIRA)

Wednesday, 19 September Wed, 19 Sep

6:12 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

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

Kevin Conner (JIRA)

Monday, 1 October Mon, 1 Oct

4:35 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Kevin Conner updated JBESB-646: ------------------------------- Fix Version/s: 4.2.1 IR2 (was: 4.2.1 IR1)

...

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

Daniel Bevenius (JIRA)

Tuesday, 2 October Tue, 2 Oct

7:03 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379856 ] Daniel Bevenius commented on JBESB-646: --------------------------------------- I had a chat with Kurt about the possibility to store the properties in question in juddi. Here is his response:

...

A UDDI is not meant for storing meta data, but rather a directory to store where services can be found. So I think this is not going to work out unless we move to a repository and use something like ebXML.

So, I'm bit stuck at the moment. Some refactoring is needed to have the JMSCourier to get this information.

...

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

Mark Little (JIRA)

8:57 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379876 ] Mark Little commented on JBESB-646: ----------------------------------- UDDI should be able to support this: http://www.w3.org/Submission/WS-PolicyAttachment/ Whether jUDDI can or cannot is obviously a different issue.

...

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

Mark Little (JIRA)

8:59 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379877 ] Mark Little commented on JBESB-646: ----------------------------------- To take a pragmatic approach, can we do this within the config as originally thought?

...

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

Daniel Bevenius (JIRA)

9:27 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379889 ] Daniel Bevenius commented on JBESB-646: ---------------------------------------

...

can we do this within the config as originally thought?

Do you mean like Burr suggested: <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_business_service_Request" persist="true"  /> </jms-bus> I see no problem with this, the only problem is getting this information to the JMSCourier without going via the JMSEpr.

...

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

Mark Little (JIRA)

10:05 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12379907 ] Mark Little commented on JBESB-646: ----------------------------------- Stick it in the EPR.

...

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

Daniel Bevenius (JIRA)

Thursday, 4 October Thu, 4 Oct

9:09 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=comments#action_12380452 ] Daniel Bevenius commented on JBESB-646: --------------------------------------- Should I add Priority and TimeToLive aswell of leave them until we find a better place for these values?

...

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

Daniel Bevenius (JIRA)

Sunday, 7 October Sun, 7 Oct

5:54 a.m.

New subject: [JBoss JIRA] Closed: (JBESB-646) NON_PERSISTENT JMS messaging.

[ http://jira.jboss.com/jira/browse/JBESB-646?page=all ] Daniel Bevenius closed JBESB-646. --------------------------------- Resolution: Done Committed with revision 15626.

...

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

6084

days inactive

6188

days old

esb-issues@lists.jboss.org

Manage subscription

26 comments

5 participants

tags (0)

participants (5)

Burr Sutter (JIRA)
Daniel Bevenius (JIRA)
Kevin Conner (JIRA)
Kurt Stam (JIRA)
Mark Little (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (JBESB-646) NON_PERSISTENT JMS messaging.