Non persistent JMS Message

[naxius]

Hi,

I am using Jboss Messaging and I'd like to know how to configure a queue that is not managing persistent messages.

By default, the distribution is coming out with an in-memory database and its PersistentManager. How can I sitch to a non persistent messaging configuration?

Many thanks for your feedback.

Regards
Alexandre

[timfox]

If you send a message as non persistent (DeliveryMode.NON_PERSISTENT) then it won't get persisted.

If you don't control over this, them there's not much you can do currently.

There is a task scheduled for this for JBM2.0 http://jira.jboss.com/jira/browse/JBMESSAGING-381

[naxius]

"timfox" wrote:
If you send a message as non persistent (DeliveryMode.NON_PERSISTENT) then it won't get persisted.

If you don't control over this, them there's not much you can do currently.

There is a task scheduled for this for JBM2.0 http://jira.jboss.com/jira/browse/JBMESSAGING-381

Thanks a lot Tim for your quick answer.
Though, if I compare BEA product to jBoss messaging, the behavior is quite different. In a commercial product that I won't quote here, it's quite easy to configure a queue or a topic with no datasource associated to it (storing enable=true or false).

The thing I do not understand is that Jboss must have a datasource for all JMS stuff even though a persistant messaging system is not needed, because I know that if things goes wrong (server crash, ...), it's not business critical.

Many thank Tim for your feedback.
Alexandre

[naxius]

"timfox" wrote:
If you send a message as non persistent (DeliveryMode.NON_PERSISTENT) then it won't get persisted.

If you don't control over this, them there's not much you can do currently.

There is a task scheduled for this for JBM2.0 http://jira.jboss.com/jira/browse/JBMESSAGING-381

Thanks a lot Tim for your quick answer.
Though, if I compare commercial product to jBoss messaging, the behavior is quite different. In a commercial product that I won't quote here, it's quite easy to configure a queue or a topic with no datasource associated to it (storing enable=true or false).

The thing I do not understand is that Jboss must have a datasource for all JMS stuff even though a persistant messaging system is not needed, because I know that if things goes wrong (server crash, ...), it's not business critical.

Many thank Tim for your feedback.
Alexandre

[timfox]

"aaubry" wrote:

Though, if I compare commercial product to jBoss messaging, the behavior is quite different. In a commercial product that I won't quote here, it's quite easy to configure a queue or a topic with no datasource associated to it (storing enable=true or false).

The thing I do not understand is that Jboss must have a datasource for all JMS stuff even though a persistant messaging system is not needed, because I know that if things goes wrong (server crash, ...), it's not business critical.

As I say, this is a scheduled task and has been for some time.

It is actually very easy to implement, we just haven't got around to it yet!

We only have limited resources (two permanent developers) so we can't do everything instantly - take a look at JIRA for open tasks.

If you like you could attempt the task yourself and contribute back to the project.

wdyt?

:)