axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Perry2 <PERR...@uk.ibm.com>
Subject Re: Code freeze for Axis C++ 1.3 final release.
Date Thu, 07 Oct 2004 11:56:08 GMT




There are still issues with the new transport layer. The new transport
layer has been tested on Linux using the ant test suite with the following
tests:

CalculatorDoc - Client Execution - PASSED
ComplexTypeAll - Client Execution - PASSED
Enumeration - Client Execution - PASSED
ExceptionTestDoc - Client Execution - PASSED
FaultMappingDoc - Client Execution - PASSED
ManyTypeRefRoot - Client Execution - PASSED
MathOpsDoc - Client Execution - FAILED
RecurseTypes - Client Execution - PASSED
SimpleArrayDoc - Client Execution - PASSED
SimpleRefDoc - Client Execution - FAILED
SimpleTypeArray - Client Execution - PASSED
SimpleTypeInnerUnbounded - Client Execution - PASSED
SimpleTypeInnerUnboundedInOutput - Client Execution - PASSED

As can be seen a couplt of the tests fail. Debugging the code the stack
trace is below, and is the same for both failures.

The MathOpsDoc test threw a SIGSEGV:
--------------------------------------------------------
#0  0xb73661f7 in _int_free () from /lib/tls/libc.so.6
#1  0xb7364e68 in free () from /lib/tls/libc.so.6
#2  0xb74b9263 in operator delete () from /usr/lib/libstdc++.so.5
#3  0xb758757c in AxisTransportException::processException
(this=0xbfffb6c0, iExceptionCode=45,
    pcMessage=0xb6698c58 "Channel error while waiting for timeout")
    at /build/nw00_P/obj/src/transport/axis/AxisTransportException.cpp:260
#4  0xb7586152 in AxisTransportException (this=0xbfffb6c0,
iExceptionCode=45,
    pcMessage=0xb6698c58 "Channel error while waiting for timeout")
    at /build/nw00_P/obj/src/transport/axis/AxisTransportException.cpp:89
#5  0xb6693812 in Channel::operator>> (this=0x80553d8, msg=@0x805542c)
    at /build/nw00_P/src/ws-axis/c/src/transport/axis2/Channel.cpp:244
#6  0xb669675e in Axis2Transport::getBytes (this=0x80553c8,
pcBuffer=0x806f10c "",
    pSize=0xbfffb7e0) at
/build/nw00_P/src/ws-axis/c/src/transport/axis2/Axis2Transport.cpp:173
#7  0xb72c3ec6 in SoapBinInputStream::readBytes (this=0x8062000,
pcToFill=0x806f10c "",
    iMaxToRead=7536752) at
/build/nw00_P/src/ws-axis/c/src/xml/xerces/SoapBinInputStream.cpp:45
#8  0xb71b5148 in xml4c_5_3::XMLReader::refreshRawBuffer ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#9  0xb71b24ae in xml4c_5_3::XMLReader::XMLReader ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#10 0xb713d38c in xml4c_5_3::ReaderMgr::createReader ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#11 0xb7110fa9 in xml4c_5_3::IGXMLScanner::scanReset ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#12 0xb71b7b45 in xml4c_5_3::XMLScanner::scanFirst ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#13 0xb714a1b1 in xml4c_5_3::SAX2XMLReaderImpl::parseFirst ()
   from /home/axistest/production/obj/package/PreReqs/libxml4c.so.54
#14 0xb72c396f in XMLParserXerces::next (this=0x80577b8, isCharData=false)
    at /build/nw00_P/src/ws-axis/c/src/xml/xerces/XMLParserXerces.cpp:84
#15 0xb759260a in axiscpp::SoapDeSerializer::getEnvelope (this=0x80564b8)
    at /build/nw00_P/obj/src/soap/SoapDeSerializer.cpp:232
#16 0xb75940d6 in axiscpp::SoapDeSerializer::getVersion (this=0x80564b8)
    at /build/nw00_P/obj/src/soap/SoapDeSerializer.cpp:890
#17 0xb75291a3 in axiscpp::ClientAxisEngine::invoke (this=0x8055460,
pMsg=0x8055498)
---Type <return> to continue, or q <return> to quit---
    at /build/nw00_P/obj/src/engine/client/ClientAxisEngine.cpp:315
#18 0xb7528bff in axiscpp::ClientAxisEngine::process (this=0x8055460,
pSoap=0x80553c8)
    at /build/nw00_P/obj/src/engine/client/ClientAxisEngine.cpp:188
#19 0xb7560e24 in axiscpp::Call::invoke (this=0x80523d0)
    at /build/nw00_P/obj/src/engine/client/Call.cpp:269
