-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.3 SP1
-
None
I'm not sure about the JMS version number. I'm using JBoss 4.0.3SP1.
In AbstractDLQHandler.java, line 132 reads:
QueueConnectionFactory qcf = (QueueConnectionFactory) Util.lookup(ctx,
queueFactoryRef, TopicConnectionFactory.class);
^^^^
but should read:
QueueConnectionFactory qcf = (QueueConnectionFactory) Util.lookup(ctx,
queueFactoryRef, QueueConnectionFactory.class);
^^^^^^
This causes the lookup to fail reliably.
I'm hitting this code because I'm using the demo for JBoss/WebSphereMQ integration. The extra configuration for WebSphereMQ winds up triggering the GenericDLQHandler. I don't know how many use cases are affected by this, but this is a critical bug for me. There is no workaround besides using a custom-built jms-ra.jar which is something I'd rather not maintain.
Obviously, this change also makes the 'import ...TopicConnectionFactory' statement superfluous.
- is related to
-
JBJCA-17 JMS Message Inflow
- Closed