You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Samisa Abeysinghe <sa...@yahoo.com> on 2004/11/22 06:13:34 UTC

Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

When I try to run clients with the latest CVS code, the client hangs infinitely.

Ruuning with gdb and intrrupting shows that it client is waiting for a lock. Unfortunately gdb
does not show where the lock is being used.

(gdb) bt
#0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
#2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
#3  0x00ba8338 in ?? () from /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
#4  0x09b97c48 in ?? ()
#5  0x00d6affc in ?? () from /lib/tls/libc.so.6
#6  0x09b96598 in ?? ()
#7  0x09ba1c60 in ?? ()
#8  0xfee53778 in ?? ()
#9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
Previous frame identical to this frame (corrupt stack?)

Any thoughts whay this is happening.

Thanks,
Samisa...


		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


Caching and restoring MessageData properties

Posted by sanjaya singharage <sa...@opensource.lk>.
In Call::Initialize(), properties in the member Call::m_handlerProperties,
are populated to the MessageData object of the ClientAxisEngine.
Where does the reverse happen (i.e. population of Call::m_handlerProperties
with MessageData properties)? Or does it happen at all? Is this only for
setting properties on the request path? Call::unInitialize() seems to be the
choice for the reverse process, but it doesn't seem to happen in that
method.

can some one comment please?

sanjaya.



Ant build [WAS: Re: Run fails [WAS:Re: Build error log ...}]

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I cannot just run ant build on Linux after checking out source from CVS in AXISCPP_HOME.

I get the error:
/home/samisa/autoCVS/cvsAutoBuild/build/buildClient.xml:7: Directory /home/obj/objects creation
was not successful for an unknown reason.

If I fix this I get few more...

I could fix those and let the user run ant on source tree as it is. 
It it OK to change 
    dir.obj = ${basedir}/../../../obj 
to
    dir.obj = ${basedir}/deploy/obj 
and 
    dir.zips = ${basedir}/../../../zips
to
    dir.zips = ${basedir}/deploy/zips 

Would this have any side effects to the nightly build?

Thanks,
Samisa...

--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> I tried the noghly build today and it is not blocking.
> Is this something to do with the GNU make build? Has there been any files removed lately from
> the
> source that the GNU make build is not updated for?
> 
> I also have few comments on the nightly build:
> 
> 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as -l option only picks
> those
> 
> 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are placed in deploy/lib
> usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
> 
> 3. There are neoumourous name differences in the so files available with the nightly build and
> those build with GNU make system. (Simply speaking they are not consistant) I think .so file
> names
> that come with nightly build are more appropriate. We have to make the GNU make to build the
> same
> and also change the docs accordingly.
> 
> 4. Nither ant not make could be used to build samples. I had to use g++ on command line. Why not
> have the samples built for the nightly build?
> 
> 5. simple_axis_server is placed in bin, usually this is placed in deploy/bin
> 
> 6. Excecute rights are not set on simple_axis_server binary
> 
> 
> 
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> 
> > I will try the nightly build.
> > 
> > However, I am still facing the same problem with the CVS checkout with GNU make build.
> > 
> > Samisa...
> > --- John Hawkins <HA...@uk.ibm.com> wrote:
> > 
> > > 
> > > 
> > > 
> > > 
> > > Our build from the 19th did not have this problem. Perhaps try the
> > > overnight build on the web-site?
> > > 
> > > John Hawkins
> > > 
> > > 
> > > 
> > > 
> > >                                                                            
> > >              Samisa Abeysinghe                                             
> > >              <samisa_abeysingh                                             
> > >              e@yahoo.com>                                               To 
> > >                                        Apache AXIS C Developers List       
> > >              22/11/2004 10:01          <ax...@ws.apache.org>          
> > >                                                                         cc 
> > >                                                                            
> > >              Please respond to                                     Subject 
> > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
> > >              Developers List"          log for CVS source - Summary: build 
> > >                                        success}                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > > 
> > > 
> > > 
> > > 
> > > Is anybody else experiancing this?
> > > 
> > > I think it is failing to go past lock() call in
> > > DeserializerPool::getInstance() of
> > > src/engine/DeserializerPool.cpp.
> > > 
> > > However, I am still strugling to find a solution. Appreciate any help.
> > > 
> > > Thanks,
> > > Samisa...
> > > 
> > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > > 
> > > > When I try to run clients with the latest CVS code, the client hangs
> > > infinitely.
> > > >
> > > > Ruuning with gdb and intrrupting shows that it client is waiting for a
> > > lock. Unfortunately gdb
> > > > does not show where the lock is being used.
> > > >
> > > > (gdb) bt
> > > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> > > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > #3  0x00ba8338 in ?? () from
> > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > #4  0x09b97c48 in ?? ()
> > > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > #6  0x09b96598 in ?? ()
> > > > #7  0x09ba1c60 in ?? ()
> > > > #8  0xfee53778 in ?? ()
> > > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > Previous frame identical to this frame (corrupt stack?)
> > > >
> > > > Any thoughts whay this is happening.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Meet the all-new My Yahoo! - Try it today!
> > > > http://my.yahoo.com
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > The all-new My Yahoo! - Get yours free!
> > > http://my.yahoo.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 		
> > __________________________________ 
> > Do you Yahoo!? 
> > The all-new My Yahoo! - Get yours free! 
> > http://my.yahoo.com 
> >  
> > 
> > 
> 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Meet the all-new My Yahoo! - Try it today! 
> http://my.yahoo.com 
>  
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


