This content has been marked as final.
Show 2 replies
-
1. Re: Routing to an Oracle AQ produces AQjmsException during d
dr.shizuma May 11, 2009 3:53 AM (in response to dr.shizuma)I had a look at the code and I think that's the problem here:
org.jboss.soa.esb.actions.routing.JMSRouter:private Properties getEnvironment() { final Properties environment = new Properties(); environment.setProperty(Context.PROVIDER_URL, jndiUrl); environment.setProperty(Context.INITIAL_CONTEXT_FACTORY, jndiContextFactory); environment.setProperty(Context.URL_PKG_PREFIXES, jndiPkgPrefix); return environment ; }
This environment is used to create the initial factory, but org.jboss.soa.esb.oracle.aq.AQInitialContextFactory already connects when someone calls "getInitialContext()" & the connection details are not passed in the environment.... -
2. Re: Routing to an Oracle AQ produces AQjmsException during d
kconner May 11, 2009 6:30 AM (in response to dr.shizuma)There are two issues with this, one is definitely a bug
The JMSRouter has no knowledge of extending the JNDI configuration, unlike the JMSEpr, which means that this action is only useful with providers that require no configuration other than potential security details.
The other issue is that the integration with Oracle AQ should really be binding into the real JNDI hierarchy rather than creating a mock JNDI and populating that independently.
I'll create a bug for the first and have the second investigated.