Hi alebu,
If it segfaults can you send us the gdb backtrace ? BTW, another RC of
1.3.1 will be available soon.
Thanks,
-Manjula.
On Wed, 2008-04-23 at 09:55 +0200, alebu wrote:
> Link to 1.3.1 you gave is broken for me.
> Now I got slightly different problem.
> After compiling using g++ for compiler and linker (probably i was
> using gcc/g++ earlier and thats was the problem)
> I simply have segmentaion fault before any of my custom code is
> executed. First row of generated with WSDL2C invoke
> method was logging function and it is not executed. So, as I
> understand, problem occurs somewhere before invoke call.
> Compiling the same code with the same parameters but using gcc works
> fine. I should mention that code in both cases is
> C code. All declarations are covered with
> #ifdef __cplusplus
> extern "C" {
> #endif
> //code
> #ifdef __cplusplus
> }
> #endif
> In axis2c logs last LIVE line is:
> engine.c(670) End:axis2_engine_invoke_phases
> engine.c(648) Start:axis2_engine_invoke_phases
> engine.c(670) End:axis2_engine_invoke_phases
> class_loader.c(140) Object loaded successfully
> ... and no any error messages
>
> Any ideas? I could try the same with axis2c 1.3.1 but I need a link to
> it (on website only 1.3.0 is available)
> Compiler options are (fragment from Eclipse/C log):
> Invoking: GCC C Compiler
> g++ -I/opt/axis2c-1.3.0/include/axis2-1.3.0 -O0 -g3 -Wall -c
> -fmessage-length=0 -fPIC -MMD -MP -MF"src/adb_field_type.d"
> -MT"src/adb_field_type.d" -o"src/adb_field_type.o"
>
> And linking log part is:
> Invoking: GCC C Linker
> g++ -L/opt/axis2c-1.3.0/lib -L/home/BEA/tuxedo9.1/lib -shared
> -o"libmyservice.so" ./src/adb_field_type.o ./src/adb_serve.o
> ./src/adb_serveResponse.o ./src/adb_serve_req_type.o
> ./src/adb_serve_resp_type.o ./src/axis2_skel_uniservice.o
> ./src/axis2_svc_skel_uniservice.o -ldl -lbuft -lfml -lfml32 -lengine -ltux
> -lpthread -laxutil -laxis2_axiom -laxis2_engine -laxis2_parser
> -laxis2_http_sender -laxis2_http_receiver -laxis2_libxml2
>
> Some additional libraries relative to BEA Tuxedo are included, but I
> don't think that they are the problem.
>
>
> On Mon, Apr 14, 2008 at 4:08 PM, Samisa Abeysinghe <[EMAIL PROTECTED]>
> wrote:
> What are the compiler options you used when compiling the
> service?
>
> We have added the dlerror to the log in 1.3.1. The RC is
> available, can you try with that?
>
> Samisa...
>
> alebu wrote:
>
> Hi list.
> I have such a situation:
> I have some web-service which was generated from WSDL
> using WSDL2C utility.
> Later I decided to write part of this web-service with
> C++. Before functions that uses
> C++ code I put:
> #ifdef __cplusplus
> extern "C"
> #endif
> Then I tried to compile using g++. During compilation
> some errors were found, but
> all of them was about incorrect conversion from void*
> into axis2 types.
> When I fixed them (I hope) but when I call this
> web-service I got axis error:
> ...
> <faultcode>soapenv:Server</faultcode>
> <faultstring>Failed in creating
> DLL</faultstring>
> ...
> In axis2.log only one message was interesting for me:
> raw_xml_in_out_msg_recv.c(115) Impl object for service
> 'myService' not set in message receiver. 100 :: Failed
> in creating DLL
>
> I understand that it probably was'nt very wise to
> compile .c files using g++ but, compilation was
> sucessful, so I wonder
> where possible problem can be.
> Is it possible at all to compile axis2/C web serice
> from C++ sources using C++ possibilities?
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG. Version: 7.5.519 / Virus Database:
> 269.22.13/1376 - Release Date: 4/13/2008 1:45 PM
>
>
>
> --
> Samisa Abeysinghe Director, Engineering; WSO2 Inc.
>
> http://www.wso2.com/ - "The Open Source SOA Company"
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
