Works !
Thanks for reply, Scott.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880381#3880381
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880381
---
This SF.Net
anonymous wrote : I meant this on the last line :
|
| | true
| | ...
| |
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880130#3880130
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880130
My goal is :
Separate instances of the same MDB are deployed in separate ejb-jars. Each one
is configured to pick message from it's own queue.
What I've done (looks wrong) :
They are distinct named jar, different JNDI name, different queue names in DDs
and so on.
My trouble is :
After starting
Thanks for reply,
Tried, but does not work better.
Much of code in this mbean is not of my own so, I've worked around with a
singleton factory provider. I think it's an too-early call (at
instantiation-time rather start time...)
View the original post :
http://www.jboss.org/index.html?module=
Hi,
MBean Short desc :
Main goal is to produce JMS messages on a specified Queue as files are uploaded
in specified directories. It works fine when deployed on a running jboss but I
still experience troubles when JBoss is restarted.
Troubles:
1 - ConnectionFactory (JMS) is not yet bound at st