It Runs :Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
At last..........it is *working*.

Strange but true: adding -lpthread to libaxiscpp_client_la_LIBADD in
ws-axis/c/src/engine/client/Makefile.am solved the problem.

So, it is a problem with build files (and wasted lot of my time because I thought it was a bug :((
)

Samisa...


--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> Hi John,
>    I got it from http://cvs.apache.org/dist/axis/nightly/. The site shows last modified day to
> be
> 22-Nov-2004. 
> 
>     I tried the Linux build and did not get the locking problem with that, which means it is
> working correctly.
> 
>     BTW - It is very nice to see the nightly builds going. :)
> Thanks,
> Samisa...
> 
> --- John Hawkins <HA...@uk.ibm.com> wrote:
> 
> > 
> > 
> > 
> > 
> > Hi Samisa,
> > 
> > I'm afraid to say that I'm a little confused with the nightly build at the
> > moment. According to the web-site the last update was on Octboer the 26th.
> > But according to our ftp logs it was yesterday so I'm not sure what build
> > you actually got ! Can you tell? I'm going to try and investigate later
> > today but v. busy !
> > 
> > 
> > John Hawkins
> > 
> > 
> > 
> > 
> >                                                                            
> >              Samisa Abeysinghe                                             
> >              <samisa_abeysingh                                             
> >              e@yahoo.com>                                               To 
> >                                        Apache AXIS C Developers List       
> >              23/11/2004 08:19          <ax...@ws.apache.org>          
> >                                                                         cc 
> >                                                                            
> >              Please respond to                                     Subject 
> >               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
> >              Developers List"          log for CVS source - Summary: build 
> >                                        success}                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> > 
> > 
> > 
> > 
> > I tried the noghly build today and it is not blocking.
> > Is this something to do with the GNU make build? Has there been any files
> > removed lately from the
> > source that the GNU make build is not updated for?
> > 
> > I also have few comments on the nightly build:
> > 
> > 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as
> > -l option only picks
> > those
> > 
> > 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are
> > placed in deploy/lib
> > usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
> > 
> > 3. There are neoumourous name differences in the so files available with
> > the nightly build and
> > those build with GNU make system. (Simply speaking they are not consistant)
> > I think .so file names
> > that come with nightly build are more appropriate. We have to make the GNU
> > make to build the same
> > and also change the docs accordingly.
> > 
> > 4. Nither ant not make could be used to build samples. I had to use g++ on
> > command line. Why not
> > have the samples built for the nightly build?
> > 
> > 5. simple_axis_server is placed in bin, usually this is placed in
> > deploy/bin
> > 
> > 6. Excecute rights are not set on simple_axis_server binary
> > 
> > 
> > 
> > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > 
> > > I will try the nightly build.
> > >
> > > However, I am still facing the same problem with the CVS checkout with
> > GNU make build.
> > >
> > > Samisa...
> > > --- John Hawkins <HA...@uk.ibm.com> wrote:
> > >
> > > >
> > > >
> > > >
> > > >
> > > > Our build from the 19th did not have this problem. Perhaps try the
> > > > overnight build on the web-site?
> > > >
> > > > John Hawkins
> > > >
> > > >
> > > >
> > > >
> > > >
> > 
> > > >              Samisa Abeysinghe
> > 
> > > >              <samisa_abeysingh
> > 
> > > >              e@yahoo.com>
> > To
> > > >                                        Apache AXIS C Developers List
> > 
> > > >              22/11/2004 10:01          <ax...@ws.apache.org>
> > 
> > > >
> > cc
> > > >
> > 
> > > >              Please respond to
> > Subject
> > > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build
> > error
> > > >              Developers List"          log for CVS source - Summary:
> > build
> > > >                                        success}
> > 
> > > >
> > 
> > > >
> > 
> > > >
> > 
> > > >
> > 
> > > >
> > 
> > > >
> > 
> > > >
> > > >
> > > >
> > > >
> > > > Is anybody else experiancing this?
> > > >
> > > > I think it is failing to go past lock() call in
> > > > DeserializerPool::getInstance() of
> > > > src/engine/DeserializerPool.cpp.
> > > >
> > > > However, I am still strugling to find a solution. Appreciate any help.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > > >
> > > > > When I try to run clients with the latest CVS code, the client hangs
> > > > infinitely.
> > > > >
> > > > > Ruuning with gdb and intrrupting shows that it client is waiting for
> > a
> > > > lock. Unfortunately gdb
> > > > > does not show where the lock is being used.
> > > > >
> > > > > (gdb) bt
> > > > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > > #1  0x003f2cbe in __lll_mutex_lock_wait () from
> > /lib/tls/libpthread.so.0
> > > > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > > #3  0x00ba8338 in ?? () from
> > > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > > #4  0x09b97c48 in ?? ()
> > > > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > > #6  0x09b96598 in ?? ()
> > > > > #7  0x09ba1c60 in ?? ()
> > > > > #8  0xfee53778 in ?? ()
> > > > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > > Previous frame identical to this frame (corrupt stack?)
> > > > >
> > > > > Any thoughts whay this is happening.
> > > > >
> > > > > Thanks,
> > > > > Samisa...
> > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Meet the all-new My Yahoo! - Try it today!
> > > > > http://my.yahoo.com
> > > > >
> > > > >
> > > > >
> > > >
> 
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
In http://www.apache.org/dist/ws/axis-c/, even though the package names say current, they are
really the 1.3 final releases. 
In other words this is the place where final releases are placed.

