You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Michael Kipper <mk...@rogers.com> on 2005/10/07 04:12:24 UTC

Need Help Installing axis-c for Linux

Hi,

I am installing Apache axis-c for a school project. I'm having some major
issues getting it running.
I'm using LinuxFromScratch, kernel 2.6.12, on an amd64.
I've built apache httpd, xerces-c and axis-c from cvs-source, all in /opt.
Everything builds fine, up until I start apache, and get the following in
/var/log/apache/error_log:

Thu Oct 06 19:36:55 2005] [notice] Digest: generating secret for digest
authentication ...
[Thu Oct 06 19:36:55 2005] [notice] Digest: done
[Thu Oct 06 19:36:56 2005] [notice] Apache/2.0.54 (Unix) DAV/2 configured
-- resuming normal operations
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
[Thu Oct 06 19:36:57 2005] [notice] child pid 18946 exit signal Aborted (6)
[Thu Oct 06 19:36:57 2005] [notice] child pid 18947 exit signal Aborted (6)
[Thu Oct 06 19:36:57 2005] [notice] child pid 18948 exit signal Aborted (6)
[Thu Oct 06 19:36:57 2005] [notice] child pid 18949 exit signal Aborted (6)
[Thu Oct 06 19:36:57 2005] [notice] child pid 18950 exit signal Aborted (6)
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
<snip>

And so on, forever.
Some info:

[root@lfs ~]# uname -a
Linux lfs 2.6.12 #1 Thu Sep 15 00:55:24 EDT 2005 x86_64 x86_64 x86_64
GNU/Linux
[root@lfs ~]# file /opt/apache/modules/libaxiscpp_mod2.so
/opt/apache/modules/libaxiscpp_mod2.so: ELF 64-bit LSB shared object, AMD
x86-64, version 1 (SYSV), not stripped
[root@lfs ~]# file /opt/apache/modules/libaxis_xmlparser.so
/opt/apache/modules/libaxis_xmlparser.so: ELF 64-bit LSB shared object, AMD
x86-64, version 1 (SYSV), not stripped

Please help!

Thanks,
Michael


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Hi

I don't have problems with calling Axis::terminate(). But I call it after all Axis instances are already destroyed.


  ----- Original Message ----- 
  From: Pico Florin 
  To: Apache AXIS C User List 
  Sent: Tuesday, October 11, 2005 3:35 PM
  Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


  Hi!

    Thank you Thomas. I seems to be more stable now. Regarding the code

     Axis::terminate() I've used in my application(a task that from time to time sends SOAP messages to SAP BC server) when destructor of the client is called and an "Assertion failure exception"  is thrown in my engine task. If I don't put this code then everything is allright...Therefore, it is necessaru to use it? Is safety?

     Regards,

          Florin



------------------------------------------------------------------------------
  Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail 

Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Pico Florin <pi...@yahoo.co.uk>.
Hi!

  Thank you Thomas. I seems to be more stable now. Regarding the code

   Axis::terminate() I've used in my application(a task that from time to time sends SOAP messages to SAP BC server) when destructor of the client is called and an "Assertion failure exception"  is thrown in my engine task. If I don't put this code then everything is allright...Therefore, it is necessaru to use it? Is safety?

   Regards,

        Florin

		
---------------------------------
Yahoo! Messenger  NEW - crystal clear PC to PC calling worldwide with voicemail 

Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Hi

You need to include Axis.hpp in the main file.

If I'm not wrong than you should call Axis::initialize(false); before you use axis objects. In my example I call this in my main loop before I created threads in which I created pBLP = new Soap(s.strURL.c_str(), APTHTTP1_1);

When all threads are finished than you call Axis::terminate() (I think).




  ----- Original Message ----- 
  From: Pico Florin 
  To: Apache AXIS C User List 
  Sent: Tuesday, October 11, 2005 2:16 PM
  Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


  Hi!

    Thank you for your responses. I want to understand the code



  Axis::initialize(false);


  What is the exactly snippet code? What should I include?



  Thank you,

       Florin


   



------------------------------------------------------------------------------
  To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Pico Florin <pi...@yahoo.co.uk>.
Hi!

  Thank you for your responses. I want to understand the code

 

Axis::initialize(false);


What is the exactly snippet code? What should I include?

 

Thank you,

     Florin


 

		
---------------------------------
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Hi Samisa

Thank you for your notification. I didn't have that. I already tested that 
and it seems to be much more stable now. I still have some problems with 
stability under very difficult conditions (about 100 threads generated in 10 
seconds). I'll try to find the position in code where this happens.

Thank you

Tomaz



