PnR fails: Transport level info mismatch

[akaraivanov]

Hi

I am trying to run ProvideAndRegister to Hieos-1.2 repository running on linux. Everything should be setup ok. When I try to do ProvideAndRegister I get an exception (seen on the client/submitting side as):

Caused by: javax.xml.ws.soap.SOAPFaultException: Transport level information does not match with SOAP Message namespace URI
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72)
        at org.jboss.ws.core.jaxws.binding.SOAP12BindingJAXWS.throwFaultException(SOAP12BindingJAXWS.java:117)
        at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)

I know what the error means but I am not sure why it happens. I would like to enable axis2 to produce stack traces but cannot make it to do it. I tried changing:

  sendStacktraceDetailsWithFaults=true
  DrillDownToRootCauseForFaultReason=true

in

glassfish/domains/domain1/applications/j2ee-modules/axis2/WEB-INF/conf/axis2.xml
as well as the one contained in glassfish/domains/domain1/autodeploy/axis2.war
but with not effect.

Any ideas how I can diagnose this?

Thanks
Alex.

[Bernie Thuman]

This looks like a client-side issue versus a HIEOS server-side issue.  We do not use JAXWS.  Have you tried TCPMON to see if a message is being sent to the server?

[akaraivanov]

Yes, message is sent. It could easily be a client issue - I can see the message seems different that in my other xds setup with different repo. The beginning of the message is at the bottom of the post. Do you know how to enable server side traces in hieos - especially by axis2? My changes in axis2.xml do not have any effect. May be I am changing a wrong copy.

Here is the beginning of the message:

POST /axis2/services/xdsrepositoryb HTTP/1.1
SOAPAction: \\\"urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b\\\"
Content-Type: multipart/related; type=\\\"application/xop+xml\\\"; start=\\\"<rootpart@ws.jboss.org>\\\";
        start-info=\\\"text/xml\\\";
        boundary=\\\"---=_Part_226_711946624.1341407161389\\\"
JBoss-Remoting-Version: 22
User-Agent: JBossRemoting - 2.2.2.SP8
Host: fire:8080
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Transfer-Encoding: chunked

3f9

----=_Part_226_711946624.1341407161389
Content-Type: application/xop+xml; type=\\\"text/xml\\\"
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart@ws.jboss.org>

<env:Envelope xmlns:env=\\\'[http://www.w3.org/2003/05/soap-envelope\\](http://www.w3.org/2003/05/soap-envelope%5C%5C%5C)'>
<env:Header>

[akaraivanov]

The forum software at SF.net does not like when I post log messages - had to abbreviate it a lot. Here is the next lines from it.

<wsa:To xmlns:wsa=\'[http://www.w3.org/2005/08/addressing](http://www.w3.org/2005/08/addressing%5C)'>http://fire:8080/axis2/services/xdsrepositoryb</wsa:To>

[akaraivanov]

For the record. Using a patched jbossws-core.jar on my side fixed the problem.