Damitha, correct me if I am wrong.

Thanks,
Samisa...

--- John Hawkins <HA...@uk.ibm.com> wrote:

> 
> 
> 
> 
> Cool - yes, the actual "cvs site" is correct and working but when you go
> here ->http://www.apache.org/dist/ws/axis-c/
> the files are different. unfortunately Adrian was doing all this and he's
> on holiday this wk. so, if anyone wants a nightly build this week they'll
> have to go to cvs directly.
> 
> 
> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              23/11/2004 12:53          <ax...@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
>              Developers List"          log for CVS source - Summary: build 
>                                        success}                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> Hi John,
>    I got it from http://cvs.apache.org/dist/axis/nightly/. The site shows
> last modified day to be
> 22-Nov-2004.
> 
>     I tried the Linux build and did not get the locking problem with that,
> which means it is
> working correctly.
> 
>     BTW - It is very nice to see the nightly builds going. :)
> Thanks,
> Samisa...
> 
> --- John Hawkins <HA...@uk.ibm.com> wrote:
> 
> >
> >
> >
> >
> > Hi Samisa,
> >
> > I'm afraid to say that I'm a little confused with the nightly build at
> the
> > moment. According to the web-site the last update was on Octboer the
> 26th.
> > But according to our ftp logs it was yesterday so I'm not sure what build
> > you actually got ! Can you tell? I'm going to try and investigate later
> > today but v. busy !
> >
> >
> > John Hawkins
> >
> >
> >
> >
> >
> 
> >              Samisa Abeysinghe
> 
> >              <samisa_abeysingh
> 
> >              e@yahoo.com>
> To
> >                                        Apache AXIS C Developers List
> 
> >              23/11/2004 08:19          <ax...@ws.apache.org>
> 
> >
> cc
> >
> 
> >              Please respond to
> Subject
> >               "Apache AXIS C           Re: Run fails [WAS:Re: Build error
> 
> >              Developers List"          log for CVS source - Summary:
> build
> >                                        success}
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> >
> >
> >
> > I tried the noghly build today and it is not blocking.
> > Is this something to do with the GNU make build? Has there been any files
> > removed lately from the
> > source that the GNU make build is not updated for?
> >
> > I also have few comments on the nightly build:
> >
> > 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so
> as
> > -l option only picks
> > those
> >
> > 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are
> > placed in deploy/lib
> > usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
> >
> > 3. There are neoumourous name differences in the so files available with
> > the nightly build and
> > those build with GNU make system. (Simply speaking they are not
> consistant)
> > I think .so file names
> > that come with nightly build are more appropriate. We have to make the
> GNU
> > make to build the same
> > and also change the docs accordingly.
> >
> > 4. Nither ant not make could be used to build samples. I had to use g++
> on
> > command line. Why not
> > have the samples built for the nightly build?
> >
> > 5. simple_axis_server is placed in bin, usually this is placed in
> > deploy/bin
> >
> > 6. Excecute rights are not set on simple_axis_server binary
> >
> >
> >
> > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> >
> > > I will try the nightly build.
> > >
> > > However, I am still facing the same problem with the CVS checkout with
> > GNU make build.
> > >
> > > Samisa...
> > > --- John Hawkins <HA...@uk.ibm.com> wrote:
> > >
> > > >
> > > >
> > > >
> > > >
> > > > Our build from the 19th did not have this problem. Perhaps try the
> > > > overnight build on the web-site?
> > > >
> > > > John Hawkins
> > > >
> > > >
> > > >
> > > >
> > > >
> >
> > > >              Samisa Abeysinghe
> >
> > > >              <samisa_abeysingh
> >
> > > >              e@yahoo.com>
> > To
> > > >                                        Apache AXIS C Developers List
> >
> > > >              22/11/2004 10:01          <ax...@ws.apache.org>
> >
> > > >
> > cc
> > > >
> >
> > > >              Please respond to
> > Subject
> > > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build
> > error
> > > >              Developers List"          log for CVS source - Summary:
> > build
> > > >                                        success}
> >
> > > >
> >
> > > >
> >
> 
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by John Hawkins <HA...@uk.ibm.com>.



