You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "enes.caglar" <en...@hotmail.com> on 2016/01/22 10:14:18 UTC

Re: No IConnectionFactory implementation found for connection

Fixed the problem by using ConnectionFactory instead of NMSConnectionFactory.



--
View this message in context: http://activemq.2283324.n4.nabble.com/No-IConnectionFactory-implementation-found-for-connection-tp4705373p4706313.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: No IConnectionFactory implementation found for connection

Posted by "enes.caglar" <en...@hotmail.com>.

Thank you for your reply. Also tried with NMSConnectionfactory with the uri
you specified and it worked.



--
View this message in context: http://activemq.2283324.n4.nabble.com/No-IConnectionFactory-implementation-found-for-connection-tp4705373p4707431.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: No IConnectionFactory implementation found for connection

Posted by Jim Gomes <jg...@apache.org>.

Using NMSConnectionFactory will work if you format the URI correctly. When
using NMSConnectionFactory, you must prefix the URI with the provider
implementation you wish to use. For instance, if you want to use ActiveMQ
provider, use the following format:

activemq:failover:tcp://activemqhost:61616

If you want to use TIBCO provider, use the following format:

ems:tcp://tibcohost:7222

Those are just a couple of samples to show how to use NMSConnectionFactory.
It is the preferred method rather than using the straight ConnectionFactory.

On Fri, Jan 22, 2016, 1:36 AM enes.caglar <en...@hotmail.com> wrote:

> Fixed the problem by using ConnectionFactory instead of
> NMSConnectionFactory.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/No-IConnectionFactory-implementation-found-for-connection-tp4705373p4706313.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>