[jira] Commented: (AXISCPP-946) client axis engine invoke throws exception

["Antoine Galataud (JIRA)" <ax...@ws.apache.org>]

    [ http://issues.apache.org/jira/browse/AXISCPP-946?page=comments#action_12368732 ] 

Antoine Galataud commented on AXISCPP-946:
------------------------------------------

More infos, as i sent to mailing list :
I tried with :
- 1.6a.n binary release for SunOS
- calculator example
- xerces 2.2.0

I'm stuck again with the "same" error : when i run the calculator sample, i get a SIGABRT; here is my debugger output :
Reading calculator
Reading ld.so.1
Reading libdl.so.1
Reading libaxis_client.so
Reading libCstd.so.1
Reading libCrun.so.1
Reading libm.so.1
Reading libw.so.1
Reading libc.so.1
Reading libsocket.so.1
Reading libnsl.so.1
Reading libmp.so.2
Reading libCstd_isa.so.1
Reading libc_psr.so.1
(dbx) run                                                                   
Running: calculator
(process id 21159)
Reading libaxis_xerces.so
Reading libxerces-c.so.22
Reading libpthread.so.1
Reading libthread.so.1
detected a multithreaded program
Reading libhttp_transport.so
Reading libhttp_channel.so
Reading nss_files.so.1
Reading nss_nis.so.1
Exception of type <unknown type> is unhandled
t@1 (l@1) stopped in __exdbg_notify_of_throw at 0xfefd3d94
0xfefd3d94: __exdbg_notify_of_throw       :     jmp     %o7 + 0x8

Unfortunatly, i don't have much time to see where exactly exception occurs, but i guess it's probably at the same point (or nearly)

My stub and skeleton compilation options :
Skeleton :
 CC -qoption ld -i -o libcalc.so -xO3 -xlibmil -xlibmopt -DNDEBUG -xildoff -DNDEBUG -DSYSV -DSVR4 -Dsolaris -DANSI_C -D_TEMPLATES_ENABLE_ -mt -D_POSIX_THREADS -D_REENTRANT -DEXCEPTION_EXPORTS -PIC -G -I../../include *.cpp

Stub :
CC *.cpp -I../include -L /axis/axis-c-1.6a.n-SunOS-trace-bin/lib/axis -ldl -laxis_client -o calculator

my axiscpp.conf :
WSDDFilePath:/axis/etc/server.wsdd
XMLParser:/axis/axis-c-1.6a.n-SunOS-trace-bin /lib/axis/libaxis_xerces.so
LogPath:/log/AxisLog
ClientLogPath:/axis/log/AxisClientLog
ClientWSDDFilePath:/axis/etc/client.wsdd
Transport_http:/axis/axis-c-1.6a.n-SunOS-trace-bin/lib/axis/libhttp_transport.so
Channel_HTTP:/axis/axis-c-1.6a.n-SunOS-trace-bin/lib/axis/libhttp_channel.so

my server.wsdd :
<?xml version="1.0" encoding="UTF-8"?>
<deployment xmlns=" http://xml.apache.org/axis/wsdd/" xmlns:C="http://xml.apache.org/axis/wsdd/providers/C" xmlns:CPP=" http://xml.apache.org/axis/wsdd/providers/CPP">
    <globalConfiguration>
    </globalConfiguration>
    <service name="Calculator" provider="CPP:RPC" description="Calculator Web Service">
        <parameter name="allowedMethods" value="add"/>
        <parameter name="className" value="/apache/webservices/libcalc.so"/>
    </service>
</deployment>

Once again, i have no way to verify that my webservice is up and correctly deployed by apache without testing with a client, so i can't figure out if it's a client bug or server bug.
With simple_axis_server, if i open its url in a browser, it does nothing. If i start the client, same bug, unless the browser requests it, then it waits

I also found another bug in 1.5 release : axiscpp.conf is not correctly parsed (it's not an encoding problem, i checked) : if i let comments (with #), the file is just not parsed.

One other question : for tests, do you use gcc on Solaris or do you use native CC (in buildInitialize.xml, it's set at CC) ?

Thank again for help, hope we could fix those bugs rapidly !

> client axis engine invoke throws exception
> ------------------------------------------
>
>          Key: AXISCPP-946
>          URL: http://issues.apache.org/jira/browse/AXISCPP-946
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Engine
>     Versions: 1.5 Final
>  Environment: Solaris 8
>     Reporter: Antoine Galataud

>
> I found a problem in 1.5 final release with ClientAxisEngine::invoke(MessageData* pMsg) in ClientAxisEngine.cpp
> I compiled axis c++ with apache 1.3 support and xerces 2.5.0. I can deploy the library modaxis_cpp, even if i can't verify that the web service is correctly deployed without calling it with a client. I so generated client stub and server skeleton, compiled, ant tried to run it.
> It results in SIGABRT, at this point : m_pSZ->markEndOfStream(); in the ClientAxisEngin.cpp, so when the client begin the call.
> markEndOfStream() seems to call virtual flushOutput(), but i can't see what is the problem there.
> I tried with xerces 2.2.0 as described, but it changed nothing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira