We Keep Coding

Apache axis admin client process - 401 error

What does org.apache.axis.client.AdminClient.process() do?
Is there any authentication/authorization happening behind the scenes on invoking this function?
We have a legacy SOAP based web service built using Apache Axis 1. On application start up, the web service try to deploy automatically using the AdminClient.process(). Everything was working fine until our client implemented sso and now the soap service throws the below exception.
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (401)401
faultActor:
faultNode:
faultDetail:
{}:return code: 401
HTTP Status 401 – Unauthorized: The request has not been applied because it lacks valid authentication credentials for the target resource. VMware tc Runtime 9.0.65.A.RELEASE&lt
{http://xml.apache.org/axis/}HttpErrorCode:401
(401)401
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1792)
at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
Apparently the SSO isn't configured properly. But what does the adminClient.process(String[] arg0)) does internally?Why does it complain about authentication while its merely invoking a http url?
Java code:
AdminClient ac = new AdminClient();
String result = ac.process(
new String[] {
"-p" + API_PORT,
"-l"+API_PROTOCOL+"://"+API_HOST+":"
+ API_PORT
+ "/"+CONTEXT+"/axis/AdminService",
deploymentdescriptorfile });
Code is deployed in VMware TC server

Different result/output for same wsdl in Postman, SOAP UI, jdeveloper Http Analyzer

I have a wsdl url which is giving different result when I am testing with Postman, SOAP UI, Jdeveloper Http Analyzer even tough passing same request header and body in all tools.
In Postman, Jdeveloper Http Analyzer it's wsdl returning same 500-Internal server error.
In SOAP UI, it's returning correct result.
I have created Custom Java client application in jdeveloper to consume webservice, in that I am getting below error
The Error
Exception in thread "main" com.sun.xml.internal.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/xml Supported ones are: [text/xml]
at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:220)
at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:151)
at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:299)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:268)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:217)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)
at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:95)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:178)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
at com.sun.proxy.$Proxy36.getService(Unknown Source)
at someClient.SomeClient.main(WaselClient.java:23)
How can i solve this issue?

When I am importing wsdl into SOAPUI request payload is loading without spaces in the header parameter.
for eg., content-type=”text/xml;charset=utf-8”(check there is no gap between xml; and charset),
where as in postman and jdeveloper http analyzer request payload is loading with spaces in the header parameter. content-type=”text/xml; charset=utf-8”(check there is a gap between xml; and charset).
Due to this it was giving different result.

Unable to parse SOAP response

I am using JAX-WS to call a SOAP webservice. While parsing a SOAP response getting below exception. My SOAP client is a JAR which is running inside another web application deployed in Weblogic server.
javax.xml.soap.SOAPException: Error parsing envelope: most likely due to an invalid SOAP message.: Unexpected EOF in prolog
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2139)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2045)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1134)
at oracle.j2ee.ws.saaj.util.ResettableXMLStreamReader.next(ResettableXMLStreamReader.java:218)
at oracle.j2ee.ws.saaj.soap.StaxHandler.moveNext(StaxHandler.java:213)
at oracle.j2ee.ws.saaj.soap.StaxHandler.staxParse(StaxHandler.java:117)
at oracle.j2ee.ws.saaj.soap.StaxHandler.staxParse(StaxHandler.java:105)
at oracle.j2ee.ws.saaj.soap.StaxHandler.staxParse(StaxHandler.java:88)
at oracle.j2ee.ws.saaj.soap.AbstractSOAPImplementation.getStaXParsedEnvelope(AbstractSOAPImplementation.java:235)
at oracle.j2ee.ws.saaj.soap.AbstractSOAPImplementation.createEnvelope(AbstractSOAPImplementation.java:70)
Surprisingly I am able to print the SOAP response in the logs.

SAXParseException: XML document structures must start and end within the same entity

I'm calling a web service from an Apache Axis 1.4 Java client. The call reaches the server correctly but the client is throwing this exception after approximately a couple of minutes:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
faultActor:
faultNode:
faultDetail:
The exception is not always the same. Sometimes it specifies a specific element in the response:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXParseException: The element type "name" must be terminated by the matching end-tag "</name>".
faultActor:
faultNode:
faultDetail:
The web service call I am making returns a large amount of data. If I configure the server to return less data, the call is completed successfully.
Note: Although I'm not getting any client-side time out exceptions, I tried increasing the value for the timeout to five minutes, but this had no effect.

Apache Axis 1.4 supports HTTP 1.0 by default. The server being called is using HTTP 1.1, which apparently supports Chunked Transfer Encoding.
From w3.org:
The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size indicator, followed by an OPTIONAL trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information necessary for the recipient to verify that it has received the full message.
Which means that Axis 1.4 knows nothing about chunks in the HTTP response and probably closes the connection before receiving all the chunks. When it attempts to deserialize the SOAP message, it complains that the XML is not well formed and is missing some closing tag, which is expected because it doesn't have the complete SOAP response.
The solution is to configure Axis to use CommonsHTTPSender which supports HTTP 1.1 by default. You do this by adding a client-config.wsdd on your classpath under org/apache/axis/client/client-config.wsdd with the following content:
<?xml version="1.0" encoding="UTF-8"?>
<deployment name="ApacheCommonsHTTPConfig" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
<globalConfiguration>
<parameter name="disablePrettyXML" value="true"/>
<parameter name="enableNamespacePrefixOptimization" value="false"/>
</globalConfiguration>
<transport name="http" pivot="java:org.apache.axis.transport.http.CommonsHTTPSender" />
<transport name="local" pivot="java:org.apache.axis.transport.local.LocalSender" />
<transport name="java" pivot="java:org.apache.axis.transport.java.JavaSender" />
</deployment>
The relevant setting is the transport with name "http".
Most application servers already have this class loaded in their classpath, in case it isn't you need to add the Apache Commons HTTP jar to your classpath.

Getting Exception faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client

I am using axis1. While applying command cryptic for my soap I am getting an exception like below. Below are the details.
[ERROR] 2011-05-06 09:23:56,073 [MyAmeadeusTest] (MyAmeadeusTest.java:crypticCommand:278)
11|Session|
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: 11|Session|
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: 11|Session|
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601)
Help would be appreciated.

You need to do one of two things:
1) Look on the web server that your SOAP requests are going to. In those logs you'll probably find the Exception being thrown on that side that is turning into the AxisFault.
2) Use something like WireShark to trace the HTTP traffic. Although this won't give you a lot of information beyond what you already have, it will prove that the AxisFault is basically a client-side representation of an Exception thrown on the server side.
The stack trace you get in this instance (i.e., from SoapFaultBuilder) is entirely misleading, as it's the stack trace of the code that is creating a client-side representation of the server error rather than the server-side stack trace showing the actual problem.