axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera" <>
Subject Re: Axis2: soap/jms question
Date Sat, 24 Mar 2007 18:58:33 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ascii" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Shantanu / John Turner<br>
I have reapplied the fixes for 2030 and 2277 and fixed the unit tests,
as I had to revert them last week due to test failures. Would be great
if you could verify this with JBoss or other implementations. The
changes are all in the o.a.a.transport.jms package (3 files)<br>
Shantanu Sen wrote:
<blockquote cite=""
  <pre wrap="">Hi Asankha,

Sounds good. Please let me know the specific file that you patch so that I do not have to
update the whole tree again.


----- Original Message ----
From: Asankha C. Perera <a class="moz-txt-link-rfc2396E" href="">&lt;;</a>
To: <a class="moz-txt-link-abbreviated" href=""></a>
Sent: Thursday, March 22, 2007 9:54:49 PM
Subject: Re: Axis2: soap/jms question

Hi Shantanu
  <blockquote type="cite">
    <pre wrap="">17:12:30,812 ERROR [JMSMessageReceiver] JMS Worker [JMSWorker-1] Encountered
Axis Fault : The [action] cannot be processed at the receiver.
org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver.
        at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingF
        at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSu
        at org.apache.axis2.handlers.addressing.AddressingValidationHandler.chec
        at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invo
        at org.apache.axis2.engine.Phase.invoke(
        at org.apache.axis2.engine.AxisEngine.invoke(

On investigating, it seems that the AddressValidationHandler.checkAction will always throw
this exception as the following code indicated if the operation and service values are null.
  if ((msgContext.getAxisService() == null) || (msgContext.getAxisOperation() == null)) {
                    .triggerActionNotSupportedFault(msgContext, msgContext.getWSAAction());

Now here is the envelope that is generated by the stub and published in the JMS message:

&lt;?xml version="1.0" encoding="utf-8"?&gt;

            <a class="moz-txt-link-freetext" href=""></a>

I also noted that previous to invoking the handlers in the dispatch phase (i.e. in the pre-dispatch
phase), the AddressingInHandler successfully parses the wsa:Action info from the soap headers.
Should'nt this be responsible for setting the operation (getPrice) in this case?

I tried to find out why the messageContext was not getting filled with the serviceName. It
seems that in JMSMessageReceiver.createMessageContext, it looks for the servicename based
on the destinationName as shown in the following code:
Destination dest = message.getJMSDestination();
            String destinationName = null;
            if (dest instanceof Queue) {
                destinationName = ((Queue) dest).getQueueName();
            } else if (dest instanceof Topic) {
                destinationName = ((Topic) dest).getTopicName();

            String serviceName = jmsConFac.getServiceNameForDestination(destinationName);

However, the destination name in this case (JBOSS MQ) is 'requestQ'. Note that the services.xml
contains the following as the parameter:
    &lt;parameter name="transport.jms.Destination" locked="true"&gt;queue/requestQ&lt;/parameter&gt;

And the JMSConnectionFactory stores the mapping as follows in the destinations variable:


Hence the serviceName is returned as null since JBOSS returns requestQ and not queue/requestQ
as the destination name.
  <pre wrap=""><!---->You are spot on correct in your analysis, and earlier this
week I 
committed a patch that would fix the above, but unfortunately had to 
revert it back due to unit test failures as I didn't have time to 
investigate it due to commitments on Apache Synapse. I will promise to 
commit this patch with proper testing over this weekend and I think you 
could test it early next week and give me first hand feedback


To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href=""></a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href=""></a>

To unsubscribe, e-mail: <a class="moz-txt-link-abbreviated" href=""></a>
For additional commands, e-mail: <a class="moz-txt-link-abbreviated" href=""></a>


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message