----- Original Message ----- 
From: "Samisa Abeysinghe" <sa...@gmail.com>
To: "Apache AXIS C User List" <ax...@ws.apache.org>
Sent: Monday, October 10, 2005 3:51 PM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


> Tomaz Rotovnik wrote:
>
>>
>> Samisa thank you for response.
>>
>> I have right location of channel library dfined in "axiscpp.conf". When I 
>> run the program and calling one function every 300ms, it crashes 
>> (randomly) after some calls were done succesfully, but with the same 
>> error. Function is also synchronized (using mutex) so it can only be 
>> processed only one at the time.
>>
>> So I think the problem is in loading library very often, but I don't how 
>> to solve the problem.
>
> Well I happen to remember that there is one more thing that you should 
> take note of when using threading.
> In the main program, before you start threads, you got to initialize the 
> Axis platform:
>    Axis::initialize(false);
> false here means that it is not server.
>
> Have you done this already in your threaded client?
>
> Thanks,
> Samisa...
>
>>
>> Best regards
>>
>> Tomaz
>>
>>
>> ----- Original Message ----- From: "Samisa Abeysinghe" 
>> <sa...@gmail.com>
>> To: "Apache AXIS C User List" <ax...@ws.apache.org>
>> Sent: Saturday, October 08, 2005 12:25 AM
>> Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>>
>>
>>> Tomaz Rotovnik wrote:
>>>
>>>> Hi
>>>>  I've the same problem. Couple of days ago I send question about safe 
>>>> threading on client side. When I start debugging I found out that call 
>>>> m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.
>>>>  Then I enable possibility (uncomment) to print out possible exceptions 
>>>> in function Call:initialize().
>>>> Exception that I get was: DLOPEN FAILED in loading channel library.
>>>
>>>
>>> This basically means that the client cannot locate the channel library 
>>> specified in axiscpp.conf.
>>> Have a look at the axiscpp.conf to see what you have set as the location 
>>> of the channel library. Then ensure that it is there.
>>> You got to do the same for the parser library.
>>>
>>> Thanks,
>>> Samisa...
>>>
>>>>  I'm not sure yet if this exception was thrown by 
>>>> axis3\ChannelFactory.cpp file.
>>>>  Functions that are called are:
>>>> openConnection calls
>>>> setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
>>>>     HTTPTransport::setTransportProperty calls
>>>>        LoadChannelLibrary
>>>>  I repeat experiment (multiple calls on separately created Call 
>>>> objects) couple of times with same error report.
>>>>  Now I'm looking for solution.
>>>>  Could you check if the problem is same with your code?
>>>>
>>>>     ----- Original Message -----
>>>>     *From:* Pico Florin <ma...@yahoo.co.uk>
>>>>     *To:* Apache AXIS C User List <ma...@ws.apache.org>
>>>>     *Sent:* Friday, October 07, 2005 3:53 PM
>>>>     *Subject:* Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>>>>
>>>>     Hi!
>>>>
>>>>       I've tested my example in different ways of implementation. Some
>>>>     of them fail on this snippet
>>>>
>>>>
>>>>
>>>>     if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
>>>>        return NULL;
>>>>      }
>>>>
>>>>
>>>>     leading to :
>>>>
>>>>
>>>>     "Unknown exception has occured". What are the reasons for this
>>>>     failures? Just to know better how to avoid this situation.
>>>>
>>>>          Thank you,
>>>>
>>>>               Florin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>     ------------------------------------------------------------------------
>>>>
>>>>     How much free photo storage do you get? Store your holiday snaps
>>>>     for FREE with Yahoo! Photos. *Get Yahoo! Photos*
>>>>
>>>> <http://us.rd.yahoo.com/mail/uk/taglines/default/photos/*http://uk.photos.yahoo.com/>
>>>>
>>>
>>>
>>
>>
> 


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Tomaz Rotovnik wrote:

>
> Samisa thank you for response.
>
> I have right location of channel library dfined in "axiscpp.conf". 
> When I run the program and calling one function every 300ms, it 
> crashes (randomly) after some calls were done succesfully, but with 
> the same error. Function is also synchronized (using mutex) so it can 
> only be processed only one at the time.
>
> So I think the problem is in loading library very often, but I don't 
> how to solve the problem.

Well I happen to remember that there is one more thing that you should 
take note of when using threading.
In the main program, before you start threads, you got to initialize the 
Axis platform:
    Axis::initialize(false);
false here means that it is not server.

Have you done this already in your threaded client?

Thanks,
Samisa...

