Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 47867 invoked from network); 3 Mar 2009 13:29:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 13:29:28 -0000 Received: (qmail 39613 invoked by uid 500); 3 Mar 2009 13:29:28 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 39602 invoked by uid 500); 3 Mar 2009 13:29:28 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 39593 invoked by uid 99); 3 Mar 2009 13:29:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 05:29:28 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of patelpradeep@gmail.com designates 209.85.200.175 as permitted sender) Received: from [209.85.200.175] (HELO wf-out-1314.google.com) (209.85.200.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 13:29:21 +0000 Received: by wf-out-1314.google.com with SMTP id 23so3317613wfg.28 for ; Tue, 03 Mar 2009 05:29:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=dnqF7xVh+fkCWB+mKABIGXMRhvJWwE0AWTUrCuOPJk0=; b=bk4ehYq7USvrFowCKm5t76bEvGerkHbob5rdqHCFzB4AUc/bJto7+AFi4Il0TncPEz mrJ9jInVnfQWKhThsP95I8mKthb6kLexbbPaFEVP2+XFE2NeSgkWJmIeHC12C1soJ3tU 3IY/QnmcfJmRS0waV3NFi0rCd97IJeFlYNE0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Se0Bv9SOQnTZ3/nc+d+NJrgf65jxwNpyFwUlAMfMiXKbfCk3VkAWLT3OHt5OulqkKB wuUbbS1qdr2hZaWl8QWPa5H+dBu59pWdhwYOWvF+NzL6XIa8WAYxYMIpLlBkbtUq4/H2 sBRO5WFG9M7R9hwBcxadeaf8JcvfXTZ1C65JM= MIME-Version: 1.0 Received: by 10.142.210.8 with SMTP id i8mr3596264wfg.297.1236086941037; Tue, 03 Mar 2009 05:29:01 -0800 (PST) In-Reply-To: References: Date: Tue, 3 Mar 2009 18:59:01 +0530 Message-ID: Subject: Re: unable to start axis2_http_server on AIX 6.1 From: PP To: Apache AXIS C User List Content-Type: multipart/alternative; boundary=000e0cd32e3e08366a046436eb51 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd32e3e08366a046436eb51 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Josef, Thank you for your reply. Right now i am not using Axis2c on mainframes. We also want to run it on Linux and AIX machines. I was able to build sourc= e and client/server on Linux without a single error. Now we are building on AIX and here we are facing these problems. There were lot of compilation issues. I was able to solve them by following the instructions from a Jira issue. Then i got the shared libs as .a files on AIX. Now when i start the server = i get this error message. The server tries to load the library and the lib is available in the location but the problem is in the lib format according to the error message. The error is: [Mon Mar 2 13:26:20 2009] [error] class_loader.c(162) Loading shared library ..//lib/libaxis2_http_sender.a Failed. DLERROR IS 0509-022 Cannot load module ../lib/libaxis2_http_sender.a. 0509-103 The module has an invalid magic number. Thank you, Pradeep Patel On Tue, Mar 3, 2009 at 4:23 PM, Stadelmann Josef wrote: > Hi Patel > > my name is Josef; I hope I can help you even I ask maybe very stupid > questions - but for all of them you have to find an asnwer yourself. > > my reference - I ported axis2/C a while ago to our HP OpenVMS platform > running on Alpha machines. > The OpenVMS OS does not know the concept of a DLL but something similar, > that of shrable code images. > > How did I start: I toke the windows kit and found there are some platform > specific things for windows which are different then that found in the li= nux > src kit. So all this migth be again be different fotr OpenVMS; and it was > different. > > So I had to re-implement a few things in order to have on OpenVMS deal wi= th > a .DLL-like concept - the sharable images. > > > So my first question to you is; > > what is the equivalent / similar concept of a DLL in your main frame > environment? > how would you load a main-frame-assembly containing code and data as > used in a DLL? > > I ask this because I am far away from beeing a main frame expert. And som= etimes, > you can not only port Ansi-C code, but need to undestand and then port > ideras or at least the higher concepts behind. > > Given a service in Axis2/C is packaged/assembled into a DLL for windows. > This DLL is then loaded up-on request for a particular service or module = by > the axis2 engine. > > The axis2 engine will have to find the proper DLL / (your assembly) first > by calling a seek algorythm (function); and it expects a full windows pat= h / > mainframe path returning as a result. > > The axis2/C engine would then try to access this DLL (your assembly) via > this full path and undertake steps to bring its functions and data into > memory. > > And it must be able to call a function in this brougth to memory assembyl= , > so it needs to know how to resolve the entry point to the function it wan= ts > to call. > > How will this be done / implemented in your main frame? > > > And I am 100% confident, without a good portion of main-frame > axis2-c-engine debugging and tracing you want be able to do it. I had to > single step through the axis2-engine code until I found why certain thing= s > go wrong. And then implement / make it a plat-form-specific fix. > > Josef > > > > > -----Urspr=FCngliche Nachricht----- > *Von:* PP [mailto:patelpradeep@gmail.com] > *Gesendet:* Freitag, 27. Februar 2009 15:22 > *An:* axis-c-user@ws.apache.org > *Betreff:* unable to start axis2_http_server on AIX 6.1 > > Hi, > > I followed these instructions to build axis2c on AIX. After little effort= i > was able to build the lib/server. > > > http://mail-archives.apache.org/mod_mbox/ws-axis-c-dev/200810.mbox/%3C1C5= 078180E92E94595BBC384F5F3FC3B0206A8B6@USCOBRMFA-SE-70.northamerica.cexp.com= %3E > > but when i start the server it just stops and when i see the error log. > The error message is "cannot load /lib/axis2_http_sender.a ...invalid mag= ic > number.... > > can someone please help what could be the error? > > My env is: > AIX-rpm-6.1.0.0-1 > axis2c-src-1.5.0 > > gcc-cpp-4.2.3-1 > gcc-4.2.3-1 > libgcc-4.2.3-1 > > > > -- > Thanks & Regards > Pradeep Patel > > --=20 Thanks & Regards Pradeep Patel --000e0cd32e3e08366a046436eb51 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Josef,

Thank you for your reply.

Right now i am not using = Axis2c on mainframes.

We also want to run it on Linux and AIX machin= es. I was able to build source and client/server on Linux without a single = error.

Now we are building on AIX and here we are facing these problems.
Th= ere were lot of compilation issues. I was able to solve them by following t= he instructions from a Jira issue.

Then i got the shared libs as .a = files on AIX. Now when i start the server i get this error message. The ser= ver tries to load the library and the lib is available in the location but = the problem is in the lib format according to the error message.

The error is:
[Mon Mar=A0 2 13:26:20 2009] [error] class_loader.c(16= 2) Loading shared library ..//lib/libaxis2_http_sender.
a=A0 Failed. DLERROR IS=A0=A0=A0=A0=A0=A0=A0 0509-022 Cannot l= oad module ../lib/libaxis2_http_sender.a.
=A0=A0=A0=A0=A0=A0=A0 0509-103=A0=A0 The module has an invalid magic number= .



Thank you,
Pradeep Patel


On Tue, Mar 3, 2009 at 4:23 PM, Stadelmann Josef <josef.stadelmann@axa-winterthur.ch> wrote:
Hi=20 Patel
=A0
my name is=20 Josef; I hope I can help you even I ask maybe very stupid questions - but f= or=20 all of them you have to find an asnwer yourself.
=A0
my reference=20 - I ported axis2/C a while ago to our HP OpenVMS platform running on Alpha= =20 machines.
The OpenVMS = OS does not know the concept of a DLL but=20 something similar, that of=A0shrable code images.
=A0
How did I=20 start: I toke the windows kit and found there are some platform specific th= ings=20 for windows which are different then that found in the linux src kit.=A0So= =20 all this migth be again be different fotr OpenVMS; and it was=20 different.
=A0
So I had to=20 re-implement a few things=A0in order to have on OpenVMS deal with a .DLL-li= ke=20 concept - the sharable images.
=A0
=A0
So my first=20 question to you is;
=A0
=A0=A0=A0 what is the equ= ivalent / similar concept of a=20 DLL in your main frame environment?
=A0=A0=A0 how would you l= oad a main-frame-assembly containing code and data=20 as used in a DLL?
=A0
I ask this=20 because I am far away from beeing a main frame expert. = And=A0sometimes, you can not only port=A0Ansi-C code= , but=20 need to undestand and then port ideras or at least the higher concepts behi= nd.=20
=A0
Given a=20 service in Axis2/C is packaged/assembled into a DLL for windows. This DLL i= s=20 then loaded up-on=A0request for=A0a particular=A0service or=20 module=A0by the axis2 engine.
=A0
The axis2=20 engine will=A0have=A0to find the proper DLL / (your assembly) first by=20 calling a seek algorythm (function); and it expects a=A0full windows path /= =20 mainframe path returning as a result.
=A0
The axis2/C=20 engine=A0would then try to access this DLL (your assembly)=A0via this full= =20 path=A0and undertake steps to bring=A0its functions and data into=20 memory.
=A0
And it must=20 be able to call a function in this brougth to memory assembyl, so it needs = to=20 know how to resolve the entry point to the function it wants to=20 call.
=A0
How will this=20 be done / implemented in your main frame?
=A0
=A0
And I am 100%=20 confident, without a good portion of main-frame axis2-c-engine debugging an= d=20 tracing you want be able to do it. I had to single step through the axis2-e= ngine=20 code until I found why certain things go wrong. And then implement / make i= t a=20 plat-form-specific fix.
=A0
Josef
=A0
=A0
=A0
-----Urs= pr=FCngliche Nachricht-----
Von: PP=20 [mailto:patel= pradeep@gmail.com]
Gesendet: Freitag, 27. Februar 2009=20 15:22
An: axis-c-user@ws.apache.org
Betreff: unable to=20 start axis2_http_server on AIX 6.1

Hi,

I followed=20 these instructions to build axis2c on AIX. After little effort i was able= to=20 build the lib/server.

http://mail-= archives.apache.org/mod_mbox/ws-axis-c-dev/200810.mbox/%3C1C5078180E92E9459= 5BBC384F5F3FC3B0206A8B6@USCOBRMFA-SE-70.northamerica.cexp.com%3E

but=20 when i start the server it just stops and when i see the error log.
Th= e=20 error message is "cannot load /lib/axis2_http_sender.a ...invalid ma= gic=20 number....
=A0
can someone please help what could be the=20 error?

My env=20 is:
AIX-rpm-6.1.0.0-1
axis2c-src-1.5.0

gcc-cpp-4.2.3-1
gc= c-4.2.3-1
libgcc-4.2.3-1



--=20
Thanks & Regards
Pradeep Patel



--
Thanks & RegardsPradeep Patel
--000e0cd32e3e08366a046436eb51--