[jboss-as7-dev] Why is JMS message persistence disabled by default?

[Emanuel Muckenhuber]

AFAIR we only disabled it because of startup time, since the creation of 
the journal files wasn't lazy. However enabling it in the configuration 
should work though.

On 04/20/2011 09:59 AM, Jaikiran Pai wrote:
> The JMS message requirements
> http://download.oracle.com/javaee/6/tutorial/doc/bncfu.html state that:
>
> "The most reliable way to produce a message is to send a PERSISTENT
> message within a transaction. *JMS messages are PERSISTENT by default*".
>
> However, currently while testing 7.0.0.Beta3 I noticed that this isn't
> the case. Sending out 3 messages to a queue and restarting the server
> loses the messages. Before restarting I did use the JConsole to make
> sure that the message count shows up correctly and it did. On restart I
> see the count reset to 0. Looking at the messaging subsystem, I notice
> that we have set:
>
> <!-- disable messaging persistence -->
> <persistence-enabled>false</persistence-enabled>
>
> This shouldn't be the case, since it breaks JMS spec out of the box. By
> the way, I tried setting it to persistence-enabled=true and testing this
> whole flow again. But I still see the message count reset to 0 on a
> server restart. I'll see if I can figure out why the persistence-enabled
> flag change isn't taking effect.
>
> -Jaikiran
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev