By this bit:
"I" wrote:I meant that while the server console log shows all kinds of stuff being done, as the JSM tracing is turned on, using these instructions: http://www.jboss.org/community/wiki/JBossMessagingUserEnablingTRACEloggingonserver.
...there's no sign of that msg either in the JMS system...
I just don't see it the Topic's statistics that a message passed through or something.
It seems like a MDB config issue, can you post the question to EJB team? Also JBM has some good examples for users to get started. You can download them from JBoss.org. Especially there is an example ejb3mdb that may be of some interest to you.
So, indeed, the fix seems to have been related to a missing Activation Property: @ActivationConfigProperty(propertyName = "destination", propertyValue = "JMSTopic1").
This is kinda strange, since the setting mappedName, already names the Topic.
The bean wasn't deploying properly, but the error was swallowed until the JBoss log4j settings were set to TRACE, which ended up spelling out the details.