>> This is what I've been trying: >> <sequence name="sendJMSKoList"> >> <send> >> <endpoint> >> <address >> uri="jms:/cn=testQueue?transport.jms.ConnectionFactory=cn=outgoingQueueFactor >> y&transport.jms.DestinationType=queue"/> >> </endpoint> >> </send> >> </sequence> >> > Why do you have > ..transport.jms.ConnectionFactory=cn=outgoingQueueFactory... ? i.e. why > =cn=..?
I'm trying to use the connectionfactory that is set in the axis2.xml file in the "JMSSender" section. Similar to how the jms proxy uses the connection factory in the JMSListener for listening to the queue. I have this "working" with the full uri that spells out all the JMS connection info similar to http://people.apache.org/~veithen/synapse/Synapse_Samples.html#Sample250 But after it runs for a while I get connection exceptions. It seems like it is creating a new connection every time it publishes. I was hoping that by using the connection factory in the axis2.xml file, it would take care of that problem. >> In axis2.xml, this is what the jmssender looks like: >> <parameter name="outgoingQueueFactory"> >> <parameter >> name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</paramete >> r> >> <parameter >> name="java.naming.provider.url">ldap://servicelayer-dev:389/o=imq</parameter> >> <parameter >> name="transport.jms.ConnectionFactoryJNDIName">cn=marklogicXCF</parameter> >> </parameter> >> >> >> This is the error I get: >> ERROR JMSOutTransportInfo Cannot locate destination : cn=testQueue using >> jms:/cn=testQueue?transport.jms.ConnectionFactory=cn=outgoingQueueFactory&tra >> nsport.jms.DestinationType=queue >> javax.naming.NoInitialContextException: Need to specify class name in >> environment or system property, or as an applet parameter, or in an >> application resource >> > Have you placed the JAR containing LdapCtxFactory (and any of its > dependencies) into the lib directory? Yes, all needed jars are in the lib directory. Like I said, it all "works" when I have the full uri in the synapse.xml but after a while I get connection errors. > > Please share the full synapse.xml, axis2.xml and the log files See attached > > cheers > asankha This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain company proprietary and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited. If you have received this in error, please reply immediately to the sender and delete this message. Thank you.
