-
1. Re: MDB on WebSphere application sever is not picking up message
gaohoward Feb 25, 2013 1:07 AM (in response to honglei_ruan)EAP 6.0 uses HornetQ as its default messaging service, which has totally different set of configurations from JBM. If you can give more configuration details of your MDB setup, it will help a lot to figure out the issue.
-
2. Re: MDB on WebSphere application sever is not picking up message
honglei_ruan Feb 25, 2013 9:58 AM (in response to gaohoward)My MDB setup is almost the same as with JBM (that is the issue?). And on my local webspher server, I am not using Activation Specification. I am still using Message Listener ports for MDB binding. Here are the config details:
JMS Provider Config:
Name: JBoss Messaging
ClassPath: {libPath}\jboss-client.jar
External Intitial Context Factory: org.jboss.naming.remote.client.InitialContextFactory
External Provider URL: remote://localhost:4447
ConnectionFactory Config:
Provier: JBoss Messaging
Name: XAConnectionFactory
JNDI Name: jms/XAConnectionFactory
External JNDI Name: XAConnectionFactory
Queue Config:
Provier: JBoss Messaging
Name: FileConnectQueue
JNDI Name: jms/FileConnectQueue
External JNDI Name: queue/FileConnectQueue
MDB Listener Port:
Name: FCQListenerPort
Connection Factory JNDI: jms/XAConnectionFactory
Destination JNDI: jms/FileConnectQueue
Please kindly let me know what I missed. Thanks!!