Cool - yes, the actual "cvs site" is correct and working but when you go
here ->http://www.apache.org/dist/ws/axis-c/
the files are different. unfortunately Adrian was doing all this and he's
on holiday this wk. so, if anyone wants a nightly build this week they'll
have to go to cvs directly.


John Hawkins




                                                                           
             Samisa Abeysinghe                                             
             <samisa_abeysingh                                             
             e@yahoo.com>                                               To 
                                       Apache AXIS C Developers List       
             23/11/2004 12:53          <ax...@ws.apache.org>          
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
             Developers List"          log for CVS source - Summary: build 
                                       success}                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Hi John,
   I got it from http://cvs.apache.org/dist/axis/nightly/. The site shows
last modified day to be
22-Nov-2004.

    I tried the Linux build and did not get the locking problem with that,
which means it is
working correctly.

    BTW - It is very nice to see the nightly builds going. :)
Thanks,
Samisa...

--- John Hawkins <HA...@uk.ibm.com> wrote:

>
>
>
>
> Hi Samisa,
>
> I'm afraid to say that I'm a little confused with the nightly build at
the
> moment. According to the web-site the last update was on Octboer the
26th.
> But according to our ftp logs it was yesterday so I'm not sure what build
> you actually got ! Can you tell? I'm going to try and investigate later
> today but v. busy !
>
>
> John Hawkins
>
>
>
>
>

>              Samisa Abeysinghe

>              <samisa_abeysingh

>              e@yahoo.com>
To
>                                        Apache AXIS C Developers List

>              23/11/2004 08:19          <ax...@ws.apache.org>

>
cc
>

>              Please respond to
Subject
>               "Apache AXIS C           Re: Run fails [WAS:Re: Build error

>              Developers List"          log for CVS source - Summary:
build
>                                        success}

>

>

>

>

>

>

>
>
>
>
> I tried the noghly build today and it is not blocking.
> Is this something to do with the GNU make build? Has there been any files
> removed lately from the
> source that the GNU make build is not updated for?
>
> I also have few comments on the nightly build:
>
> 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so
as
> -l option only picks
> those
>
> 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are
> placed in deploy/lib
> usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
>
> 3. There are neoumourous name differences in the so files available with
> the nightly build and
> those build with GNU make system. (Simply speaking they are not
consistant)
> I think .so file names
> that come with nightly build are more appropriate. We have to make the
GNU
> make to build the same
> and also change the docs accordingly.
>
> 4. Nither ant not make could be used to build samples. I had to use g++
on
> command line. Why not
> have the samples built for the nightly build?
>
> 5. simple_axis_server is placed in bin, usually this is placed in
> deploy/bin
>
> 6. Excecute rights are not set on simple_axis_server binary
>
>
>
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
>
> > I will try the nightly build.
> >
> > However, I am still facing the same problem with the CVS checkout with
> GNU make build.
> >
> > Samisa...
> > --- John Hawkins <HA...@uk.ibm.com> wrote:
> >
> > >
> > >
> > >
> > >
> > > Our build from the 19th did not have this problem. Perhaps try the
> > > overnight build on the web-site?
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
>
> > >              Samisa Abeysinghe
>
> > >              <samisa_abeysingh
>
> > >              e@yahoo.com>
> To
> > >                                        Apache AXIS C Developers List
>
> > >              22/11/2004 10:01          <ax...@ws.apache.org>
>
> > >
> cc
> > >
>
> > >              Please respond to
> Subject
> > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build
> error
> > >              Developers List"          log for CVS source - Summary:
> build
> > >                                        success}
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
> > >
> > >
> > >
> > > Is anybody else experiancing this?
> > >
> > > I think it is failing to go past lock() call in
> > > DeserializerPool::getInstance() of
> > > src/engine/DeserializerPool.cpp.
> > >
> > > However, I am still strugling to find a solution. Appreciate any
help.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > >
> > > > When I try to run clients with the latest CVS code, the client
hangs
> > > infinitely.
> > > >
> > > > Ruuning with gdb and intrrupting shows that it client is waiting
for
> a
> > > lock. Unfortunately gdb
> > > > does not show where the lock is being used.
> > > >
> > > > (gdb) bt
> > > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > #1  0x003f2cbe in __lll_mutex_lock_wait () from
> /lib/tls/libpthread.so.0
> > > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > #3  0x00ba8338 in ?? () from
> > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > #4  0x09b97c48 in ?? ()
> > > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > #6  0x09b96598 in ?? ()
> > > > #7  0x09ba1c60 in ?? ()
> > > > #8  0xfee53778 in ?? ()
> > > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > Previous frame identical to this frame (corrupt stack?)
> > > >
> > > > Any thoughts whay this is happening.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Meet the all-new My Yahoo! - Try it today!
> > > > http://my.yahoo.com
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > The all-new My Yahoo! - Get yours free!
> > > http://my.yahoo.com
> > >
> > >
> > >
> > >
> > >
> >
> >
>
=== message truncated ===