>
> Best regards
>
> Tomaz
>
>
> ----- Original Message ----- From: "Samisa Abeysinghe" 
> <sa...@gmail.com>
> To: "Apache AXIS C User List" <ax...@ws.apache.org>
> Sent: Saturday, October 08, 2005 12:25 AM
> Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>
>
>> Tomaz Rotovnik wrote:
>>
>>> Hi
>>>  I've the same problem. Couple of days ago I send question about 
>>> safe threading on client side. When I start debugging I found out 
>>> that call m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.
>>>  Then I enable possibility (uncomment) to print out possible 
>>> exceptions in function Call:initialize().
>>> Exception that I get was: DLOPEN FAILED in loading channel library.
>>
>>
>> This basically means that the client cannot locate the channel 
>> library specified in axiscpp.conf.
>> Have a look at the axiscpp.conf to see what you have set as the 
>> location of the channel library. Then ensure that it is there.
>> You got to do the same for the parser library.
>>
>> Thanks,
>> Samisa...
>>
>>>  I'm not sure yet if this exception was thrown by 
>>> axis3\ChannelFactory.cpp file.
>>>  Functions that are called are:
>>> openConnection calls
>>> setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
>>>     HTTPTransport::setTransportProperty calls
>>>        LoadChannelLibrary
>>>  I repeat experiment (multiple calls on separately created Call 
>>> objects) couple of times with same error report.
>>>  Now I'm looking for solution.
>>>  Could you check if the problem is same with your code?
>>>
>>>     ----- Original Message -----
>>>     *From:* Pico Florin <ma...@yahoo.co.uk>
>>>     *To:* Apache AXIS C User List <ma...@ws.apache.org>
>>>     *Sent:* Friday, October 07, 2005 3:53 PM
>>>     *Subject:* Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>>>
>>>     Hi!
>>>
>>>       I've tested my example in different ways of implementation. Some
>>>     of them fail on this snippet
>>>
>>>
>>>
>>>     if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
>>>        return NULL;
>>>      }
>>>
>>>
>>>     leading to :
>>>
>>>
>>>     "Unknown exception has occured". What are the reasons for this
>>>     failures? Just to know better how to avoid this situation.
>>>
>>>          Thank you,
>>>
>>>               Florin
>>>
>>>
>>>
>>>
>>>
>>>
>>>     
>>> ------------------------------------------------------------------------ 
>>>
>>>     How much free photo storage do you get? Store your holiday snaps
>>>     for FREE with Yahoo! Photos. *Get Yahoo! Photos*
>>>
>>> <http://us.rd.yahoo.com/mail/uk/taglines/default/photos/*http://uk.photos.yahoo.com/> 
>>>
>>>
>>
>>
>
>


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by John Hawkins <HA...@uk.ibm.com>.
Hmm, I thought we'd got rid of this - there is certainly a JIRA that was 
trying to address all these sorts of 
issues.http://issues.apache.org/jira/browse/AXISCPP-657
Hmm, looks like it never had any specific issues addressed in it ! Maybe 
you can use this JIRA to fix it ?

cheers,
John.





"Tomaz Rotovnik" <to...@uni-mb.si> 
11/10/2005 22:38
Please respond to
"Apache AXIS C User List"


To
"Apache AXIS C User List" <ax...@ws.apache.org>
cc

Subject
Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?






Hi

When I use multithreading on client side I found out that for each 
transaction HTTPChannel.dll library is loaded. Is this necessary? Why only 

this dll and not also AxisXMLParser and HTTPTransport?

Best Regards

Tomaz



Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Hi

When I use multithreading on client side I found out that for each 
transaction HTTPChannel.dll library is loaded. Is this necessary? Why only 
this dll and not also AxisXMLParser and HTTPTransport?

Best Regards

Tomaz


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Tomaz Rotovnik wrote:

>
> Samisa thank you for response.
>
> I have right location of channel library dfined in "axiscpp.conf". 
> When I run the program and calling one function every 300ms, it 
> crashes (randomly) after some calls were done succesfully, but with 
> the same error. Function is also synchronized (using mutex) so it can 
> only be processed only one at the time.

