It's not impossible that my MDB config is wrong, it's bothering that same configuration works consistently in weblogic and websphere but not in jboss. As I said, I did try to make the subscription durable, see the MDB's ejb-jar.xml underneath.
I also tried to make the messages persistent, but at that point the text in the system.out became "10:10:38,736 INFO [STDOUT] Warning: Message to JBossTopic[com.bluemartini.DBUtilTopic] not processed: delegator->JBossMessage[5244570167312385]:PERSISTENT, deliveryId=1", and the JMS message was still delivered 2 times out of 3.
Frankly there is a certain hint of flakiness coming out of this issue, in regards to JBoss capability of working with JMS. Hope I'm wrong and indeed something in our app is interfering with the JMS (although don't really see how...)
thanks/Ranjix
P.S. Again, a hint towards where in the sources is the text "Message to JBossTopic" constructed would really help. At that point I could try and debug.
the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID"
version="2.1"
<display-name>remotedesktop-JAR</display-name>
<enterprise-beans>
<message-driven>
<description> db util mdb </description>
<display-name>DBUtilTopicMDB</display-name>
<ejb-name>DBUtilTopicMDB</ejb-name>
<ejb-class>com.bluemartini.jms.mdb.DBUtilTopicMDB</ejb-class>
<transaction-type>Bean</transaction-type>
<message-destination-type>javax.jms.Topic</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>subscriptionDurability</activation-config-property-name>
<activation-config-property-value>Durable</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
</ejb-jar>