More details here http://mail-archives.apache.org/mod_mbox/activemq-users/200703.mbox/% [EMAIL PROTECTED]
Michele On Fri, 2007-08-10 at 09:38 +0100, Michele Mazzucco wrote: > Lizhao, > > from http://activemq.apache.org/containers.html it looks like it should > work. > > Michele > > On Fri, 2007-08-10 at 13:26 +0800, Chen, Lizhao wrote: > > Hi, Michele, > > > > I don't think it runs embedded ActiveMQ in Tomcat which described in > > http://activemq.apache.org/tomcat.html, you should have to run > > standalone ActiveMQ else. > > > > Best Regards! > > > > > > > > Lizhao Chen > > > > > > > > 86-021-50800850-8395 > > > > -----Original Message----- > > From: Michele Mazzucco [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 10, 2007 1:26 AM > > To: [email protected] > > Subject: Re: [axis2] jms configuration how to > > > > Asankha, > > > > thanks for the quick reply. I'm quite familiar with Joram > > (standalone) but not with ActiveMQ so I did what is described here > > [1] (second option) > > > > > > Michele > > > > [1] http://activemq.apache.org/tomcat.html > > > > On 9 Aug 2007, at 17:47, Asankha C. Perera wrote: > > > > > Michele > > >> <transportReceiver name="jms" > > >> class="org.apache.axis2.transport.jms.JMSListener"> > > >> <parameter name="default"> > > >> <parameter > > >> name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQI > > > > >> nitialContextFactory</parameter> > > >> <parameter > > >> name="java.naming.provider.url">tcp://localhost:61616</parameter> > > >> <parameter > > >> name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory > > > > >> </parameter> > > >> </parameter> > > >> </transportReceiver> > > >> > > > You have specified that the JMS connection factory found when a > > > JNDI lookup is performed for "QueueConnectionFactory" using the > > > initial context factory > > > "org.apache.activemq.jndi.ActiveMQInitialContextFactory" and the > > > url "tcp://localhost:61616" should be used by the Axis2 JMS > > > listener. Note that the above sample configuration is the default > > > configuration for a standalone ActiveMQ release - and not for an > > > ActiveMQ instance embedded into Tomcat. > > >> [ERROR] Error creating a JMS connection using the factory : > > >> QueueConnectionFactory > > >> javax.jms.JMSException: Could not create Transport. Reason: > > >> java.io.IOException: Transport scheme NOT recognized: [tcp] > > >> > > > Here the JNDI lookup has failed when trying to access the JNDI > > > context using the above IC factory and URL. Probably this is due to > > > an issue in embedding ActiveMQ into Tomcat - which I am not > > > familiar with. You could refer to the ActiveMQ documentation, and > > > supply the correct parameters for Axis2 to use to acquire the JNDI > > > context and things will work > > > > > > asankha > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > ============================================================ > > The information contained in this message may be privileged > > and confidential and protected from disclosure. If the reader > > of this message is not the intended recipient, or an employee > > or agent responsible for delivering this message to the > > intended recipient, you are hereby notified that any reproduction, > > dissemination or distribution of this communication is strictly > > prohibited. If you have received this communication in error, > > please notify us immediately by replying to the message and > > deleting it from your computer. Thank you. Tellabs > > ============================================================ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