OK I get it now. So there is a threading issue in loading the parser lib.
Please create a Jira issue 
(http://issues.apache.org/jira/browse/AXISCPP) and attach your WSDL and 
the client code so that the developers could have a look into this.

Thanks,
Samisa...

>
> So I think the problem is in loading library very often, but I don't 
> how to solve the problem.
>
> Best regards
>
> Tomaz
>
>
> ----- Original Message ----- From: "Samisa Abeysinghe" 
> <sa...@gmail.com>
> To: "Apache AXIS C User List" <ax...@ws.apache.org>
> Sent: Saturday, October 08, 2005 12:25 AM
> Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>
>
>> Tomaz Rotovnik wrote:
>>
>>> Hi
>>>  I've the same problem. Couple of days ago I send question about 
>>> safe threading on client side. When I start debugging I found out 
>>> that call m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.
>>>  Then I enable possibility (uncomment) to print out possible 
>>> exceptions in function Call:initialize().
>>> Exception that I get was: DLOPEN FAILED in loading channel library.
>>
>>
>> This basically means that the client cannot locate the channel 
>> library specified in axiscpp.conf.
>> Have a look at the axiscpp.conf to see what you have set as the 
>> location of the channel library. Then ensure that it is there.
>> You got to do the same for the parser library.
>>
>> Thanks,
>> Samisa...
>>
>>>  I'm not sure yet if this exception was thrown by 
>>> axis3\ChannelFactory.cpp file.
>>>  Functions that are called are:
>>> openConnection calls
>>> setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
>>>     HTTPTransport::setTransportProperty calls
>>>        LoadChannelLibrary
>>>  I repeat experiment (multiple calls on separately created Call 
>>> objects) couple of times with same error report.
>>>  Now I'm looking for solution.
>>>  Could you check if the problem is same with your code?
>>>
>>>     ----- Original Message -----
>>>     *From:* Pico Florin <ma...@yahoo.co.uk>
>>>     *To:* Apache AXIS C User List <ma...@ws.apache.org>
>>>     *Sent:* Friday, October 07, 2005 3:53 PM
>>>     *Subject:* Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>>>
>>>     Hi!
>>>
>>>       I've tested my example in different ways of implementation. Some
>>>     of them fail on this snippet
>>>
>>>
>>>
>>>     if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
>>>        return NULL;
>>>      }
>>>
>>>
>>>     leading to :
>>>
>>>
>>>     "Unknown exception has occured". What are the reasons for this
>>>     failures? Just to know better how to avoid this situation.
>>>
>>>          Thank you,
>>>
>>>               Florin
>>>
>>>
>>>
>>>
>>>
>>>
>>>     
>>> ------------------------------------------------------------------------ 
>>>
>>>     How much free photo storage do you get? Store your holiday snaps
>>>     for FREE with Yahoo! Photos. *Get Yahoo! Photos*
>>>
>>> <http://us.rd.yahoo.com/mail/uk/taglines/default/photos/*http://uk.photos.yahoo.com/> 
>>>
>>>
>>
>>
>
>


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Samisa thank you for response.

I have right location of channel library dfined in "axiscpp.conf". When I 
run the program and calling one function every 300ms, it crashes (randomly) 
after some calls were done succesfully, but with the same error. Function is 
also synchronized (using mutex) so it can only be processed only one at the 
time.

So I think the problem is in loading library very often, but I don't how to 
solve the problem.

Best regards

Tomaz


----- Original Message ----- 
From: "Samisa Abeysinghe" <sa...@gmail.com>
To: "Apache AXIS C User List" <ax...@ws.apache.org>
Sent: Saturday, October 08, 2005 12:25 AM
Subject: Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


> Tomaz Rotovnik wrote:
>
>> Hi
>>  I've the same problem. Couple of days ago I send question about safe 
>> threading on client side. When I start debugging I found out that call 
>> m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.
>>  Then I enable possibility (uncomment) to print out possible exceptions 
>> in function Call:initialize().
>> Exception that I get was: DLOPEN FAILED in loading channel library.
>
> This basically means that the client cannot locate the channel library 
> specified in axiscpp.conf.
> Have a look at the axiscpp.conf to see what you have set as the location 
> of the channel library. Then ensure that it is there.
> You got to do the same for the parser library.
>
> Thanks,
> Samisa...
>
>>  I'm not sure yet if this exception was thrown by 
>> axis3\ChannelFactory.cpp file.
>>  Functions that are called are:
>> openConnection calls
>> setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
>>     HTTPTransport::setTransportProperty calls
>>        LoadChannelLibrary
>>  I repeat experiment (multiple calls on separately created Call objects) 
>> couple of times with same error report.
>>  Now I'm looking for solution.
>>  Could you check if the problem is same with your code?
>>
>>     ----- Original Message -----
>>     *From:* Pico Florin <ma...@yahoo.co.uk>
>>     *To:* Apache AXIS C User List <ma...@ws.apache.org>
>>     *Sent:* Friday, October 07, 2005 3:53 PM
>>     *Subject:* Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>>
>>     Hi!
>>
>>       I've tested my example in different ways of implementation. Some
>>     of them fail on this snippet
>>
>>
>>
>>     if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
>>        return NULL;
>>      }
>>
>>
>>     leading to :
>>
>>
>>     "Unknown exception has occured". What are the reasons for this
>>     failures? Just to know better how to avoid this situation.
>>
>>          Thank you,
>>
>>               Florin
>>
>>
>>
>>
>>
>>
>>     ------------------------------------------------------------------------
>>     How much free photo storage do you get? Store your holiday snaps
>>     for FREE with Yahoo! Photos. *Get Yahoo! Photos*
>> 
>> <http://us.rd.yahoo.com/mail/uk/taglines/default/photos/*http://uk.photos.yahoo.com/>
>>
>
> 


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Tomaz Rotovnik wrote:

