Nirmal Just to close the loop here in HCC, i'll summarize from the Apache NiFi mailng-list response I've posted a few minutes ago The NPE is due to the fact that we are invoking a default constructor for whatever connection factory class is provided (i.e., ‘org.exolab.jms.client.JmsConnectionFactory’). And that works for most major JMS providers (ActiveMQ, IBM, Tibco, Weblogic etc.). However for OpenJMS after looking at the code it is rather clear that the default constructor was not exposed to be actually used by the developers, rather internal serialization use. /** * Default constructor required for serialization */ public JmsConnectionFactory() { } Not sure why it was done this way . . ., but the NPE is due to the fact that the server proxy class is null so when it attempts to do Class.forName(proxyClassName) in getProxy() method it fails with NPE. One other thing I noticed is that all OpenJMS examples are based on obtaining ConnectionFactory from JNDI for which we currently do not have support. Please raise the JIRA if you believe that it’s important to add such feature. Cheers Oleg ... View more