You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by excess2 <ga...@yahoo.com> on 2008/12/31 21:17:37 UTC

Axis2 client request to IIS 5.0 returns a 500 error.

I need to use a web service residing on IIS 5.0 using axis2.

The ws returns a 500 error.

There must be something wrong with my request but I can't figure out the
problem.

The outgoing request looks like this (captured from wireshark).

POST
/arsys/services/ARService?server=arsp002.us.primus&webService=VOIP_SIP_Trouble_Ticket
HTTP/1.0

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

SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"

User-Agent: Axis2

Host: mcldevmidt01.us.primus

Content-Length: 556



<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><ns1:AuthenticationInfo
xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"
soapenv:mustUnderstand="0"><ns1:userName>Glen</ns1:userName><ns1:password>glen</ns1:password><ns1:locale></ns1:locale><ns1:timeZone></ns1:timeZone></ns1:AuthenticationInfo></soapenv:Header><soapenv:Body><ns1:OpGet
xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"><ns1:Ticket_Number>SIP000000000001</ns1:Ticket_Number></ns1:OpGet></soapenv:Body></soapenv:Envelope>

A working request from another project that uses weblogic looks like this

POST
/arsys/services/ARService?server=arsp002&webService=VOIP_SIP_Trouble_Ticket
HTTP/1.0

User-Agent: BEA WLW 8.1

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

SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"