> Hi
>  
> I've the same problem. Couple of days ago I send question about safe 
> threading on client side. When I start debugging I found out that call 
> m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.
>  
> Then I enable possibility (uncomment) to print out possible exceptions 
> in function Call:initialize().
> Exception that I get was: DLOPEN FAILED in loading channel library.

This basically means that the client cannot locate the channel library 
specified in axiscpp.conf.
Have a look at the axiscpp.conf to see what you have set as the location 
of the channel library. Then ensure that it is there.
You got to do the same for the parser library.

Thanks,
Samisa...

>  
> I'm not sure yet if this exception was thrown by 
> axis3\ChannelFactory.cpp file.
>  
> Functions that are called are:
> openConnection calls
> setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
>     HTTPTransport::setTransportProperty calls
>        LoadChannelLibrary
>  
> I repeat experiment (multiple calls on separately created Call 
> objects) couple of times with same error report.
>  
> Now I'm looking for solution.
>  
> Could you check if the problem is same with your code?
>  
>
>     ----- Original Message -----
>     *From:* Pico Florin <ma...@yahoo.co.uk>
>     *To:* Apache AXIS C User List <ma...@ws.apache.org>
>     *Sent:* Friday, October 07, 2005 3:53 PM
>     *Subject:* Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?
>
>     Hi!
>
>       I've tested my example in different ways of implementation. Some
>     of them fail on this snippet
>
>      
>
>      
>
>     if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
>        return NULL;
>      }
>
>      
>
>     leading to :
>
>      
>
>     "Unknown exception has occured". What are the reasons for this
>     failures? Just to know better how to avoid this situation.
>
>          Thank you,
>
>               Florin
>
>      
>
>      
>
>      
>
>      
>
>      
>
>     ------------------------------------------------------------------------
>     How much free photo storage do you get? Store your holiday snaps
>     for FREE with Yahoo! Photos. *Get Yahoo! Photos*
>     <http://us.rd.yahoo.com/mail/uk/taglines/default/photos/*http://uk.photos.yahoo.com/>
>


Re: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Tomaz Rotovnik <to...@uni-mb.si>.
Hi 

I've the same problem. Couple of days ago I send question about safe threading on client side. When I start debugging I found out that call m_pCall->initialize(CPP_DOC_PROVIDER)) causes exception.

Then I enable possibility (uncomment) to print out possible exceptions in function Call:initialize().
Exception that I get was: DLOPEN FAILED in loading channel library.

I'm not sure yet if this exception was thrown by axis3\ChannelFactory.cpp file.

Functions that are called are:
openConnection calls
setTransportProperty(CHANNEL_HTTP_DLL_NAME,...
    HTTPTransport::setTransportProperty calls
       LoadChannelLibrary

I repeat experiment (multiple calls on separately created Call objects) couple of times with same error report.

Now I'm looking for solution. 

Could you check if the problem is same with your code?

  ----- Original Message ----- 
  From: Pico Florin 
  To: Apache AXIS C User List 
  Sent: Friday, October 07, 2005 3:53 PM
  Subject: Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?


  Hi!

    I've tested my example in different ways of implementation. Some of them fail on this snippet





  if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
     return NULL;
   }



  leading to :



  "Unknown exception has occured". What are the reasons for this failures? Just to know better how to avoid this situation.

       Thank you,

            Florin













------------------------------------------------------------------------------
  How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! Photos

Why "m_pCall->initialize(CPP_RPC_PROVIDER))" fails?

Posted by Pico Florin <pi...@yahoo.co.uk>.
Hi!

  I've tested my example in different ways of implementation. Some of them fail on this snippet

 

 

if (AXIS_SUCCESS != m_pCall->initialize(CPP_RPC_PROVIDER)) {
   return NULL;
 }

 

leading to :

 

"Unknown exception has occured". What are the reasons for this failures? Just to know better how to avoid this situation.

     Thank you,

          Florin

 

 

 

 

 

		
---------------------------------
How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! Photos

Re: Need Help Installing axis-c for Linux

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Michael Kipper wrote:

