axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <>
Subject Re: cvs commit: xml-axis/java/test/functional
Date Sun, 02 Sep 2001 13:25:20 GMT
OK, that code indeed notices the timeout for doTestIBM.  The transportsample
test was still hanging though, I assume because the thread waiting on the
URL data was still wedged.  While in there I noticed that the req file
wasn't getting deleted in this case because invoke() never came back in
FileReader, so I switched to getting the Message as bytes to read in the
whole file and then deleting it before calling invoke().  Also fixed the
FileSender to increment its index even if a timeout occurs.

The latter fix enabled the second FileReader to find the xml2.req file and
complete the XXX test successfully.

The synchronization in this sample still seems inadequate and potentially
trouble-causing.  It does work now, so I'll put the test back.  And yes, it
was in fact much easier to remove it.


----- Original Message -----
From: "Sam Ruby" <>
To: <>
Sent: Sunday, September 02, 2001 2:47 AM
Subject: Re: cvs commit: xml-axis/java/test/functional

> >3) It doesn't appear to me that anything in the functional tests catches
> the
> >timeout exception and says that it's OK (i.e. should not result in a
> failed
> >test).  Did I miss something?  I didn't add the test back in because of
> >this, but if you can enlighten me or fix it, please do.
> We are talking about doTestIBM, right?
> - Sam Ruby

View raw message