[
https://issues.apache.org/jira/browse/AMQ-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3298.
-------------------------------
Resolution: Fixed
fixed in trunk, added property preferJndiDestinationLookup to the JmsConnector
so that the Topic and Queue connectors can be configured to look in JNDI before
using the default JMS create method.
> Cannot create bridge to WebSphere queue using default messaging provider
> ------------------------------------------------------------------------
>
> Key: AMQ-3298
> URL: https://issues.apache.org/jira/browse/AMQ-3298
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.4.2
> Environment: all
> Reporter: Richard Evans
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
>
> I am attempting to configure a queue-to-queue bridge from ActiveMQ to a queue
> in WebSphere 7. The WebShere queue used the internal 'default messaging
> provider'. The bridge configuration provides the JNDI name for the queue.
> In the ActiveMQ JmsQueueConnector.createForeignQueue method, the queue is
> created using:
> try {
> result = session.createQueue(queueName);
> } catch (JMSException e) {
> // look-up the Queue
> try {
> result = (Queue)jndiOutboundTemplate.lookup(queueName,
> Queue.class);
> ...
>
> Unfortunately, the Session.createQueue method in the WebSphere connector does
> not throw an exception at this point; instead a Queue object is created which
> cannot be used for message transmission. Ideally there would be a
> configuration option which bypasses the createQueue call and goes direct to
> the JNDI lookup.
> Or try the JNDI approach first and fallback to createQueue?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