>--- Samisa Abeysinghe <sa...@gmail.com> wrote:
>
>  
>
>>Well I am not a gdb guru, hence not that sure with attaching, may be you 
>>could watch variables as well as back trace.
>>
>>    
>>
>
>I rebuilt axis-c with trace and debug.
>
>  
>
>>However what I do is:
>>
>>[root@lfs ~/blfs]# gdb httpd
>> and then on gdb promt run:
>>(gdb) r -X
>>
>>then run a cliet, and if the server crashes gdb will drop back to gdb
>>prompt. Then run:
>>(gdb) bt
>>
>>    
>>
>
>Here goes:
>[root@lfs ~]# set +h
>[root@lfs ~]# PATH=/opt/apache/sbin:/usr/bin:/bin gdb httpd
>GNU gdb 6.3
>Copyright 2004 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you
>are
>welcome to change it and/or distribute copies of it under certain
>conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "x86_64-pc-linux-gnu"...(no debugging symbols
>found)
>Using host libthread_db library "/lib64/libthread_db.so.1".
>
>(gdb) r -X
>Starting program: /opt/apache/sbin/httpd -X
>(no debugging symbols found)
>(no debugging symbols found)
><snip>
>(no debugging symbols found)
>(no debugging symbols found)
>[Thread debugging using libthread_db enabled]
>[New Thread 46912516256144 (LWP 4728)]
>(no debugging symbols found)
>(no debugging symbols found)
><snip>
>(no debugging symbols found)
>(no debugging symbols found)
>Program received signal SIGSEGV, Segmentation fault.
>[Switching to Thread 46912516256144 (LWP 4728)]
>0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
>194         static inline bool isTraceOn() { return
>(*g_traceEntrypoints->m_traceOn)(); }
>Current language:  auto; currently c++
>(gdb) bt
>#0  0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
>#1  0x00002aaaae78e0f8 in XMLParserXerces (this=0x63fc10)
>    at /obj/src/xml/xerces/XMLParserXerces.cpp:40
>#2  0x00002aaaae78fc9b in CreateInstance (inst=0x7fffffb8edc0)
>    at /obj/src/xml/xerces/ParserLoader.cpp:36
>#3  0x00002aaaae208529 in axiscpp::XMLParserFactory::getParserObject ()
>   from /opt/apache/modules/libaxis_server.so
>#4  0x00002aaaae21785b in axiscpp::WSDDDocument::parseDocument ()
>   from /opt/apache/modules/libaxis_server.so
>#5  0x00002aaaae21794d in axiscpp::WSDDDocument::getDeployment ()
>   from /opt/apache/modules/libaxis_server.so
>#6  0x00002aaaae1f16fd in axiscpp::WSDDDeployment::loadWSDD ()
>   from /opt/apache/modules/libaxis_server.so
>#7  0x00002aaaae20b7d8 in initialize_module ()
>   from /opt/apache/modules/libaxis_server.so
>#8  0x00000000004277ea in ap_run_child_init ()
>#9  0x0000000000425a5d in ap_graceful_stop_signalled ()
>#10 0x0000000000425fb4 in ap_graceful_stop_signalled ()
>#11 0x0000000000426743 in ap_mpm_run ()
>#12 0x000000000042d210 in main ()
>(gdb)
>
>  
>
>>One more thing; are the Xerces libs on a location that could be located
>>by Apache?
>>    
>>
>
>[root@lfs ~]# /sbin/ldconfig -v | grep xerces
>/opt/xerces-c/lib:
>        libxerces-depdom.so.26 -> libxerces-depdom.so.26.0
>        libxerces-c.so.26 -> libxerces-c.so.26.0
>
>  
>
OK, it seems that the problem is with the parser.
However it is strange that it says that it is failing in trace:  
AxisTrace.h:194
I am not sure whay this is. May be you could disable trace and try gdb.
We have had few problems with Xerces 2.6 in the past. I am not sure if 
this is one of those. The alternative is to try with Xerces 2.2.

Thanks,
Samisa...

>Thanks again,
>Michael
>
>
>  
>


Re: Need Help Installing axis-c for Linux

Posted by Michael Kipper <mk...@rogers.com>.
--- Samisa Abeysinghe <sa...@gmail.com> wrote:

> Well I am not a gdb guru, hence not that sure with attaching, may be you 
> could watch variables as well as back trace.
> 

I rebuilt axis-c with trace and debug.

> However what I do is:
> 
> [root@lfs ~/blfs]# gdb httpd
>  and then on gdb promt run:
> (gdb) r -X
> 
> then run a cliet, and if the server crashes gdb will drop back to gdb
> prompt. Then run:
> (gdb) bt
> 

Here goes:
[root@lfs ~]# set +h
[root@lfs ~]# PATH=/opt/apache/sbin:/usr/bin:/bin gdb httpd
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...(no debugging symbols
found)
Using host libthread_db library "/lib64/libthread_db.so.1".