Accept: application/soap+xml, text/xml, application/xml, */*

Host: mcldevmidt01.us.primus

Connection: Keep-Alive

Content-Length: 900



<SOAP-ENV:Envelope
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><urn:AuthenticationInfo
xmlns:urn="urn:VOIP_SIP_Trouble_Ticket"><aut:userName
xmlns:aut="AuthenticationInfo">Glen</aut:userName><aut:password
xmlns:aut="AuthenticationInfo">glen</aut:password><aut:locale
xmlns:aut="AuthenticationInfo"/><aut:timeZone
xmlns:aut="AuthenticationInfo"/><aut:authentication
xmlns:aut="AuthenticationInfo"/></urn:AuthenticationInfo></soapenv:Header>
<SOAP-ENV:Body>
<ns:OpGet xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10"><ns:Ticket_Number
xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10">SIP000000000001</ns:Ticket_Number></ns:OpGet></SOAP-ENV:Body>
</SOAP-ENV:Envelope>

My question is what's wrong with the first request (which fails with a 500
from the server) compared to the second one which works.

Thanks for any assistance you might provide.

G



-- 
View this message in context: http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21236655.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by Amila Suriarachchi <am...@gmail.com>.

On Tue, Jan 6, 2009 at 1:21 AM, excess2 <ga...@yahoo.com> wrote:

>
> The non-working request matches the wsdl.


wsdl2java tool assumes that the wsdl correctly describes the service. one
option is to change the wsdl
file to suite for the service and generate the code with that.

thanks,
Amila.

>
>
> Somehow the working request has apparently been tweaked.
>
> G
>
>
>
> Andreas Veithen-2 wrote:
> >
> > Can you check which of the two requests conforms to the WSDL?
> >
> > Andreas
> >
> > On Mon, Jan 5, 2009 at 20:21, excess2 <ga...@yahoo.com> wrote:
> >>
> >> Thanks!
> >>
> >> I see the problem you pointed out.
> >>
> >> However, I have no idea how to fix this.
> >>
> >> The stubs I'm using for the client were generated from a
> >> VOIP_SIP_Trouble_Ticket10 wsdl.
> >>
> >> The <urn:AuthenticationInfo xmlns:urn = "urn:VOIP_SIP_Trouble_Ticket10">
> >> is
> >> populated by stub code
> >>
> >> not by an explicit call.  How do I force it to VOIP_SIP_Trouble_Ticket
> >> instead?
> >>
> >> Is there an axis2 method that lets me override the default
> >> VOIP_SIP_Trouble_Ticket10 with VOIP_SIP_Trouble_Ticket?
> >>
> >> Thanks,
> >>
> >> G
> >>
> >>
> >>
> >> Andreas Veithen-2 wrote:
> >>>
> >>> The difference between the two requests is in the namespace URIs of
> >>> AuthenticationInfo and its children. In the first request all elements
> >>> are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
> >>> second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
> >>> children in "AuthenticationInfo".
> >>>
> >>> Andreas
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297434.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297928.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by excess2 <ga...@yahoo.com>.

The non-working request matches the wsdl.

Somehow the working request has apparently been tweaked.

G



Andreas Veithen-2 wrote:
> 
> Can you check which of the two requests conforms to the WSDL?
> 
> Andreas
> 
> On Mon, Jan 5, 2009 at 20:21, excess2 <ga...@yahoo.com> wrote:
>>
>> Thanks!
>>
>> I see the problem you pointed out.
>>
>> However, I have no idea how to fix this.
>>
>> The stubs I'm using for the client were generated from a
>> VOIP_SIP_Trouble_Ticket10 wsdl.
>>
>> The <urn:AuthenticationInfo xmlns:urn = "urn:VOIP_SIP_Trouble_Ticket10">
>> is
>> populated by stub code
>>
>> not by an explicit call.  How do I force it to VOIP_SIP_Trouble_Ticket
>> instead?
>>
>> Is there an axis2 method that lets me override the default
>> VOIP_SIP_Trouble_Ticket10 with VOIP_SIP_Trouble_Ticket?
>>
>> Thanks,
>>
>> G
>>
>>
>>
>> Andreas Veithen-2 wrote:
>>>
>>> The difference between the two requests is in the namespace URIs of
>>> AuthenticationInfo and its children. In the first request all elements
>>> are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
>>> second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
>>> children in "AuthenticationInfo".
>>>
>>> Andreas
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297434.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297928.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by Andreas Veithen <an...@gmail.com>.

Can you check which of the two requests conforms to the WSDL?

Andreas

On Mon, Jan 5, 2009 at 20:21, excess2 <ga...@yahoo.com> wrote:
>
> Thanks!
>
> I see the problem you pointed out.
>
> However, I have no idea how to fix this.
>
> The stubs I'm using for the client were generated from a
> VOIP_SIP_Trouble_Ticket10 wsdl.
>
> The <urn:AuthenticationInfo xmlns:urn = "urn:VOIP_SIP_Trouble_Ticket10"> is
> populated by stub code
>
> not by an explicit call.  How do I force it to VOIP_SIP_Trouble_Ticket
> instead?
>
> Is there an axis2 method that lets me override the default
> VOIP_SIP_Trouble_Ticket10 with VOIP_SIP_Trouble_Ticket?
>
> Thanks,
>
> G
>
>
>
> Andreas Veithen-2 wrote:
>>
>> The difference between the two requests is in the namespace URIs of
>> AuthenticationInfo and its children. In the first request all elements
>> are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
>> second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
>> children in "AuthenticationInfo".
>>
>> Andreas
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297434.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by excess2 <ga...@yahoo.com>.

Thanks!

I see the problem you pointed out.

However, I have no idea how to fix this.

The stubs I'm using for the client were generated from a
VOIP_SIP_Trouble_Ticket10 wsdl.

The <urn:AuthenticationInfo xmlns:urn = "urn:VOIP_SIP_Trouble_Ticket10"> is
populated by stub code

not by an explicit call.  How do I force it to VOIP_SIP_Trouble_Ticket
instead?

Is there an axis2 method that lets me override the default
VOIP_SIP_Trouble_Ticket10 with VOIP_SIP_Trouble_Ticket?

Thanks,

G

Andreas Veithen-2 wrote:
> 
> The difference between the two requests is in the namespace URIs of
> AuthenticationInfo and its children. In the first request all elements
> are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
> second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
> children in "AuthenticationInfo".
> 
> Andreas
> 
>  
> 

-- 
View this message in context: http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297434.html
Sent from the Axis - User mailing list archive at Nabble.com.

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by Andreas Veithen <an...@gmail.com>.

The difference between the two requests is in the namespace URIs of
AuthenticationInfo and its children. In the first request all elements
are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
children in "AuthenticationInfo".

Andreas

On Wed, Dec 31, 2008 at 21:17, excess2 <ga...@yahoo.com> wrote:
>
> I need to use a web service residing on IIS 5.0 using axis2.
>
> The ws returns a 500 error.
>
> There must be something wrong with my request but I can't figure out the
> problem.
>
> The outgoing request looks like this (captured from wireshark).
>
> POST
> /arsys/services/ARService?server=arsp002.us.primus&webService=VOIP_SIP_Trouble_Ticket
> HTTP/1.0
>
> Content-Type: text/xml; charset=UTF-8
>
> SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"
>
> User-Agent: Axis2
>
> Host: mcldevmidt01.us.primus
>
> Content-Length: 556
>
>
>
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><ns1:AuthenticationInfo
> xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"
> soapenv:mustUnderstand="0"><ns1:userName>Glen</ns1:userName><ns1:password>glen</ns1:password><ns1:locale></ns1:locale><ns1:timeZone></ns1:timeZone></ns1:AuthenticationInfo></soapenv:Header><soapenv:Body><ns1:OpGet
> xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"><ns1:Ticket_Number>SIP000000000001</ns1:Ticket_Number></ns1:OpGet></soapenv:Body></soapenv:Envelope>
>
> A working request from another project that uses weblogic looks like this
>
> POST
> /arsys/services/ARService?server=arsp002&webService=VOIP_SIP_Trouble_Ticket
> HTTP/1.0
>
> User-Agent: BEA WLW 8.1
>
> Content-Type: text/xml; charset=UTF-8
>
> SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"
>
> Accept: application/soap+xml, text/xml, application/xml, */*
>
> Host: mcldevmidt01.us.primus
>
> Connection: Keep-Alive
>
> Content-Length: 900
>
>
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><urn:AuthenticationInfo
> xmlns:urn="urn:VOIP_SIP_Trouble_Ticket"><aut:userName
> xmlns:aut="AuthenticationInfo">Glen</aut:userName><aut:password
> xmlns:aut="AuthenticationInfo">glen</aut:password><aut:locale
> xmlns:aut="AuthenticationInfo"/><aut:timeZone
> xmlns:aut="AuthenticationInfo"/><aut:authentication
> xmlns:aut="AuthenticationInfo"/></urn:AuthenticationInfo></soapenv:Header>
> <SOAP-ENV:Body>
> <ns:OpGet xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10"><ns:Ticket_Number
> xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10">SIP000000000001</ns:Ticket_Number></ns:OpGet></SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> My question is what's wrong with the first request (which fails with a 500
> from the server) compared to the second one which works.
>
> Thanks for any assistance you might provide.
>
> G
>
>
>
> --
> View this message in context: http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21236655.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>