__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com





Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi John,
   I got it from http://cvs.apache.org/dist/axis/nightly/. The site shows last modified day to be
22-Nov-2004. 

    I tried the Linux build and did not get the locking problem with that, which means it is
working correctly.

    BTW - It is very nice to see the nightly builds going. :)
Thanks,
Samisa...

--- John Hawkins <HA...@uk.ibm.com> wrote:

> 
> 
> 
> 
> Hi Samisa,
> 
> I'm afraid to say that I'm a little confused with the nightly build at the
> moment. According to the web-site the last update was on Octboer the 26th.
> But according to our ftp logs it was yesterday so I'm not sure what build
> you actually got ! Can you tell? I'm going to try and investigate later
> today but v. busy !
> 
> 
> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              23/11/2004 08:19          <ax...@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
>              Developers List"          log for CVS source - Summary: build 
>                                        success}                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> I tried the noghly build today and it is not blocking.
> Is this something to do with the GNU make build? Has there been any files
> removed lately from the
> source that the GNU make build is not updated for?
> 
> I also have few comments on the nightly build:
> 
> 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as
> -l option only picks
> those
> 
> 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are
> placed in deploy/lib
> usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
> 
> 3. There are neoumourous name differences in the so files available with
> the nightly build and
> those build with GNU make system. (Simply speaking they are not consistant)
> I think .so file names
> that come with nightly build are more appropriate. We have to make the GNU
> make to build the same
> and also change the docs accordingly.
> 
> 4. Nither ant not make could be used to build samples. I had to use g++ on
> command line. Why not
> have the samples built for the nightly build?
> 
> 5. simple_axis_server is placed in bin, usually this is placed in
> deploy/bin
> 
> 6. Excecute rights are not set on simple_axis_server binary
> 
> 
> 
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> 
> > I will try the nightly build.
> >
> > However, I am still facing the same problem with the CVS checkout with
> GNU make build.
> >
> > Samisa...
> > --- John Hawkins <HA...@uk.ibm.com> wrote:
> >
> > >
> > >
> > >
> > >
> > > Our build from the 19th did not have this problem. Perhaps try the
> > > overnight build on the web-site?
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> 
> > >              Samisa Abeysinghe
> 
> > >              <samisa_abeysingh
> 
> > >              e@yahoo.com>
> To
> > >                                        Apache AXIS C Developers List
> 
> > >              22/11/2004 10:01          <ax...@ws.apache.org>
> 
> > >
> cc
> > >
> 
> > >              Please respond to
> Subject
> > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build
> error
> > >              Developers List"          log for CVS source - Summary:
> build
> > >                                        success}
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> 
> > >
> > >
> > >
> > >
> > > Is anybody else experiancing this?
> > >
> > > I think it is failing to go past lock() call in
> > > DeserializerPool::getInstance() of
> > > src/engine/DeserializerPool.cpp.
> > >
> > > However, I am still strugling to find a solution. Appreciate any help.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > >
> > > > When I try to run clients with the latest CVS code, the client hangs
> > > infinitely.
> > > >
> > > > Ruuning with gdb and intrrupting shows that it client is waiting for
> a
> > > lock. Unfortunately gdb
> > > > does not show where the lock is being used.
> > > >
> > > > (gdb) bt
> > > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > #1  0x003f2cbe in __lll_mutex_lock_wait () from
> /lib/tls/libpthread.so.0
> > > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > #3  0x00ba8338 in ?? () from
> > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > #4  0x09b97c48 in ?? ()
> > > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > #6  0x09b96598 in ?? ()
> > > > #7  0x09ba1c60 in ?? ()
> > > > #8  0xfee53778 in ?? ()
> > > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > Previous frame identical to this frame (corrupt stack?)
> > > >
> > > > Any thoughts whay this is happening.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Meet the all-new My Yahoo! - Try it today!
> > > > http://my.yahoo.com
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > The all-new My Yahoo! - Get yours free!
> > > http://my.yahoo.com
> > >
> > >
> > >
> > >
> > >
> >
> >
> 
=== message truncated ===



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by John Hawkins <HA...@uk.ibm.com>.



Hi Samisa,

I'm afraid to say that I'm a little confused with the nightly build at the
moment. According to the web-site the last update was on Octboer the 26th.
But according to our ftp logs it was yesterday so I'm not sure what build
you actually got ! Can you tell? I'm going to try and investigate later
today but v. busy !