#20 0x0804a016 in MathOps::div (this=0xbfffc200, Value0=10, Value1=5)
    at
/home/axistest/production/obj/test/generated/cpp/MathOpsDoc/MathOps.cpp:52
#21 0x0804afea in main (argc=2, argv=0xbfffc414)
    at
/home/axistest/production/obj/test/generated/cpp/MathOpsDoc/MathOpsDocClient.cpp:32
--------------------------------------------------------


The response captured in tcpmon is
--------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
         <divResponse xmlns="http://soapinterop.org">
            <divReturn xmlns="http://soapinterop.org/wsdl">2</divReturn>
         </divResponse>
      </soapenv:Body>
   </soapenv:Envelope>

--------------------------------------------------------

The SimpleRefDoc test failed in exactly the same way, again with a valid
response.

Both of these tests work when run with the old transport layer, so it looks
like there are still issues with the new transport layer.

I can't even get the tests to run on windows, but I am still investigating
the cause.

Regards

Andrew Perry
Clients for Web Service Stack
perryan@uk.ibm.com
Mail Point 127
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828  External + 44 (0)1962 819828
Fax. + 44(0)1962 818080


                                                                           
             John                                                          
             Hawkins/UK/IBM@IB                                             
             MGB                                                        To 
                                       "Apache AXIS C Developers List"     
             07/10/2004 08:48          <axis-c-dev@ws.apache.org>          
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           Re: Code freeze for Axis C++ 1.3    
             Developers List"          final release.                      
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           








I think the key question is test -

How long would it take to redo the tests on whatever platforms were tested
in the past wks ? My assumption is it would take that length of time again?
Which would be unnaceptable I think.

Our only way of testing the system is by running the fv suite on all
platforms. If we can do that then I'm happy to believe that the transport
is as good as the other one.

We have got a windows and linux build with aut tests running.

NOTE: we use xml4c as the parser not pure xerces.

Andrew P - have we tested the new transport on those platforms. if so, what
was the outcome?




John Hawkins





             Samisa Abeysinghe
             <samisa_abeysingh
             e@yahoo.com>                                               To
                                       Apache AXIS C Developers List
             07/10/2004 06:41          <axis-c-dev@ws.apache.org>
                                                                        cc

             Please respond to                                     Subject
              "Apache AXIS C           Re: Code freeze for Axis C++ 1.3
             Developers List"          final release.










The point is simple. Old transport has known critical bugs (such as message
size limits and
terribly slow). New transport has proven to solve the problems and fast as
well. Hence it is not a
question of different transports for 1.3 beta and 1.3 final. Rather a
question of fixing known
bugs in 1.3 beta in 1.3 final.

Is it a good idea to ship a buggy transport with 1.3 fianl, while we have
the solution in the CVS
already?

Samisa...

--- sanjaya singharage <sanjayas@opensource.lk> wrote:

> Is it wise to change the tranport in the middle of the release? To
> elaborate, the 1.3 Alpha and Beta will have one transport and the final
> release will have a different  new transport. Is this recommended or ok
> practise for apache projects?
>
> sanjaya.
>
> ----- Original Message -----
> From: "Samisa Abeysinghe" <samisa_abeysinghe@yahoo.com>
> To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> Sent: Wednesday, October 06, 2004 4:56 PM
> Subject: Re: Code freeze for Axis C++ 1.3 final release.
>
>
> > Are we making axis2 transport and Xerces based paser lib as defaults
for
> 1.3 final release?
> > If yes, we have to change the docs accordingly.
> > If no, why not ;-)
> >
> > Thanks,
> > Samisa...
> >
> > --- damitha kumarage <damitha@opensource.lk> wrote:
> >
> > > Hi all,
> > >
> > > How about freezing the Axis C++ code base in preparation for  1.3
final
> > > Release on 07th October 2004 and making a final release on 08th
October
> > > 2004.
> > > During this period developers are expected to adhere to the
following.
> > >
> > > * There will be no new addition to the existing code in the CVS.
> > >    That means no new feature added or existing feature removed.
> > >
> > > * Folders/Files/Classes/Variables/Methods  will not be added or
removed
> > >    unless it is required by bug fixes.
> > >
> > > * Only bug fixes are allowed which are recorded in Jira. But prior to
> > > the fix the developer needs to send a notice to the C dev mailing
list
> > > explaining his move. Before fixing the bug tagging the cvs with a
> > > meaningful name is recommended
> > >
> > >
> > > regds
> > > damitha
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > _______________________________
> > Do you Yahoo!?
> > Declare Yourself - Register online to vote today!
> > http://vote.yahoo.com
> >
> >
>
>
>




__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail





Mime
View raw message