On 02/19/2016 12:39 PM, Flores, Paul A. wrote: > Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 > Release to work. > > > > When I go to run it I am seeing the following. > > > > Can some one point me to a resolution? I am running out of hair to pull! >
Try changing you URI in the jndi.properties to 'amqp://localhost:5672' not the 'amqp' is not capitalized. > > Thanks. > > > > Paul > > > > 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory > - Failed to create Provider instance for AMQP, due to: > java.io.IOException: Provider scheme NOT recognized: [AMQP] > 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory > - Failed to create JMS Provider instance for: AMQP > Caught exception, exiting. > javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 > at > org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) > at HelloWorld.main(HelloWorld.java:51) > Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) > at > org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) > at > org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) > ... 1 more > Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not find > factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) > at > org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) > ... 4 more > -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/
