1 Reply Latest reply on Aug 26, 2011 1:27 PM by Murali Kumar

    MDB w/Tibco Queue only Works with ActivationConfig Settings

    Patrick Dobson Newbie


      I hope someone has figured this out. We are running JBoss 4.2.2. We have a simple MDB being driven off a Tibco EMS Queue. I got this to work (after many failed attempts) by configuring an ExternalContext and a JMSProviderLoader. This works only if I have all of the connection info (user, password, URL, etc.) in the Properties for the ExternalContext (no problem) AND ALSO in the ActivationConfig annotations for the MDB (problem!).

      Basically, we need this info to be configurable at deployment time so we have to find a way to take it out of the MDB annotations (or override them).

      We tried putting the same info (user, password, maxSession, DLQ settings, etc.) into an ejb-jar.xml, jboss.xml, properties for the JMSProviderLoader. But the only place it seems to have any effect is when set as ActivationConfig annotations in the MDB which is not acceptable for our situation.

      It appears this info gets set on a JMSActivationSpec object when the ear gets deployed. How can I get these values set without using MDB annotations?

      Any help would be very much appreciated!

      -ptFromSeismic