John Hawkins




                                                                           
             Samisa Abeysinghe                                             
             <samisa_abeysingh                                             
             e@yahoo.com>                                               To 
                                       Apache AXIS C Developers List       
             23/11/2004 08:19          <ax...@ws.apache.org>          
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
             Developers List"          log for CVS source - Summary: build 
                                       success}                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




I tried the noghly build today and it is not blocking.
Is this something to do with the GNU make build? Has there been any files
removed lately from the
source that the GNU make build is not updated for?

I also have few comments on the nightly build:

1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as
-l option only picks
those

2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are
placed in deploy/lib
usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib

3. There are neoumourous name differences in the so files available with
the nightly build and
those build with GNU make system. (Simply speaking they are not consistant)
I think .so file names
that come with nightly build are more appropriate. We have to make the GNU
make to build the same
and also change the docs accordingly.

4. Nither ant not make could be used to build samples. I had to use g++ on
command line. Why not
have the samples built for the nightly build?

5. simple_axis_server is placed in bin, usually this is placed in
deploy/bin

6. Excecute rights are not set on simple_axis_server binary



--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> I will try the nightly build.
>
> However, I am still facing the same problem with the CVS checkout with
GNU make build.
>
> Samisa...
> --- John Hawkins <HA...@uk.ibm.com> wrote:
>
> >
> >
> >
> >
> > Our build from the 19th did not have this problem. Perhaps try the
> > overnight build on the web-site?
> >
> > John Hawkins
> >
> >
> >
> >
> >

> >              Samisa Abeysinghe

> >              <samisa_abeysingh

> >              e@yahoo.com>
To
> >                                        Apache AXIS C Developers List

> >              22/11/2004 10:01          <ax...@ws.apache.org>

> >
cc
> >

> >              Please respond to
Subject
> >               "Apache AXIS C           Re: Run fails [WAS:Re: Build
error
> >              Developers List"          log for CVS source - Summary:
build
> >                                        success}

> >

> >

> >

> >

> >

> >

> >
> >
> >
> >
> > Is anybody else experiancing this?
> >
> > I think it is failing to go past lock() call in
> > DeserializerPool::getInstance() of
> > src/engine/DeserializerPool.cpp.
> >
> > However, I am still strugling to find a solution. Appreciate any help.
> >
> > Thanks,
> > Samisa...
> >
> > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> >
> > > When I try to run clients with the latest CVS code, the client hangs
> > infinitely.
> > >
> > > Ruuning with gdb and intrrupting shows that it client is waiting for
a
> > lock. Unfortunately gdb
> > > does not show where the lock is being used.
> > >
> > > (gdb) bt
> > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > #1  0x003f2cbe in __lll_mutex_lock_wait () from
/lib/tls/libpthread.so.0
> > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > #3  0x00ba8338 in ?? () from
> > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > #4  0x09b97c48 in ?? ()
> > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > #6  0x09b96598 in ?? ()
> > > #7  0x09ba1c60 in ?? ()
> > > #8  0xfee53778 in ?? ()
> > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > Previous frame identical to this frame (corrupt stack?)
> > >
> > > Any thoughts whay this is happening.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Meet the all-new My Yahoo! - Try it today!
> > > http://my.yahoo.com
> > >
> > >
> > >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The all-new My Yahoo! - Get yours free!
> > http://my.yahoo.com
> >
> >
> >
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
>
>
>




__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com





Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
There is a definite problem with the SharedObject::lock () method inherited by DeserializerPool
class.

The problem occures when it is called by DeserializerPool class. SerializerPool calls the same
method prior to DeserializerPool calls it and does not hang. The client hangs when
DeserializerPool calls SharedObject::lock()

