Re: SSL configuration question
Hi,
Do you have any other Axis2/C related library in your LD_LIBRARY_PATH?
If so, can you remove them or put ${AXIS2C_HOME}/lib/ as the first
entry in $LD_LIBRARY_PATH?
Also, can you do "ldd and see what are the
libraries/paths link to client?
Regards,
Shankar
On Fri, Oct 2, 2009 at 1:04 AM, wrote:
> Shankar,
> Thank you for your help. I reconfigured as follows.
>
> cd /home/gbs/axis2c/axis2c-src-1.6.0
> su
> export AXIS2C_HOME=/usr/local/axis2c
> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${AXIS2C_HOME}/lib/
> ./configure --enable-openssl=yes --prefix=${AXIS2C_HOME}
> --with-apache2="/usr/local/apache2/include" > config_out 2> config_err
>
> I found no errors or warnings in config_out; config_err was empty. I found
> no errors in the config.log file. The only warning seems to be unrelated:
> cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but
> not for C
> Relevant lines from config.log are:
>
> $ ./configure --enable-openssl=yes --prefix=/usr/local/axis2c
> --with-apache2=/usr/local/apache2/include
> ...
> configure:21638: checking whether to use openssl
> configure:21651: result: yes
> ...
> config.status:746: creating src/core/transport/http/sender/ssl/Makefile
> ...
> configure:23296: === configuring in util
> (/home/gbs/axis2c/axis2c-src-1.6.0/util)
> configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c'
> '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include'
> --cache-file=/dev/null --srcdir=.
> configure:23296: === configuring in axiom
> (/home/gbs/axis2c/axis2c-src-1.6.0/axiom)
> configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c'
> '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include'
> --cache-file=/dev/null --srcdir=.
> configure:23296: === configuring in neethi
> (/home/gbs/axis2c/axis2c-src-1.6.0/neethi)
> configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c'
> '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include'
> --cache-file=/dev/null --srcdir=.
> configure:23296: === configuring in guththila
> (/home/gbs/axis2c/axis2c-src-1.6.0/guththila)
> configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c'
> '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include'
> --cache-file=/dev/null --srcdir=.
>
> The diff command showed this config.log to be identical to that of the
> previous configure attempt.
> I appreciate your help with this.
> George
>
> -- Forwarded Message: --
> From: Selvaratnam Uthaiyashankar
> To: Apache AXIS C User List
> Subject: Re: SSL configuration question
> Date: Thu, 01 Oct 2009 03:02:18 +
>
>
> Hi,
>
> It seems Axis2/C engine (client side) is not configured with
> --enable-openssl=yes. Is there any errors when you configure? Can you
> configure with --enable-openssl=yes again and see?
>
> Regards,
> Shankar
>
> On Sun, Sep 27, 2009 at 8:14 AM, wrote:
>> I have been using axis2c-src-1.6.0 for a few days with an existing service
>> running Red Hat EL 4.7 and Apache2 httpd-2.0.63. Axis2/C is deployed as an
>> Apache2 module. The samples and hello work with http transport, but I have
>> not run https successfully with axis2 yet. The problem appears to be
>> similar
>> to that reported 2009-05-14 by chankm (Kwang Mien), but there does not
>> seem
>> to be a response to that message in the archive. Can anyone explain why
>> axis2c is not using https here?
>> Thanks for the help.
>> George Sherwood
>>
>> I am using a test system with a self-signed certificate. SSL is working
>> with
>> httpd; e.g. https://64.232.245.115/pub/promos.php is accessed as expected
>> from a remote browser. However SSL does not appear to be configured
>> correctly for axis2.
>>
>> Both of the following commands seem to run OK.
>> ./echo http://64.232.245.115/axis2/services/echo
>> ./hello http://64.232.245.115/axis2/services/hello
>>
>> But the responses for the corresponding https endpoints do not.
>> ./echo https://64.232.245.115:443/axis2/services/echo
>> yields "echo client invoke FAILED!"
>> ./hello https://64.232.245.115:443/axis2/services/hello
>> yields "hello client invoke FAILED!"
>>
>> The echo.log contains the following lines.
>> [Sat Sep 26 20:01:13 2009] [error] http_client.c(271) Transport protocol
>> is
>> unsupported by axis2
>> [Sat Sep 26 20:01:13 2009] [error] http_client.c(272) Invalid Transport
>> Protocol, HTTPS transport not enabled.
>> [Sat Sep 26 20:01:13 2009] [error] http_client.c(544) client data stream
>> null or socket error for host 64.232.245.115 and 443 port
>> [Sat Sep 26 20:01:13 2009] [error] http_client.c(548) A read attempt(HTTP)
>> for the reply without sending the request
>> [Sat Sep 26 20:01:13 2009] [error] http_sender.c(1381) status_code < 0
>> [Sat Sep 26 20:01:13 2009] [error] engine.c(179) Transport sender invoke
>> failed
>> [Sat Sep 26 20:01:13 2009] [error] echo.c(145) Stub invoke FAILED: Error
>> code: 75 :: A read attempt(HTTP) for the reply without sending the reques
Re: Problem with Ubuntu
Hi, Glad to hear that you solved the problem. Regards, Shankar On Fri, Oct 2, 2009 at 3:34 AM, Jose M Medina V wrote: > Hi Selvaratnam, > I already solve the problem. This consist in I didn=92t put the =20 > definition of the function axis2_srvprb_agrApuesta in the library so I =20= > > this cause a problem of integer pointer assignation in 64 bits =20 > environment. > > Thanks for your interest in the problem. > On Sep 30, 2009, at 10:46 PM, Selvaratnam Uthaiyashankar wrote: > > Hi, > > Can you run using simple axis server and see whether it crashes? When > you are debugging httpd with -X flag, it runs in a single process. > That might be the reason why it works.. If it crash it simple axis > server, it might be easy to debug. > > Regards, > Shankar > > > > > José M. Medina V. > Wesam Consulting > jose_med...@wesamconsulting.com > Mobile: +58(416)613-3302 +58(414)019-0580 > Ofc: +58(212)959-4155 Ext. 204 > BB pin: 31E562BF > Caracas - Venezuela > > > > > > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
Re: Problem with Ubuntu
Hi Selvaratnam, I already solve the problem. This consist in I didn=92t put the =20 definition of the function axis2_srvprb_agrApuesta in the library so I =20= this cause a problem of integer pointer assignation in 64 bits =20 environment. Thanks for your interest in the problem. On Sep 30, 2009, at 10:46 PM, Selvaratnam Uthaiyashankar wrote: Hi, Can you run using simple axis server and see whether it crashes? When you are debugging httpd with -X flag, it runs in a single process. That might be the reason why it works.. If it crash it simple axis server, it might be easy to debug. Regards, Shankar José M. Medina V. Wesam Consulting jose_med...@wesamconsulting.com Mobile: +58(416)613-3302 +58(414)019-0580 Ofc: +58(212)959-4155 Ext. 204 BB pin: 31E562BF Caracas - Venezuela
Re: SSL configuration question
Shankar,Thank you for your help. I reconfigured as follows.cd /home/gbs/axis2c/axis2c-src-1.6.0suexport AXIS2C_HOME=/usr/local/axis2cexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${AXIS2C_HOME}/lib/./configure --enable-openssl=yes --prefix=${AXIS2C_HOME} --with-apache2="/usr/local/apache2/include" > config_out 2> config_errI found no errors or warnings in config_out; config_err was empty. I found no errors in the config.log file. The only warning seems to be unrelated:cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for CRelevant lines from config.log are: $ ./configure --enable-openssl=yes --prefix=/usr/local/axis2c --with-apache2=/usr/local/apache2/include...configure:21638: checking whether to use opensslconfigure:21651: result: yes...config.status:746: creating src/core/transport/http/sender/ssl/Makefile...configure:23296: === configuring in util (/home/gbs/axis2c/axis2c-src-1.6.0/util)configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c' '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include' --cache-file=/dev/null --srcdir=.configure:23296: === configuring in axiom (/home/gbs/axis2c/axis2c-src-1.6.0/axiom)configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c' '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include' --cache-file=/dev/null --srcdir=.configure:23296: === configuring in neethi (/home/gbs/axis2c/axis2c-src-1.6.0/neethi)configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c' '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include' --cache-file=/dev/null --srcdir=.configure:23296: === configuring in guththila (/home/gbs/axis2c/axis2c-src-1.6.0/guththila)configure:23399: running /bin/sh ./configure '--prefix=/usr/local/axis2c' '--enable-openssl=yes' '--with-apache2=/usr/local/apache2/include' --cache-file=/dev/null --srcdir=.The diff command showed this config.log to be identical to that of the previous configure attempt.I appreciate your help with this.George
-- Forwarded Message: --
From: Selvaratnam Uthaiyashankar
To: Apache AXIS C User List
Subject: Re: SSL configuration question
Date: Thu, 01 Oct 2009 03:02:18 +
Hi,
It seems Axis2/C engine (client side) is not configured with
--enable-openssl=yes. Is there any errors when you configure? Can you
configure with --enable-openssl=yes again and see?
Regards,
Shankar
On Sun, Sep 27, 2009 at 8:14 AM, wrote:
> I have been using axis2c-src-1.6.0 for a few days with an existing service
> running Red Hat EL 4.7 and Apache2 httpd-2.0.63. Axis2/C is deployed as an
> Apache2 module. The samples and hello work with http transport, but I have
> not run https successfully with axis2 yet. The problem appears to be similar
> to that reported 2009-05-14 by chankm (Kwang Mien), but there does not seem
> to be a response to that message in the archive. Can anyone explain why
> axis2c is not using https here?
> Thanks for the help.
> George Sherwood
>
> I am using a test system with a self-signed certificate. SSL is working with
> httpd; e.g. https://64.232.245.115/pub/promos.php is accessed as expected
> from a remote browser. However SSL does not appear to be configured
> correctly for axis2.
>
> Both of the following commands seem to run OK.
> ./echo http://64.232.245.115/axis2/services/echo
> ./hello http://64.232.245.115/axis2/services/hello
>
> But the responses for the corresponding https endpoints do not.
> ./echo https://64.232.245.115:443/axis2/services/echo
> yields "echo client invoke FAILED!"
> ./hello https://64.232.245.115:443/axis2/services/hello
> yields "hello client invoke FAILED!"
>
> The echo.log contains the following lines.
> [Sat Sep 26 20:01:13 2009] [error] http_client.c(271) Transport protocol is
> unsupported by axis2
> [Sat Sep 26 20:01:13 2009] [error] http_client.c(272) Invalid Transport
> Protocol, HTTPS transport not enabled.
> [Sat Sep 26 20:01:13 2009] [error] http_client.c(544) client data stream
> null or socket error for host 64.232.245.115 and 443 port
> [Sat Sep 26 20:01:13 2009] [error] http_client.c(548) A read attempt(HTTP)
> for the reply without sending the request
> [Sat Sep 26 20:01:13 2009] [error] http_sender.c(1381) status_code < 0
> [Sat Sep 26 20:01:13 2009] [error] engine.c(179) Transport sender invoke
> failed
> [Sat Sep 26 20:01:13 2009] [error] echo.c(145) Stub invoke FAILED: Error
> code: 75 :: A read attempt(HTTP) for the reply without sending the request
>
> And the hello_client.log contains the following lines.
> [Sat Sep 26 20:17:19 2009] [error] http_client.c(271) Transport protocol is
> unsupported by axis2
> [Sat Sep 26 20:17:19 2009] [error] http_client.c(272) Invalid Transport
> Protocol, HTTPS transport not enabled.
> [Sat Sep 26 20:17:19 2009] [error] http_client.c(544) client data stream
> null or socket error for host 64.232.245.115 and 443 port
> [Sat Sep 26 20:17:19 2009] [error] http_client.c(548) A read attempt(HTTP)