(gdb) r -X
Starting program: /opt/apache/sbin/httpd -X
(no debugging symbols found)
(no debugging symbols found)
<snip>
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912516256144 (LWP 4728)]
(no debugging symbols found)
(no debugging symbols found)
<snip>
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912516256144 (LWP 4728)]
0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
194         static inline bool isTraceOn() { return
(*g_traceEntrypoints->m_traceOn)(); }
Current language:  auto; currently c++
(gdb) bt
#0  0x00002aaaae789ad6 in XercesHandler (this=0x63fc30) at AxisTrace.h:194
#1  0x00002aaaae78e0f8 in XMLParserXerces (this=0x63fc10)
    at /obj/src/xml/xerces/XMLParserXerces.cpp:40
#2  0x00002aaaae78fc9b in CreateInstance (inst=0x7fffffb8edc0)
    at /obj/src/xml/xerces/ParserLoader.cpp:36
#3  0x00002aaaae208529 in axiscpp::XMLParserFactory::getParserObject ()
   from /opt/apache/modules/libaxis_server.so
#4  0x00002aaaae21785b in axiscpp::WSDDDocument::parseDocument ()
   from /opt/apache/modules/libaxis_server.so
#5  0x00002aaaae21794d in axiscpp::WSDDDocument::getDeployment ()
   from /opt/apache/modules/libaxis_server.so
#6  0x00002aaaae1f16fd in axiscpp::WSDDDeployment::loadWSDD ()
   from /opt/apache/modules/libaxis_server.so
#7  0x00002aaaae20b7d8 in initialize_module ()
   from /opt/apache/modules/libaxis_server.so
#8  0x00000000004277ea in ap_run_child_init ()
#9  0x0000000000425a5d in ap_graceful_stop_signalled ()
#10 0x0000000000425fb4 in ap_graceful_stop_signalled ()
#11 0x0000000000426743 in ap_mpm_run ()
#12 0x000000000042d210 in main ()
(gdb)

> One more thing; are the Xerces libs on a location that could be located
> by Apache?

[root@lfs ~]# /sbin/ldconfig -v | grep xerces
/opt/xerces-c/lib:
        libxerces-depdom.so.26 -> libxerces-depdom.so.26.0
        libxerces-c.so.26 -> libxerces-c.so.26.0


Thanks again,
Michael


Re: Need Help Installing axis-c for Linux

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Michael Kipper wrote:

>--- Samisa Abeysinghe <sa...@gmail.com> wrote:
>
>  
>
>>Does this happen when you run apache alone without Axis C++? (I mean 
>>without the axis entry in httpd.conf?)
>>    
>>
>
>Without the LoadModule entry in httpd.conf, httpd runs with no errors in
>the log. Previously, it wouldn't even serve up http://localhost/, but now
>it does, but the browser sits there trying to access http://localhost/axis/
> 
>  
>
>>Looking at the error it looks to me that this is something to do with 
>>C++ libs, hence this cannot be a apache problem, but a problem with 
>>modules in apache.
>>    
>>
>
>Is it a problem with the way I compiled axis-c?
>I've tried 1.5.0 and CVS, and get the same error.
>I've also rebuilt xerces-c and apache, with no results.
>
>  
>
>>May be you could debug httpd with gdb and run it with -X argument inside 
>>gdb, this will help you to trace the location of the error.
>>    
>>
>
>I've never done this before.
>I've done this:
>
>[root@lfs ~/blfs]# gdb
>GNU gdb 6.3
>Copyright 2004 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you
>are
>welcome to change it and/or distribute copies of it under certain
>conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "x86_64-pc-linux-gnu".
>(gdb) attach 17605
>Attaching to process 17605
><snip>
>Reading symbols from /opt/apache/modules/libaxiscpp_mod2.so...done.
>Loaded symbols for /opt/apache/modules/libaxiscpp_mod2.so
>Reading symbols from /opt/apache/modules/libaxis_server.so...done.
>Loaded symbols for /opt/apache/modules/libaxis_server.so
>Reading symbols from /usr/lib64/libstdc++.so.6...done.
>Loaded symbols for /usr/lib64/libstdc++.so.6
>Reading symbols from /usr/lib64/libgcc_s.so.1...done.
>Loaded symbols for /usr/lib64/libgcc_s.so.1
>0x00002aaaabc69f65 in __select_nocancel () from /lib64/libc.so.6
>
>And now what?
>  
>
Well I am not a gdb guru, hence not that sure with attaching, may be you 
could watch variables as well as back trace.

However what I do is:

[root@lfs ~/blfs]# gdb httpd
 and then on gdb promt run:
(gdb) r -X