Re: Axis2 client request to IIS 5.0 returns a 500 error.

Posted by Afkham Azeez <af...@gmail.com>.

If you look at the second request, there is a custom SOAP header that is
sent (some sort of custom authentication/UsernameToken protocol, not
WS-Sec). I assume that this header is validated on the server side.

On the Axis2 client you may need to set this custom header before sending
the request.

HTH
Azeez

On Thu, Jan 1, 2009 at 1:47 AM, excess2 <ga...@yahoo.com> wrote:

>
> I need to use a web service residing on IIS 5.0 using axis2.
>
> The ws returns a 500 error.
>
> There must be something wrong with my request but I can't figure out the
> problem.
>
> The outgoing request looks like this (captured from wireshark).
>
> POST
>
> /arsys/services/ARService?server=arsp002.us.primus&webService=VOIP_SIP_Trouble_Ticket
> HTTP/1.0
>
> Content-Type: text/xml; charset=UTF-8
>
> SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"
>
> User-Agent: Axis2
>
> Host: mcldevmidt01.us.primus
>
> Content-Length: 556
>
>
>
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> "><soapenv:Header><ns1:AuthenticationInfo
> xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"
>
> soapenv:mustUnderstand="0"><ns1:userName>Glen</ns1:userName><ns1:password>glen</ns1:password><ns1:locale></ns1:locale><ns1:timeZone></ns1:timeZone></ns1:AuthenticationInfo></soapenv:Header><soapenv:Body><ns1:OpGet
>
> xmlns:ns1="urn:VOIP_SIP_Trouble_Ticket10"><ns1:Ticket_Number>SIP000000000001</ns1:Ticket_Number></ns1:OpGet></soapenv:Body></soapenv:Envelope>
>
> A working request from another project that uses weblogic looks like this
>
> POST
> /arsys/services/ARService?server=arsp002&webService=VOIP_SIP_Trouble_Ticket
> HTTP/1.0
>
> User-Agent: BEA WLW 8.1
>
> Content-Type: text/xml; charset=UTF-8
>
> SOAPAction: "urn:VOIP_SIP_Trouble_Ticket10/OpGet"
>
> Accept: application/soap+xml, text/xml, application/xml, */*
>
> Host: mcldevmidt01.us.primus
>
> Connection: Keep-Alive
>
> Content-Length: 900
>
>
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> "><urn:AuthenticationInfo
> xmlns:urn="urn:VOIP_SIP_Trouble_Ticket"><aut:userName
> xmlns:aut="AuthenticationInfo">Glen</aut:userName><aut:password
> xmlns:aut="AuthenticationInfo">glen</aut:password><aut:locale
> xmlns:aut="AuthenticationInfo"/><aut:timeZone
> xmlns:aut="AuthenticationInfo"/><aut:authentication
> xmlns:aut="AuthenticationInfo"/></urn:AuthenticationInfo></soapenv:Header>
> <SOAP-ENV:Body>
> <ns:OpGet xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10"><ns:Ticket_Number
>
> xmlns:ns="urn:VOIP_SIP_Trouble_Ticket10">SIP000000000001</ns:Ticket_Number></ns:OpGet></SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> My question is what's wrong with the first request (which fails with a 500
> from the server) compared to the second one which works.
>
> Thanks for any assistance you might provide.
>
> G
>
>
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21236655.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>


-- 
Thanks
Afkham Azeez

Blog: http://afkham.org
Developer Portal: http://www.wso2.org
WSAS Blog: http://wso2wsas.blogspot.com
Company: http://wso2.com
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760