axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Jones" <Tjo...@metamatrix.com>
Subject RE: Soap Over JMS using Embedded Axis2 Engine
Date Wed, 03 Jan 2007 15:19:43 GMT
Thanks very much Ali. That seems to be the issue with the timeout. I started the JMSListener
from my test client and it is picking up the message now. I am now getting the following exception:
 

________________________________

From: Ali Sadik Kumlali [mailto:as_kumlali@yahoo.com] 
Sent: Tuesday, January 02, 2007 4:57 PM
To: axis-user@ws.apache.org
Subject: Re: Soap Over JMS using Embedded Axis2 Engine


Hi Ted,

War distribution(AxisServlet actually) doesn't initialize JMS listener. Please look at followings:
1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html
2) https://issues.apache.org/jira/browse/AXIS2-1488

Regards,

Ali Sadik Kumlali


----- Original Message ----
From: Ted Jones <Tjones@metamatrix.com>
To: axis-user@ws.apache.org; brennanspies@sbcglobal.net
Sent: Tuesday, January 2, 2007 9:35:14 PM
Subject: RE: Soap Over JMS using Embedded Axis2 Engine


Thanks for the reply Brennan. I believe I have everything configured as per the link below,
but I keep timing out while "waiting for the server to send the response".
 
I am seeing this in my ActiveMQ console: myservice - No subscriptions registered, will not
dispatch message at this time.
 
"myservice" is the destination I am dynamically adding in my client code and that matches
with the destination in my services.xml.
 
Here is my services.xml:
 
<service name="service">
    <description>
        My Web Service
    </description>
 <transports>
      <transport>jms</transport>
    </transports>
    <parameter name="ServiceClass" locked="false">com.test.soap.lds.service.DataServiceWebService</parameter>
 <parameter name="allowedMethods" locked="false">executeDataservice</parameter>
   
 <parameter name="transport.jms.ConnectionFactory" locked="true">QueueConnectionFactory</parameter>
    <parameter name="transport.jms.Destination" locked="true">myservice</parameter>

    <messageReceivers>
      <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"
        class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
      <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
        class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
    </messageReceivers>
</service>
 
Thanks for your help,
Ted

________________________________

From: Brennan Spies [mailto:brennanspies@sbcglobal.net] 
Sent: Friday, December 29, 2006 10:19 PM
To: axis-user@ws.apache.org
Subject: RE: Soap Over JMS using Embedded Axis2 Engine



Ted,

 

Did you uncomment/configure the appropriate entries in your axis2.xml as well as your .aar’s
service.xml?

 

http://ws.apache.org/axis2/1_1/jms-transport.html

 

 

________________________________

From: Ted Jones [mailto:Tjones@metamatrix.com] 
Sent: Friday, December 29, 2006 3:36 PM
To: axis-user@ws.apache.org
Subject: Soap Over JMS using Embedded Axis2 Engine

 

I am attempting to execute a web service via ActiveMQ. The web service is deployed to an Axis2
engine that is embedded in a web app running on Tomcat 5.5. Are there any known *gotchas*
here? I cannot seem to communicate with the service via JMS as it keeps timing out. When I
change my endpoint in the client call from the JMS endpoint to the web service endpoint, it
finds it.

 

Thanks,

Ted



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message