Re: Axis2 SOAP-over-JMS

[Asankha C. Perera]

Hi Badrys I have fixed https://issues.apache.org/jira/browse/AXIS2-2434 on the trunk, and could apply this to the 1.2 branch as soon as you could verify that the fix works as expected. Then it will get into the next build. asankha badrys wrote: Hi Asankha, Any good news concerning the "Axis2 one way messaging" issue we discussed last time ? :-) Thanks. asankha wrote: Hi Badrys Yes, the problem is not yet fixed. I will try my best to fix this in the coming week ahead asankha badrys wrote: Hi Asankha I actually could solve the axis2 problem I had and then I had another Axisfault related to JMS : So I guess I have a pure JMS question this time If you don't mind : In my web service I have a one way operation (void runPublisher() ) and when I call it from a client , it came up with this exception: << 23 mars 2007 14:26:33 org.apache.axis2.transport.jms.JMSSender invoke ATTENTION: Did not receive a JMS response within 30000 ms to destination : topic://pubtopic.TestTopic org.apache.axis2.AxisFault: Incoming message input stream is null at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202) at src.src.PublishingServiceStub.echoPublisher(PublishingServiceStub.java:154) at src.src.ClientEcho.main(ClientEcho.java:17) And then when I try to make some search about this kind of exception in mailing lists archives I found that you have dealt with it quite recently ( https://issues.apache.org/jira/browse/SYNAPSE-68 ). I would be grateful If you tell wether or not you solved the problem and how you did it. Thanks in advance. asankha wrote: Hi Badrys Seems like the problem you encounter below is not related to JMS. So its better to describe it with a new subject and post to the list for better answers. One thing I noted was that you ask for " http://localhost:8080/axis2/services/MyService/myOperation   but Axis2 says it couldn't find Service Not found EPR is /axis2/services/HelloPublishSubscribe/echoHello asankha badrys wrote: Actually, I understood the " Version" thing : Version is the web service sample given with Axis2 and according to the Apache documentation ( http://ws.apache.org/axis2/1_1/jms-transport.html ), when the JMS transport starts it checks all the destinations specified by all the web services and gives a default destination name (which is the same as the name of the service) to those who doesn't specify one. Since "Version" is one of them, the JMS transport associate a destination named Version to it. But my real problem now is the "Axis Fault : Operation Not Found" thing : when I checked this url : "http://localhost:8080/axis2/services/MyService/myOperation" I found this: <soapenv:Fault> <faultcode>soapenv:Client</faultcode> <faultstring> Service Not found EPR is /axis2/services/HelloPublishSubscribe/echoHello </faultstring> <detail/> </soapenv:Fault> I guess it means that Axis2 doesn't recognize my web service's operation but I don't know what caused that, and what is really weird : on the url : "http://localhost:8080/axis2/services/" , I can see my web service and its operations displayed. can you help me with this issue ? Thanks for your time. asankha wrote: Are you using the latest trunk? there was a defect when the JMS Destination name was different from its JNDI name but I am not sure if this is the case. If the JMS transport creates a new Queue with the name "Version", then obviously it cannot find a JMS destination with the name "Version" on the JNDI context you specify.. Could you check why that might be? asankha badrys wrote: Hi Asankha When I deployed my web service (the publish/subscirbe application I told you about before). Axis2 generated a wsdl and the wsdl2java tool generated a code (stub and callback handler) that I used to create a client. However, I noticed something weird when launching Axis2 : although I didn't forget to specify my destination (topic) and launch my JMS Broker before that, It put this on the terminal: [CODE] ATTENTION: Cannot find destination : Version Creating a Queue with this name 22 mars 2007 15:06:28 org.apache.axis2.transport.jms.JMSConnectionFactory listen INFO: Connection factory : default initialized... 22 mars 2007 15:06:28 org.apache.axis2.transport.SimpleAxis2Server main INFO: [SimpleAxisServer] Started [/CODE] And when I try to execute my client, axis2 came up with this exception : [CODE] 22 mars 2007 15:07:46 org.apache.axis2.transport.jms.JMSMessageReceiver$Worker r un GRAVE: JMS Worker [JMSWorker-1] Encountered an Axis Fault : Operation Not found EPR is and WSA Action = "" org.apache.axis2.AxisFault: Operation Not found EPR is and WSA Action = "" nSubscriber at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPha se.java:48) at org.apache.axis2.engine.Phase.invoke(Phase.java:398) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:487) at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessa geReceiver.java:198) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor ker.runTask(ThreadPoolExecutor.java:650) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor ker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) [/CODE] Have you any idea of what is causing this ? Many thanks. badrys asankha wrote: Hi Badrys does the fact of specifying a JMS destination in services.xml create a physical Destination (a Java Object that I can access from a java code) ? and if it's the case can you tell me how to do it ? Yes, if your JMS provider supports this. (e.g. ActiveMQ) This would create a JMS Queue with a name same as that of the service, and you should be able to access this using JNDI from Javacode outside 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] --------------------------------------------------------------------- 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]