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 (JIRA)" <ax...@ws.apache.org> on 2004/11/23 08:47:22 UTC
[jira] Created: (AXISCPP-281) Client hangs due to possible locking problem
Client hangs due to possible locking problem
--------------------------------------------
Key: AXISCPP-281
URL: http://nagoya.apache.org/jira/browse/AXISCPP-281
Project: Axis-C++
Type: Bug
Components: Serialization/Deserialization
Versions: current (nightly)
Environment: Linux with axis2 transport and Xerces parser lib
Reporter: Samisa Abeysinghe
Priority: Blocker
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?)
It looks to me that it is failing to go past lock() call in DeserializerPool::getInstance() of
src/engine/DeserializerPool.cpp.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-281) Client hangs due to possible locking problem
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-281?page=history ]
Samisa Abeysinghe closed AXISCPP-281:
-------------------------------------
Assign To: Samisa Abeysinghe
Resolution: Fixed
Fix Version: 1.4 Alpha
Strange but true: adding -lpthread to libaxiscpp_client_la_LIBADD in
ws-axis/c/src/engine/client/Makefile.am solved the problem.
> Client hangs due to possible locking problem
> --------------------------------------------
>
> Key: AXISCPP-281
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-281
> Project: Axis-C++
> Type: Bug
> Components: Serialization/Deserialization
> Versions: current (nightly)
> Environment: Linux with axis2 transport and Xerces parser lib
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Priority: Blocker
> Fix For: 1.4 Alpha
>
> 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?)
> It looks to me that it is failing to go past lock() call in DeserializerPool::getInstance() of
> src/engine/DeserializerPool.cpp.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira