<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<font size="-1"><tt>The JMS message requirements
<a class="moz-txt-link-freetext" href="http://download.oracle.com/javaee/6/tutorial/doc/bncfu.html">http://download.oracle.com/javaee/6/tutorial/doc/bncfu.html</a> state that:<br>
<br>
"The most reliable way to produce a message is to send a PERSISTENT
message within a transaction. *JMS messages are PERSISTENT by default*".<br>
<br>
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:<br>
<br>
<!-- disable messaging persistence --><br>
<persistence-enabled>false</persistence-enabled><br>
<br>
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.<br>
<br>
-Jaikiran <br>
</tt></font>
</body>
</html>