then run a cliet, and if the server crashes gdb will drop back to gdb prompt. Then run:
(gdb) bt

One more thing; are the Xerces libs on a location that could be located by Apache?

Samisa...


>Thanks,
>Michael
>
>
>  
>


Re: Need Help Installing axis-c for Linux

Posted by Michael Kipper <mk...@rogers.com>.
--- Samisa Abeysinghe <sa...@gmail.com> wrote:

> Does this happen when you run apache alone without Axis C++? (I mean 
> without the axis entry in httpd.conf?)

Without the LoadModule entry in httpd.conf, httpd runs with no errors in
the log. Previously, it wouldn't even serve up http://localhost/, but now
it does, but the browser sits there trying to access http://localhost/axis/
 
> Looking at the error it looks to me that this is something to do with 
> C++ libs, hence this cannot be a apache problem, but a problem with 
> modules in apache.

Is it a problem with the way I compiled axis-c?
I've tried 1.5.0 and CVS, and get the same error.
I've also rebuilt xerces-c and apache, with no results.

> May be you could debug httpd with gdb and run it with -X argument inside 
> gdb, this will help you to trace the location of the error.

I've never done this before.
I've done this:

[root@lfs ~/blfs]# gdb
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
(gdb) attach 17605
Attaching to process 17605
<snip>
Reading symbols from /opt/apache/modules/libaxiscpp_mod2.so...done.
Loaded symbols for /opt/apache/modules/libaxiscpp_mod2.so
Reading symbols from /opt/apache/modules/libaxis_server.so...done.
Loaded symbols for /opt/apache/modules/libaxis_server.so
Reading symbols from /usr/lib64/libstdc++.so.6...done.
Loaded symbols for /usr/lib64/libstdc++.so.6
Reading symbols from /usr/lib64/libgcc_s.so.1...done.
Loaded symbols for /usr/lib64/libgcc_s.so.1
0x00002aaaabc69f65 in __select_nocancel () from /lib64/libc.so.6

And now what?

Thanks,
Michael


Re: Need Help Installing axis-c for Linux

Posted by Samisa Abeysinghe <sa...@gmail.com>.
Does this happen when you run apache alone without Axis C++? (I mean 
without the axis entry in httpd.conf?)

Looking at the error it looks to me that this is something to do with 
C++ libs, hence this cannot be a apache problem, but a problem with 
modules in apache.
May be you could debug httpd with gdb and run it with -X argument inside 
gdb, this will help you to trace the location of the error.

Thanks,
Samisa...
Michael Kipper wrote:

>Hi,
>
>I am installing Apache axis-c for a school project. I'm having some major
>issues getting it running.
>I'm using LinuxFromScratch, kernel 2.6.12, on an amd64.
>I've built apache httpd, xerces-c and axis-c from cvs-source, all in /opt.
>Everything builds fine, up until I start apache, and get the following in
>/var/log/apache/error_log:
>
>Thu Oct 06 19:36:55 2005] [notice] Digest: generating secret for digest
>authentication ...
>[Thu Oct 06 19:36:55 2005] [notice] Digest: done
>[Thu Oct 06 19:36:56 2005] [notice] Apache/2.0.54 (Unix) DAV/2 configured
>-- resuming normal operations
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
>[Thu Oct 06 19:36:57 2005] [notice] child pid 18946 exit signal Aborted (6)
>[Thu Oct 06 19:36:57 2005] [notice] child pid 18947 exit signal Aborted (6)
>[Thu Oct 06 19:36:57 2005] [notice] child pid 18948 exit signal Aborted (6)
>[Thu Oct 06 19:36:57 2005] [notice] child pid 18949 exit signal Aborted (6)
>[Thu Oct 06 19:36:57 2005] [notice] child pid 18950 exit signal Aborted (6)
>terminate called after throwing an instance of 'std::logic_error'
>  what():  basic_string::_S_construct NULL not valid
><snip>
>
>And so on, forever.
>Some info:
>
>[root@lfs ~]# uname -a
>Linux lfs 2.6.12 #1 Thu Sep 15 00:55:24 EDT 2005 x86_64 x86_64 x86_64
>GNU/Linux
>[root@lfs ~]# file /opt/apache/modules/libaxiscpp_mod2.so
>/opt/apache/modules/libaxiscpp_mod2.so: ELF 64-bit LSB shared object, AMD
>x86-64, version 1 (SYSV), not stripped
>[root@lfs ~]# file /opt/apache/modules/libaxis_xmlparser.so
>/opt/apache/modules/libaxis_xmlparser.so: ELF 64-bit LSB shared object, AMD
>x86-64, version 1 (SYSV), not stripped
>
>Please help!
>
>Thanks,
>Michael
>
>
>  
>