Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 13243 invoked from network); 6 Feb 2005 15:36:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 6 Feb 2005 15:36:15 -0000 Received: (qmail 11788 invoked by uid 500); 6 Feb 2005 15:36:07 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 11773 invoked by uid 500); 6 Feb 2005 15:36:07 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 11760 invoked by uid 99); 6 Feb 2005 15:36:07 -0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=FORGED_RCVD_HELO,HTML_50_60,HTML_MESSAGE,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from host-64-65-202-3.pro.choiceone.net (HELO contextmedia.com) (64.65.202.3) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 06 Feb 2005 07:36:05 -0800 Received: from ppeddi ([192.168.1.40]) by contextmedia.com ; Sun, 06 Feb 2005 10:35:55 -0500 Message-ID: <2ae201c50c61$676bb480$aa87a8c0@ppeddi> From: "Praveen Peddi" To: References: <2ac601c50b39$a2bf13c0$aa87a8c0@ppeddi> <19e0530f05020505475c3f39c@mail.gmail.com> <2ad001c50ba4$9c745960$aa87a8c0@ppeddi> <19e0530f050205095011ba12cd@mail.gmail.com> Subject: Re: Is latest nightly build stable Date: Sun, 6 Feb 2005 10:34:53 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_2ADF_01C50C37.7E63A000" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Rcpt-To: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_2ADF_01C50C37.7E63A000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Srinivas, Thanks a lot for checking the fix. I tried the latest nightly build = dated Feb 6th. It still throws Nullpointer. But its in a different place = now. I think XML parser is now throwing nullpointer. After debugging the cvs code (assuming the cvs code code is same as = Feb6th's nightly build), I found that the nullpointer is thrown in = DeserializationContext.parse method at line 227. Following is the snippet: public void parse() throws SAXException { if (inputSource !=3D null) { SAXParser parser =3D XMLUtils.getSAXParser(); try { = parser.setProperty("http://xml.org/sax/properties/lexical-handler", = this); parser.parse(inputSource, this); //Nullpointer is thrown = here try { // cleanup - so that the parser can be reused. {some code here} } My soap enevlope looks as follows: ISAdmin ISAdmin One thing I noticed is that the xml parser it found is = weblogic.xml.jaxp.RegistrySAXParser. Even if it is coming from = weblogic.jar, I think its still the bug of Axis since axis is sending = invalid content to xml parser. Would it be possible to fix this = exception and test with weblogic. When you are testing with another = server, it is probably working fine but not in weblogic. In fact I don't = mind testing it with weblogic once I make the cvs build work. I checked out cvs code but could not build. Where can I find the process = of building cvs code. It looks like xerces and other libraries in the = classpath so it is giving me compile time errors. Thanks Praveen ----- Original Message -----=20 From: "Davanum Srinivas" To: Sent: Saturday, February 05, 2005 12:50 PM Subject: Re: Is latest nightly build stable >I checked ina fix. please take latest CVS or tonight's nightly. >=20 > -- dims >=20 >=20 > On Sat, 5 Feb 2005 12:03:27 -0500, Praveen Peddi > wrote: >> =20 >> There is no stack trace. The code is not logging the runtime = exception. I >> didn't see any exceptions in my log file.=20 >> =20 >> All I know is the exception is caught at line 324 (in my 1.2 rc2 = code). >> Following is the snippet where I saw the exception. My comments are = in red >> font.=20 >> =20 >> public void invoke(MessageContext msgContext) throws AxisFault {=20 >> =20 >> {some code here}=20 >> =20 >> // Ensure that if we get SOAP1.2, then reply using = SOAP1.2=20 >> =20 >> = if(msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants() = !=3D >> null) { // nullpointer is thrown here >> SOAPConstants soapConstants =3D >> msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants(); >> msgContext.setSOAPConstants(soapConstants); >> }=20 >> =20 >> {some code here}=20 >>=20 >> =20 >> =20 >> catch (AxisFault e) { >> throw e; >> } catch (Exception e) {//exception is caught and AxisFault is = thrown >> w/o even logging >> // Should we even bother catching it ? >> throw AxisFault.makeFault(e);=20 >> =20 >> } finally { >> // restore previous state >> setCurrentMessageContext(previousContext); >> }=20 >> }=20 >> =20 >> =20 >> BTW is there a stable build that works with weblogic 8.1.3 where I = can use >> document style webservices. Axis1.1 doesn't seem to support document = style >> properly. 1.2 RC2 release have bug with weblogic 8.1.3. Nightly build = is not >> stable. I would gretaly appreciate if someone can point me to a = stable build >> that works with weblogic8.1.3.=20 >> =20 >> Thanks=20 >> Praveen >> =20 >> =20 >> =20 >> ----- Original Message -----=20 >> From: "Davanum Srinivas" =20 >> To: =20 >> Sent: Saturday, February 05, 2005 8:47 AM=20 >> Subject: Re: Is latest nightly build stable=20 >>=20 >> > Praveen, >> >=20 >> > please send the stack trace. >> >=20 >> > -- dims >> >=20 >> >=20 >> > On Fri, 4 Feb 2005 23:17:41 -0500, Praveen Peddi >> > wrote: >> >> =20 >> >> We were using 1.1 and I tried to move to 1.2 RC2 but it doesn't = seem to >> work >> >> with weblogic 8.1.3 due to bug >> >> http://issues.apache.org/jira/browse/AXIS-1683. I see that Davanam >> Srinivas >> >> fixed this bug on Dec 04 which means RC2 also doesn't have this. = So I >> tried >> >> to get latest nightly build dated feb4. That seemed to have fixed = the >> above >> >> bug but I can use any of services.=20 >> >> =20 >> >> I get the NullPointerException.=20 >> >> =20 >> >> I don't see any errors in the log file but after debugging Axis = code I >> found >> >> the error at line 279 of org.apache.axis.server.AxisServer.java (I >> actually >> >> attached 1.2RC2 code with Feb4th nightly build so I am very sure = if its >> line >> >> 279 but it is surely in AxisServer.java).=20 >> >> =20 >> >> Doesn't anyone know about this error.=20 >> >> =20 >> >> Praveen=20 >> >> =20 >> >> =20 >> >> =20 >> >> =20 >> >> =20 >> >> **************************************************************=20 >> >> Praveen Peddi >> >> Sr Software Engg, Context Media, Inc.=20 >> >> email:ppeddi@contextmedia.com=20 >> >> Tel: 401.854.3475=20 >> >> Fax: 401.861.3596=20 >> >> web: http://www.contextmedia.com=20 >> >> **************************************************************=20 >> >> Context Media- "The Leader in Enterprise Content Integration"=20 >> >> =20 >> >=20 >> >=20 >> > --=20 >> > Davanum Srinivas - http://webservices.apache.org/~dims/ >> >=20 >=20 >=20 > --=20 > Davanum Srinivas - http://webservices.apache.org/~dims/ ------=_NextPart_000_2ADF_01C50C37.7E63A000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Srinivas,

