You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Michele Mazzucco <Mi...@ncl.ac.uk> on 2007/08/09 17:52:52 UTC
[axis2] jms configuration how to
Hi all,
I'm trying to have the jms transport running (activemq embedded in
tomcat) but it does not work. The JMS portion of axis2.xml is as
follows:
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="default">
<parameter
name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter
name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
</parameter>
</transportReceiver>
<transportSender name="jms"
class="org.apache.axis2.transport.jms.JMSSender"/>
The portion of server.xml used by JNDI is this:
<Resource name="jms/ConnectionFactory" auth="Container"
type="org.apache.activemq.ActiveMQConnectionFactory"
description="JMS Connection Factory"
factory="org.apache.activemq.jndi.JNDIReferenceFactory"
brokerURL="vm://localhost"
brokerName="LocalActiveMQBroker"/>
I've put the activemq lib in $CATALINA_HOME/lib (tomcat 6.0.13) but when
I start tomcat I get the following error (please note that commons log
is included in the activemq jar):
09-Aug-2007 16:43:22 org.apache.catalina.core.AprLifecycleListener init
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the
java.library.path: /usr/java/jdk1.5.0_10/jre/lib/i386/client:/usr/java/jdk1.5.0_10/jre/lib/i386:/usr/java/jdk1.5.0_10/jre/../lib/i386
09-Aug-2007 16:43:23 org.apache.coyote.http11.Http11NioProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
09-Aug-2007 16:43:23 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 7008 ms
09-Aug-2007 16:43:24 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
09-Aug-2007 16:43:24 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.13
09-Aug-2007 16:43:24 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive axis2.war
[INFO] Deploying module: soapmonitor-1.3
[INFO] Deploying module: script-1.3
[INFO] Deploying module: ping-1.3
[INFO] Deploying module: addressing-1.3
[INFO] Deploying module: metadataExchange-1.3
[INFO] script module activated
[INFO] HTTP Sender starting
[INFO] JMS Transport Receiver (Listener) initialized...
[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]
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:232)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:245)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:214)
at
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:161)
at
org.apache.axis2.transport.jms.JMSConnectionFactory.listen(JMSConnectionFactory.java:399)
at
org.apache.axis2.transport.jms.JMSListener.start(JMSListener.java:307)
at
org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:431)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4042)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4348)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.io.IOException: Transport scheme NOT recognized: [tcp]
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:25)
at
org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:171)
at
org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:76)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:230)
... 33 more
Caused by: java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at
org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:61)
at
org.apache.activemq.util.FactoryFinder.newInstance(FactoryFinder.java:47)
at
org.apache.activemq.transport.TransportFactory.findTransportFactory(TransportFactory.java:167)
... 35 more
Caused by: org.apache.commons.logging.LogConfigurationException:
User-specified log class 'org.apache.commons.logging.impl.Log4JLogger'
cannot be found or is not useable.
at
org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:798)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307)
at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645)
at
org.apache.activemq.transport.tcp.TcpTransportFactory.<clinit>(TcpTransportFactory.java:45)
... 44 more
[INFO] Error creating a JMS connection using the factory :
QueueConnectionFactory
09-Aug-2007 16:43:27 org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
09-Aug-2007 16:43:27 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
09-Aug-2007 16:43:27 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/31 config=null
09-Aug-2007 16:43:27 org.apache.catalina.startup.Catalina start
INFO: Server startup in 3498 ms
What's going on?
Thanks,
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] jms configuration how to
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
More details here
http://mail-archives.apache.org/mod_mbox/activemq-users/200703.mbox/%
3cec6e67fd0703290936x301b9c98u5e5be4d10fc182d8@mail.gmail.com%3e
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:Michele.Mazzucco@ncl.ac.uk]
> > Sent: Friday, August 10, 2007 1:26 AM
> > To: axis-user@ws.apache.org
> > 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: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> > ============================================================
> > 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: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] jms configuration how to
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
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:Michele.Mazzucco@ncl.ac.uk]
> Sent: Friday, August 10, 2007 1:26 AM
> To: axis-user@ws.apache.org
> 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: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> ============================================================
> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] jms configuration how to
Posted by "Chen, Lizhao" <li...@tellabs.com>.
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:Michele.Mazzucco@ncl.ac.uk]
Sent: Friday, August 10, 2007 1:26 AM
To: axis-user@ws.apache.org
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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
============================================================
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] jms configuration how to
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] jms configuration how to
Posted by "Asankha C. Perera" <as...@wso2.com>.
Michele
> <transportReceiver name="jms"
> class="org.apache.axis2.transport.jms.JMSListener">
> <parameter name="default">
> <parameter
> name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org