If I comment out  pthread_mutex_lock (mut); in SharedObject::lock () it works fine. 
I am not sure why this is happening. Also it is very strange that others are not seeing this
problem. :(

Samisa...

--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> I tried the noghly build today and it is not blocking.
> Is this something to do with the GNU make build? Has there been any files removed lately from
> the
> source that the GNU make build is not updated for?
> 
> I also have few comments on the nightly build:
> 
> 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as -l option only picks
> those
> 
> 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are placed in deploy/lib
> usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
> 
> 3. There are neoumourous name differences in the so files available with the nightly build and
> those build with GNU make system. (Simply speaking they are not consistant) I think .so file
> names
> that come with nightly build are more appropriate. We have to make the GNU make to build the
> same
> and also change the docs accordingly.
> 
> 4. Nither ant not make could be used to build samples. I had to use g++ on command line. Why not
> have the samples built for the nightly build?
> 
> 5. simple_axis_server is placed in bin, usually this is placed in deploy/bin
> 
> 6. Excecute rights are not set on simple_axis_server binary
> 
> 
> 
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> 
> > I will try the nightly build.
> > 
> > However, I am still facing the same problem with the CVS checkout with GNU make build.
> > 
> > Samisa...
> > --- John Hawkins <HA...@uk.ibm.com> wrote:
> > 
> > > 
> > > 
> > > 
> > > 
> > > Our build from the 19th did not have this problem. Perhaps try the
> > > overnight build on the web-site?
> > > 
> > > John Hawkins
> > > 
> > > 
> > > 
> > > 
> > >                                                                            
> > >              Samisa Abeysinghe                                             
> > >              <samisa_abeysingh                                             
> > >              e@yahoo.com>                                               To 
> > >                                        Apache AXIS C Developers List       
> > >              22/11/2004 10:01          <ax...@ws.apache.org>          
> > >                                                                         cc 
> > >                                                                            
> > >              Please respond to                                     Subject 
> > >               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
> > >              Developers List"          log for CVS source - Summary: build 
> > >                                        success}                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > >                                                                            
> > > 
> > > 
> > > 
> > > 
> > > Is anybody else experiancing this?
> > > 
> > > I think it is failing to go past lock() call in
> > > DeserializerPool::getInstance() of
> > > src/engine/DeserializerPool.cpp.
> > > 
> > > However, I am still strugling to find a solution. Appreciate any help.
> > > 
> > > Thanks,
> > > Samisa...
> > > 
> > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > > 
> > > > When I try to run clients with the latest CVS code, the client hangs
> > > infinitely.
> > > >
> > > > Ruuning with gdb and intrrupting shows that it client is waiting for a
> > > lock. Unfortunately gdb
> > > > does not show where the lock is being used.
> > > >
> > > > (gdb) bt
> > > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> > > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > #3  0x00ba8338 in ?? () from
> > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > #4  0x09b97c48 in ?? ()
> > > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > #6  0x09b96598 in ?? ()
> > > > #7  0x09ba1c60 in ?? ()
> > > > #8  0xfee53778 in ?? ()
> > > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > Previous frame identical to this frame (corrupt stack?)
> > > >
> > > > Any thoughts whay this is happening.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Meet the all-new My Yahoo! - Try it today!
> > > > http://my.yahoo.com
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > > __________________________________
> > > Do you Yahoo!?
> > > The all-new My Yahoo! - Get yours free!
> > > http://my.yahoo.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 		
> > __________________________________ 
> > Do you Yahoo!? 
> > The all-new My Yahoo! - Get yours free! 
> > http://my.yahoo.com 
> >  
> > 
> > 
> 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Meet the all-new My Yahoo! - Try it today! 
> http://my.yahoo.com 
>  
> 
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I tried the noghly build today and it is not blocking.
Is this something to do with the GNU make build? Has there been any files removed lately from the
source that the GNU make build is not updated for?

I also have few comments on the nightly build:

1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as -l option only picks
those

2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are placed in deploy/lib
usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib

3. There are neoumourous name differences in the so files available with the nightly build and
those build with GNU make system. (Simply speaking they are not consistant) I think .so file names
that come with nightly build are more appropriate. We have to make the GNU make to build the same
and also change the docs accordingly.

4. Nither ant not make could be used to build samples. I had to use g++ on command line. Why not
have the samples built for the nightly build?

5. simple_axis_server is placed in bin, usually this is placed in deploy/bin

6. Excecute rights are not set on simple_axis_server binary



--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> I will try the nightly build.
> 
> However, I am still facing the same problem with the CVS checkout with GNU make build.
> 
> Samisa...
> --- John Hawkins <HA...@uk.ibm.com> wrote:
> 
> > 
> > 
> > 
> > 
> > Our build from the 19th did not have this problem. Perhaps try the
> > overnight build on the web-site?
> > 
> > John Hawkins
> > 
> > 
> > 
> > 
> >                                                                            
> >              Samisa Abeysinghe                                             
> >              <samisa_abeysingh                                             
> >              e@yahoo.com>                                               To 
> >                                        Apache AXIS C Developers List       
> >              22/11/2004 10:01          <ax...@ws.apache.org>          
> >                                                                         cc 
> >                                                                            
> >              Please respond to                                     Subject 
> >               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
> >              Developers List"          log for CVS source - Summary: build 
> >                                        success}                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> >                                                                            
> > 
> > 
> > 
> > 
> > Is anybody else experiancing this?
> > 
> > I think it is failing to go past lock() call in
> > DeserializerPool::getInstance() of
> > src/engine/DeserializerPool.cpp.
> > 
> > However, I am still strugling to find a solution. Appreciate any help.
> > 
> > Thanks,
> > Samisa...
> > 
> > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > 
> > > When I try to run clients with the latest CVS code, the client hangs
> > infinitely.
> > >
> > > Ruuning with gdb and intrrupting shows that it client is waiting for a
> > lock. Unfortunately gdb
> > > does not show where the lock is being used.
> > >
> > > (gdb) bt
> > > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> > > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > #3  0x00ba8338 in ?? () from
> > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > #4  0x09b97c48 in ?? ()
> > > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > #6  0x09b96598 in ?? ()
> > > #7  0x09ba1c60 in ?? ()
> > > #8  0xfee53778 in ?? ()
> > > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > Previous frame identical to this frame (corrupt stack?)
> > >
> > > Any thoughts whay this is happening.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Meet the all-new My Yahoo! - Try it today!
> > > http://my.yahoo.com
> > >
> > >
> > >
> > 
> > 
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > The all-new My Yahoo! - Get yours free!
> > http://my.yahoo.com
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> The all-new My Yahoo! - Get yours free! 
> http://my.yahoo.com 
>  
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I will try the nightly build.

