Hi obn,
In my configuration my ejb jar file looks like this:
com/mycompany/mypackage/mbdclassfile.class
meta-inf/ejb-jar.xml
meta-inf/jboss.xml
jms-ds.xml is in your JBossHome/server/*configuration*/deploy/jms
It sounds like you have another MDB (MDBExample) listening to the same queue...
Thanks jaikiran, I solved the problem although I'm not happy about it! In my
jms-ds.xml I had specified:
java:/XAConnectionFactory
which is how the DefaultJMSProvider is configured. When I changed this to
XAConnectionFactory
as in your post, it magically works! So I don't understand why the
I've been trying to configure a simple MDB to use a remote destination as
described in this wiki page ->
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnMDBToTalkToARemoteQueue
I can see the naming lookup done on port 1099 to the remote server, but then
the MDB is bound to a local d
Here's how thedog's suggestion should look in processdefinition.xml:
|
|
|
|
|
Regards,
ROb
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933905#3933905
Reply to the post :
http://www.jboss.com/index.h