axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Neate" <bne...@alarmpoint.com>
Subject RE: Error : "Transport level information does not match with SOAP Message namespace URI"
Date Tue, 16 Sep 2008 21:41:21 GMT
Sorry I included the wrong response from axis2.

 

<?xml version='1.0' encoding='UTF-8'?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">

      <soapenv:Header>

         <wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>

      </soapenv:Header>

      <soapenv:Body>

         <soapenv:Fault>

            <faultcode>env:VersionMismatch</faultcode>

            <faultstring>Transport level information does not match with SOAP Message
namespace URI</faultstring>

            <detail />

         </soapenv:Fault>

      </soapenv:Body>

   </soapenv:Envelope>

 

Is the correct fault being sent back.

 

From: Brian Neate [mailto:bneate@alarmpoint.com] 
Sent: Tuesday, September 16, 2008 5:26 PM
To: axis-user@ws.apache.org
Subject: Error : "Transport level information does not match with SOAP Message namespace URI"

 

Hello,

 

Iā€™m trying to write a axis2 web service to consume web service requests sent from a third
party application.  The problem I am having is that when the third party application sends
web service requests to my axis2 web service it gets a "Transport level information does not
match with SOAP Message namespace URI" fault back.  I believe the problem is that the request
is being made using SOAP 1.2 (http://www.w3.org/2003/05/soap-envelope) but there is also a
SOAPAction: ā€œā€ header being added to the http request.  Is there any way to tell axis2
to ignore the extra http header and continue to process the request using SOAP 1.2?

 

I need to complete the project I am working on very quickly and any help would be greatly
appreciated.

 

Sample request:

POST /api/services/NNMWSEvent HTTP/1.1

SOAPAction: ""

Content-Type: text/xml; charset=UTF-8

JBoss-Remoting-Version: 22

User-Agent: JBossRemoting - 2.2.2.SP7 (Bluto)

Host: 127.0.0.1:8881

Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2

Connection: keep-alive

 

<env:Envelope xmlns:env='http://www.w3.org/2003/05/soap-envelope' xmlns:wsa='http://www.w3.org/2005/08/addressing'
xmlns:wse='http://schemas.xmlsoap.org/ws/2004/08/eventing'>

   <env:Header>

      <wsa:Action>http://notification.sdk.nms.ov.hp.com/nms-sdk-notify/IncidentNotificationSource/Notification</wsa:Action>

      <wsa:To>http://neate.bounceme.net:8881/api/services/NNMWSEvent</wsa:To>

   </env:Header>

   <env:Body>

      <sys:onNotification xmlns:sys='http://notification.sdk.nms.ov.hp.com/nms-sdk-notify'>

         <arg0>

            <id>64424516155</id>

            <uuid>fd6b08c9-9c78-4214-8777-ab30da17e5f07</uuid>

            <name>AddressNotResponding7</name>

            <sourceUuid>4a9596d2-2a70-43a9-97b5-b255980b5db5d</sourceUuid>

            <sourceName>192.168.168.96d</sourceName>

            <sourceNodeUuid>87c1b801-d12b-4c02-a6ce-2b4b1d91039c11</sourceNodeUuid>

            <sourceNodeName>192.168.168.9611</sourceNodeName>

            <lifecycleState>com.hp.nms.incident.lifecycle.Registered11</lifecycleState>

            <severity>CRITICALb</severity>

            <priority>com.hp.nms.incident.priority.Noneb</priority>

            <category>com.hp.nms.incident.category.Faultb</category>

            <family>com.hp.nms.incident.family.Address9</family>

            <nature>ROOTCAUSE9</nature>

            <origin>MANAGEMENTSOFTWARE9</origin>

            <duplicateCount>011</duplicateCount>

            <priority>com.hp.nms.incident.priority.Noneb</priority>

            <rcaActive>truec</rcaActive>

            <formattedMessage>Address Not Responding13</formattedMessage>

            <originOccurrenceTime>2008-09-16T14:04:15.278-07:0017</originOccurrenceTime>

            <firstOccurrenceTime>2008-09-16T14:04:15.278-07:0016</firstOccurrenceTime>

            <lastOccurrenceTime>2008-09-16T14:04:15.278-07:0015</lastOccurrenceTime>

            <created>2008-09-16T14:04:16.200-07:00</created>

            <updateTime/>

            <previousLifecycleState/>

            <previousRcaActive/>

            <cias>

               <name>com.hp.ov.nms.apa.symptom7</name>

               <type>STRING7</type>

               <value>ICMPNoResponse8</value>

            </cias>

         </arg0>

      </sys:onNotification>

   </env:Body>

</env:Envelope>

 

Axis2 Response:

<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing">

   <soapenv:Header>

      <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>

   </soapenv:Header>

   <soapenv:Body>

      <soapenv:Fault>

         <soapenv:Code>

            <soapenv:Value>soapenv:Sender</soapenv:Value>

            <soapenv:Subcode>

               <soapenv:Value>wsa:InvalidAddressingHeader</soapenv:Value>

               <soapenv:Subcode>

                  <soapenv:Value>wsa:ActionMismatch</soapenv:Value>

               </soapenv:Subcode>

            </soapenv:Subcode>

         </soapenv:Code>

         <soapenv:Reason>

            <soapenv:Text xml:lang="en-US">A header representing a Message Addressing
Property is not valid and the message cannot be processed</soapenv:Text>

         </soapenv:Reason>

         <soapenv:Detail>

            <wsa:ProblemHeaderQName>wsa:Action</wsa:ProblemHeaderQName>

         </soapenv:Detail>

      </soapenv:Fault>

   </soapenv:Body>

</soapenv:Envelope>

 

 

Thanks,

Brian

 

Mime
View raw message