However, I am still facing the same problem with the CVS checkout with GNU make build.

Samisa...
--- John Hawkins <HA...@uk.ibm.com> wrote:

> 
> 
> 
> 
> Our build from the 19th did not have this problem. Perhaps try the
> overnight build on the web-site?
> 
> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              22/11/2004 10:01          <ax...@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
>              Developers List"          log for CVS source - Summary: build 
>                                        success}                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> Is anybody else experiancing this?
> 
> I think it is failing to go past lock() call in
> DeserializerPool::getInstance() of
> src/engine/DeserializerPool.cpp.
> 
> However, I am still strugling to find a solution. Appreciate any help.
> 
> Thanks,
> Samisa...
> 
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> 
> > When I try to run clients with the latest CVS code, the client hangs
> infinitely.
> >
> > Ruuning with gdb and intrrupting shows that it client is waiting for a
> lock. Unfortunately gdb
> > does not show where the lock is being used.
> >
> > (gdb) bt
> > #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> > #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > #3  0x00ba8338 in ?? () from
> /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > #4  0x09b97c48 in ?? ()
> > #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> > #6  0x09b96598 in ?? ()
> > #7  0x09ba1c60 in ?? ()
> > #8  0xfee53778 in ?? ()
> > #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > Previous frame identical to this frame (corrupt stack?)
> >
> > Any thoughts whay this is happening.
> >
> > Thanks,
> > Samisa...
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Meet the all-new My Yahoo! - Try it today!
> > http://my.yahoo.com
> >
> >
> >
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
> 
> 
> 
> 
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 


Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by John Hawkins <HA...@uk.ibm.com>.



Our build from the 19th did not have this problem. Perhaps try the
overnight build on the web-site?

John Hawkins




                                                                           
             Samisa Abeysinghe                                             
             <samisa_abeysingh                                             
             e@yahoo.com>                                               To 
                                       Apache AXIS C Developers List       
             22/11/2004 10:01          <ax...@ws.apache.org>          
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           Re: Run fails [WAS:Re: Build error  
             Developers List"          log for CVS source - Summary: build 
                                       success}                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Is anybody else experiancing this?

I think it is failing to go past lock() call in
DeserializerPool::getInstance() of
src/engine/DeserializerPool.cpp.

However, I am still strugling to find a solution. Appreciate any help.

Thanks,
Samisa...

--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> When I try to run clients with the latest CVS code, the client hangs
infinitely.
>
> Ruuning with gdb and intrrupting shows that it client is waiting for a
lock. Unfortunately gdb
> does not show where the lock is being used.
>
> (gdb) bt
> #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> #3  0x00ba8338 in ?? () from
/home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> #4  0x09b97c48 in ?? ()
> #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> #6  0x09b96598 in ?? ()
> #7  0x09ba1c60 in ?? ()
> #8  0xfee53778 in ?? ()
> #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> Previous frame identical to this frame (corrupt stack?)
>
> Any thoughts whay this is happening.
>
> Thanks,
> Samisa...
>
>
>
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
>




__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com





Re: Run fails [WAS:Re: Build error log for CVS source - Summary: build success}

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Is anybody else experiancing this?

I think it is failing to go past lock() call in DeserializerPool::getInstance() of
src/engine/DeserializerPool.cpp.

However, I am still strugling to find a solution. Appreciate any help.

Thanks,
Samisa...

--- Samisa Abeysinghe <sa...@yahoo.com> wrote:

> When I try to run clients with the latest CVS code, the client hangs infinitely.
> 
> Ruuning with gdb and intrrupting shows that it client is waiting for a lock. Unfortunately gdb
> does not show where the lock is being used.
> 
> (gdb) bt
> #0  0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1  0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> #2  0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> #3  0x00ba8338 in ?? () from /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> #4  0x09b97c48 in ?? ()
> #5  0x00d6affc in ?? () from /lib/tls/libc.so.6
> #6  0x09b96598 in ?? ()
> #7  0x09ba1c60 in ?? ()
> #8  0xfee53778 in ?? ()
> #9  0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> Previous frame identical to this frame (corrupt stack?)
> 
> Any thoughts whay this is happening.
> 
> Thanks,
> Samisa...
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Meet the all-new My Yahoo! - Try it today! 
> http://my.yahoo.com 
>  
> 
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com