Thanks a lot for checking the fix. I = tried the=20 latest nightly build dated Feb 6th. It still throws Nullpointer. But its = in a=20 different place now. I think XML parser is now throwing=20 nullpointer.

After debugging the cvs code (assuming = the cvs code=20 code is same as Feb6th's nightly build), I found that the = nullpointer is=20 thrown in DeserializationContext.parse method at line 227.

Following is the snippet:

public void parse() throws=20 SAXException
   =20 {
        if (inputSource !=3D = null)=20 {
           =20 SAXParser parser =3D=20 XMLUtils.getSAXParser();
       &nb= sp;   =20 try=20 {
           &n= bsp;   =20 parser.setProperty("http://xml.org/sax/properties/lexical-handler",=20 this);
          &nb= sp;    =20 parser.parse(inputSource, this); //Nullpointer is = thrown=20 here

&nbs= p; =20 try=20 {
&n= bsp; =20 // cleanup - so that the parser can be reused.

=20 {some code=20 here}

}

My soap enevlope looks as = follows:

<?xml version=3D"1.0" encoding=3D"utf-8"?>
<soap:Envelope = xmlns:soap=3D"http://schemas.xmlsoap= .org/soap/envelope/"=20 xmlns:soapenc=3D"http://schemas.xmlsoap= .org/soap/encoding/"=20 xmlns:tns=3D"http://localhost:7001/axis/services/CMISOAPAuthenticationService"=20 xmlns:types=3D"http://localhost:7001/axis/services/CMISOAPAuthenticationSe= rvice/encodedTypes"=20 xmlns:xsi=3D"http://www.w3.org/2001= /XMLSchema-instance"=20 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchem= a">
<soap:Body=20 soap:encodingStyle=3D"http://schemas.xmlsoap= .org/soap/encoding/">
  <q1:login=20 xmlns:q1=3D"http://soap.session.ip.c= ontextmedia.com">
   <userID=20 xsi:type=3D"xsd:string">ISAdmin</userID>
   &l= t;password=20 xsi:type=3D"xsd:string">ISAdmin</password>
  </q= 1:login>
</soap:Body>
</soap:Envelope><= /P>

One thing I noticed is that the xml = parser it found=20 is weblogic.xml.jaxp.RegistrySAXParser. Even if it is = coming from=20 weblogic.jar, I think its still the bug of Axis since axis is = sending=20 invalid content to xml parser. Would it be possible to fix this = exception and=20 test with weblogic. When you are testing with another server, it is = probably=20 working fine but not in weblogic. In fact I don't mind testing it with = weblogic=20 once I make the cvs build work.

I checked out cvs code but could not = build. Where=20 can I find the process of building cvs code. It looks like xerces and = other=20 libraries in the classpath so it is giving me compile time = errors.

Thanks

Praveen

----- Original Message -----

From: "Davanum Srinivas" <davanum@gmail.com>

To: <axis-user@ws.apache.org>

Sent: Saturday, February 05, 2005 12:50 = PM

Subject: Re: Is latest nightly build=20 stable

>I checked ina fix. please take latest CVS or tonight's=20 nightly.
>
> -- dims
>
>
> On Sat, 5 = Feb 2005=20 12:03:27 -0500, Praveen Peddi
> <ppeddi@contextmedia.com>=20 wrote:
>>
>> There is no stack trace. The code = is not=20 logging the runtime exception. I
>> didn't see any exceptions = in my log=20 file.
>>
>> All I know is the exception = is=20 caught at line 324 (in my 1.2 rc2 code).
>> Following is the = snippet=20 where I saw the exception. My comments are in red
>> font.=20
>>
>> public void invoke(MessageContext=20 msgContext) throws AxisFault {
>>  =20
>>          &= nbsp; =20 {some code here}
>>  =20
>>          &= nbsp;     =20 // Ensure that if we get SOAP1.2, then reply using SOAP1.2=20
>>          &= nbsp;    =20
>>=20 if(msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants()=20 !=3D
>> null) { // nullpointer is thrown=20 here
>>         &nb= sp;          =20 SOAPConstants soapConstants =3D
>>=20 msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants();
&= gt;>           =          =20 msgContext.setSOAPConstants(soapConstants);
>>   =             &= nbsp;=20 }
>>  =20
>>          &= nbsp; =20 {some code here}
>>
>> =
>>  =20
>> catch (AxisFault e)=20 {
>>          =   =20 throw e;
>>         } = catch=20 (Exception e) {//exception is caught and AxisFault is thrown
>> = w/o=20 even=20 logging
>>         =    =20 // Should we even bother catching it=20 ?
>>          =   =20 throw AxisFault.makeFault(e);
>>  =20
>>         } finally=20 {
>>          =   =20 // restore previous=20 state
>>         &n= bsp;  =20 setCurrentMessageContext(previousContext);
>>   &= nbsp;    =20 }
>> }
>>
>>   =
>>=20 BTW is there a stable build that works with weblogic 8.1.3 where I can=20 use
>> document style webservices. Axis1.1 doesn't seem to = support=20 document style
>> properly. 1.2 RC2 release have bug with = weblogic=20 8.1.3. Nightly build is not
>> stable. I would gretaly = appreciate if=20 someone can point me to a stable build
>> that works with=20 weblogic8.1.3.
>>
>> Thanks
>> = Praveen
>>
>>   =
>>  =20
>> ----- Original Message -----
>> From: "Davanum = Srinivas"=20 <davanum@gmail.com> =
>> To:=20 <axis-user@ws.apache.org>=20
>> Sent: Saturday, February 05, 2005 8:47 AM
>> = Subject: Re:=20 Is latest nightly build stable
>>
>> >=20 Praveen,
>> >
>> > please send the stack=20 trace.
>> >
>> > -- dims
>> > =
>>=20 >
>> > On Fri, 4 Feb 2005 23:17:41 -0500, Praveen=20 Peddi
>> > <ppeddi@contextmedia.com>=20 wrote:
>> >>
>> >> We were using = 1.1 and I=20 tried to move to 1.2 RC2 but it doesn't seem to
>> = work
>>=20 >> with weblogic 8.1.3 due to bug
>> >> http://issues.apache.org/jira/browse/AXIS-1683. I see that Davanam
>> Srinivas
>> >> = fixed this=20 bug on Dec 04 which means RC2 also doesn't have this. So I
>>=20 tried
>> >> to get latest nightly build dated feb4. That = seemed=20 to have fixed the
>> above
>> >> bug but I can = use any=20 of services.
>> >>
>> >> I = get the=20 NullPointerException.
>> >>
>> = >> I=20 don't see any errors in the log file but after debugging Axis code = I
>>=20 found
>> >> the error at line 279 of=20 org.apache.axis.server.AxisServer.java (I
>> = actually
>>=20 >> attached 1.2RC2 code with Feb4th nightly build so I am very = sure if=20 its
>> line
>> >> 279 but it is surely in=20 AxisServer.java).
>> >>
>> = >>=20 Doesn't anyone know about this error.
>> >>  =20
>> >> Praveen
>> >>   =
>>=20 >>
>> >>
>>=20 >>
>> >>
>> = >>=20 ************************************************************** =
>>=20 >> Praveen Peddi
>> >> Sr Software Engg, Context = Media,=20 Inc.
>> >> email:ppeddi@contextmedia.com
>> = >>=20 Tel: 401.854.3475
>> >> Fax: 401.861.3596=20
>> >> web: http://www.contextmedia.com=20
>> >>=20 ************************************************************** =
>>=20 >> Context Media- "The Leader in Enterprise Content Integration"=20
>> >>
>> >
>> > =
>>=20 > --
>> > Davanum Srinivas - http://webservices.apache.org/~dims/
>> >
>
>
> --
> Davanum = Srinivas -=20 http://webservices.apache.org/~dims/ ------=_NextPart_000_2ADF_01C50C37.7E63A000--