[
https://issues.apache.org/jira/browse/AXIS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcos Pereira updated AXIS-2839:
---------------------------------
Summary: Axisfault 401 during web service consuming with weblogic 10 and
Axis 1.4 (was: Axisfault 401 and consuming web service with weblogic 10 and
Axis 1.4)
> Axisfault 401 during web service consuming with weblogic 10 and Axis 1.4
> ------------------------------------------------------------------------
>
> Key: AXIS-2839
> URL: https://issues.apache.org/jira/browse/AXIS-2839
> Project: Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: Eclipse WTS 3.3
> Weblogic 10.3
> JVM 1.5
> Reporter: Marcos Pereira
> Priority: Critical
> Labels: security
>
> I created some Webservice client( axis 1.4) in my WebApp that consumes a
> extenal vendor. The clients works fine when Debug my code in Java aplication
> mode. But does not work in my Integration environment ( Weblogic local
> server).
> Any idea for this issue ??
> This my Client code:
> public String getLocacaoPorPorcoReq (BigDecimal codigoPoco) throws
> RemoteException, Exception {
>
> WsLoadConfig wsLoadConfig = new WsLoadConfig();
> wsLoadConfig.readProperties();
> String getLocacaoPorPocoResponse = "";
> try {
> PocoServiceService service = new
> PocoServiceServiceLocator();
> java.net.URL endpoint = new
> java.net.URL(wsLoadConfig.getEndPointPocoWsURL());
>
> PocoServiceServiceSoapBindingStub bindingStub = new
> PocoServiceServiceSoapBindingStub(endpoint, service);
>
> bindingStub.setUsername(wsLoadConfig.getWsUsername());
> bindingStub.setPassword(wsLoadConfig.getWsPassword());
> getLocacaoPorPocoResponse =
> bindingStub.getLocacaoPorPoco(codigoPoco);
> } catch (RemoteException e) {
> e.printStackTrace();
> }
> return getLocacaoPorPocoResponse;
> The Request Created :
> POST /EP/PocoService HTTP/1.1
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related, text/*
> User-Agent: Axis/1.4
> Host: gdiepwlidsv.ep.petrobras.com.br:80
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: ""
> Content-Length: 460
> Connection: close
> Authorization: Basic c2FFZG9jOmpwbGtoIzQy
> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><getPocosListPorSigla
>
> xmlns="http://br/com/petrobras/transacional/servicosespecializadosep/services";><codigoUnidadeOperativa
>
> xsi:nil="true"/><siglaPoco>9-BI-19D-RJS</siglaPoco></getPocosListPorSigla></soapenv:Body></soapenv:Envelope>
> Response:
> HTTP/1.1 401 Authorization Required
> Date: Tue, 22 Feb 2011 17:53:47 GMT
> Server: Apache/2.2.3 (CentOS)
> Content-Length: 1518
> WWW-Authenticate: Basic realm="WebLogic Server"
> X-Powered-By: Servlet/2.4 JSP/2.0
> Connection: close
> Content-Type: text/html; charset=UTF-8
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
> <HTML>
> <HEAD>
> <TITLE>Error 401--Unauthorized</TITLE>
> <META NAME="GENERATOR" CONTENT="WebLogic Server">
> </HEAD>
> <BODY bgcolor="white">
> <FONT FACE=Helvetica><BR CLEAR=all>
> <TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
> <FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 401--Unauthorized</H2>
> </FONT></TD></TR>
> </TABLE>
> <TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100%
> BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica"
> SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol --
> HTTP/1.1</i>:</H3>
> </FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.2 401 Unauthorized</H4>
> </FONT><P><FONT FACE="Courier New">The request requires user authentication.
> The response MUST include a WWW-Authenticate header field (section 14.46)
> containing a challenge applicable to the requested resource. The client MAY
> repeat the request with a suitable Authorization header field (section 14.8).
> If the request already included Authorization credentials, then the 401
> response indicates that authorization has been refused for those credentials.
> If the 401 response contains the same challenge as the prior response, and
> the user agent has already attempted authentication at least once, then the
> user SHOULD be presented the entity that was given in the response, since
> that entity MAY include relevant diagnostic information. HTTP access
> authentication is explained in section 11.</FONT></P>
> </FONT></TD></TR>
> </TABLE>
> </BODY>
> </HTML>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
