>> I'll let you guys know if there are and adverse effects.
The suggested modifications certainly worked in getting around problems during
start-up.
However, now that I'm using the null-persistence-manager, I see the following
errors when deploying MDBs (ejb3) ... (I get this dump for each MDB
I've managed to come up with a resolution, for now.
If I copy the portion of the hsqldb-persistence-service.xml file related to the
JMS User Manager MBean config into the null-persistence-service.xml, the
problem is resolved.
View the original post :
http://www.jboss.org/index.html?module=b
After successfully configuring a custom destination (so I thought) with the
following customization(s) ...
jboss.messaging.destination:service=Queue,name=prototype_DLQ
jboss.messaging.destination:service=Queue,name=prototype_ExpiryQ
${config.dest.prototype_PacketResendQ.Rede
