axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Traud <stefan_tr...@yahoo.com>
Subject Re: [Axis2]: org.apache.axiom.om.OMException: Unable to locate the SOAP Part
Date Fri, 22 Mar 2013 13:13:35 GMT
Thanks Andreas!
AXIOM-389 was indeed the source of this issue. 

Not surprisingly I was able to reproduce the exception 'Part content ID cannot be blank for
non root MIME part' described in AXIOM-389 on win XP with Turkish locales, but not the 'Unable
to locate the SOAP part' exception that was raised at the Turkish institute.

Anyway, I added a quick fix to the client app to always use US locales and this solved it.

--stefan




________________________________
 Von: Andreas Veithen <andreas.veithen@gmail.com>
An: java-user <java-user@axis.apache.org> 
Gesendet: 12:42 Donnerstag, 21.März 2013
Betreff: Re: [Axis2]: org.apache.axiom.om.OMException: Unable to locate the SOAP Part
 
Could be related to AXIOM-389.

Andreas

On Thu, Mar 21, 2013 at 12:25 PM, Stefan Traud <stefan_traud@yahoo.com> wrote:
> We use an Axis2 (1.6.1) webservice and client (top-down design using ADB) to
> collect medical images (using MTOM).
>
> While this works smoothly all over the world, a customer in Turkey can not
> get rid of the following exception:
> (...)
> Caused by: org.apache.axis2.AxisFault: Unable to locate the SOAP part;
> content ID was 0.0785513db83d55a4a646b6640b9e0d2257813e7713c83dc3@apache.org
> <mailto:0.0785513db83d55a4a646b6640b9e0d2257813e7713c83dc3@apache.org>
>
>  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>  at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)
>  at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>  at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>  at ch.msmri.transfer.client.DicomTransferServiceStub.datasetUpload(Unknown
> Source)
>  ... 11 more
> Caused by: org.apache.axiom.om.OMException: Unable to locate the SOAP part;
> content ID was 0.0785513db83d55a4a646b6640b9e0d2257813e7713c83dc3@apache.org
> <mailto:0.0785513db83d55a4a646b6640b9e0d2257813e7713c83dc3@apache.org>
>  at org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Unknown
> Source)
>  at
> org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:41)
>  at
> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:179)
>  at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)
>  at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)
>  ... 17 more
>
> Not sure if the following info is of any help:
> - all communications run via https
> - Client runs on Windows XP/JRE 1.6.0_29-b11
> - The customer's institute uses no proxy server
> - The customer's institute uses a "Trend micro security agent", however
> added an exception for connections to our webserver (to exclude as possible
> source)
>
> Does anyone have an idea what could cause this exception?
> Any help is highly appreciated
> Thanks in advance
> --stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Mime
View raw message