axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Moore <amo...@ciphergen.com>
Subject RE: 1.0 Bugzilla Scrub & two unfiled exceptions
Date Tue, 20 Aug 2002 05:10:57 GMT
Update:

I captured the response XML and have added it (munged) to bugzilla here:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11706

It contains the response that generated an ArrayStoreException.

Assuming the response is both well formed and valid - it seems that the
problem must be on the client side.

Comments?

alan


> -----Original Message-----
> From: Alan Moore 
> Sent: Wednesday, August 14, 2002 4:12 PM
> To: 'axis-dev@xml.apache.org'
> Subject: RE: 1.0 Bugzilla Scrub & two unfiled exceptions
> 
> 
> Russell,
> 
> I can't get a tcpmon trace because after a bunch of 
> request/response cycles it runs out of memory (our responses 
> are quite large.)
> 
> Instead, I am going to use ethereal to capture the packets 
> off the wire.
> 
> I figured that the ArrayStoreException was on the client 
> unmarshalling side. That is why I was trying to capture the 
> response. From my recollection of the second problem (#11707) 
> it was also on the way back (TBD.)
> 
> My guess is that the response is messed up in some way and 
> when that happens (depending on which part of the large 
> response is being parsed) the axis unmarshalling code will 
> generate one of these two problems.
> 
> Is there a way I can get to the response SOAP message from my 
> client-side exception handler? If so, I could dump the 
> response xml to a file when these exceptions happen... Can I 
> call MessageContext.getCurrentContext() to get to this info?
> 
> Yes, axis is both client and server.
> 
> The defects have already been entered - see:
> 
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11706
> 
> and
> 
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11707
> 
> Thanks for looking into it.
> 
> alan
> 
> 
> -----Original Message-----
> From: butek@us.ibm.com [mailto:butek@us.ibm.com]
> Sent: Wednesday, August 14, 2002 3:23 PM
> To: axis-dev@xml.apache.org
> Subject: Re: 1.0 Bugzilla Scrub & two unfiled exceptions
> 
> 
> Hopefully you'll be able to get a tcpmon trace for that first 
> one sometime. AXIS is failing on the client side reading the 
> incoming message and it would be great if you could capture 
> that message. Is AXIS on both the client and server sides?
> 
> I'll second Rich's comment. Go ahead and open bugzillas for 
> these, even if you don't think you have all the info.
> 
> Russell Butek
> butek@us.ibm.com
> 
> 
> Please respond to axis-dev@xml.apache.org 
> To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
> cc: 
> Subject: 1.0 Bugzilla Scrub & two unfiled exceptions
> 
> 
> 
> >    1.0 BUGZILLA SCRUB
> >    ------------------
> 
> I know you all have plenty to do before shipping 1.0 but I 
> just wanted to
> let you know that I have repeatedly seen two exceptions being 
> thrown by
> Axis. I haven't had time to qualify/isolate a small test case 
> that shows the
> problem(s) so that I can file a bugzilla defect report.
> 
> When is the drop-dead date on filing bugzilla reports in 
> order for them to
> be considered for a 1.0 release?
> 
> FYI:
> 
> The exceptions I am seeing happen every once in a while. I 
> haven't been able
> to capture the server responses using tcpmon (it crashes) to determine
> whether the responses are well formed (ie. its a client-side 
> problem) or not
> (ie. its a server-side problem.)
> 
> PROBLEM #1:
> 
> - Exception:
> java.lang.ArrayStoreException 
> at org.apache.axis.utils.JavaUtils.convert(JavaUtils.java:365)
> at
> org.apache.axis.encoding.ser.BeanPropertyTarget.set(BeanProper
> tyTarget.java:
> 109)
> at
> org.apache.axis.encoding.DeserializerImpl.valueComplete(Deseri
> alizerImpl.jav
> a:260)
> at
> org.apache.axis.encoding.ser.ArrayDeserializer.valueComplete(A
> rrayDeserializ
> er.java:520)
> at
> org.apache.axis.encoding.DeserializerImpl.endElement(Deseriali
> zerImpl.java:5
> 03)
> at
> org.apache.axis.encoding.DeserializationContextImpl.endElement
> (Deserializati
> onContextImpl.java:908)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventReco
> rder.java:205)
> at
> org.apache.axis.message.MessageElement.publishToHandler(Messag
> eElement.java:
> 664)
> at
> org.apache.axis.encoding.DeserializerImpl.startElement(Deseria
> lizerImpl.java
> :371)
> at
> org.apache.axis.encoding.DeserializationContextImpl.startEleme
> nt(Deserializa
> tionContextImpl.java:874)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventReco
> rder.java:199)
> at
> org.apache.axis.message.MessageElement.publishToHandler(Messag
> eElement.java:
> 664)
> at
> org.apache.axis.encoding.DeserializerImpl.startElement(Deseria
> lizerImpl.java
> :371)
> at
> org.apache.axis.encoding.DeserializationContextImpl.startEleme
> nt(Deserializa
> tionContextImpl.java:874)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventReco
> rder.java:199)
> at
> org.apache.axis.message.MessageElement.publishToHandler(Messag
> eElement.java:
> 664)
> at
> org.apache.axis.encoding.DeserializerImpl.startElement(Deseria
> lizerImpl.java
> :371)
> at
> org.apache.axis.encoding.ser.BeanDeserializer.startElement(Bea
> nDeserializer.
> java:171)
> at
> org.apache.axis.encoding.DeserializationContextImpl.startEleme
> nt(Deserializa
> tionContextImpl.java:874)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventReco
> rder.java:199)
> at
> org.apache.axis.message.MessageElement.publishToHandler(Messag
> eElement.java:
> 664) 
> at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:250)
> at org.apache.axis.message.RPCElement.getParams(RPCElement.java:274)
> at org.apache.axis.client.Call.invoke(Call.java:1862)
> at org.apache.axis.client.Call.invoke(Call.java:1767)
> at org.apache.axis.client.Call.invoke(Call.java:1307)
> at ... the WSDL2Java generated stubs ...
> 
> PROBLEM #2:
> 
> -- not verbatim --
> 
> "Could not convert XXX to bean field YYY ..."
> 
> thrown by ... ser.BeanPropertyTarget.set( BeanPropertyTarget:130 ) ...
> 
> Axis version is a nightly build from 20020807. Server is running under
> tomcat 4.0.4 with JDK 1.4 on Linux. Client is stand-alone app 
> running on JDK
> 1.4 on Linux (same box.)
> 
> My service returns a fairly large bean with a lot of nested 
> bean properties
> and/or arrays of beans.
> 
> My client is a multi-threaded client with one thread per (WSDL2Java
> generated) stub instance. Each thread repeatedly calls the 
> same service
> method. The service blocks all clients until a state change 
> occurs at which
> time it unblocks the clients and they all tend to return from 
> the sevice
> method at the same time.
> 
> The problem seems to happen more often when I run with more client
> threads/stubs. They seem to occur after 100 - 200 calls to the service
> method but that is a very rough estimate and there doesn't 
> seem to be a
> pattern there.
> 
> That is all the info I have for now. I'll get back to you 
> with more details
> when I get a chance.
> 
> alan
> 

Mime
View raw message