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 "Unai Uribarri (JIRA)" <ax...@ws.apache.org> on 2004/12/30 12:50:12 UTC

[jira] Updated: (AXISCPP-345) Server thread locks when fails to load the service shared library

     [ http://nagoya.apache.org/jira/browse/AXISCPP-345?page=history ]

Unai Uribarri updated AXISCPP-345:
----------------------------------

    Attachment: SharedObjectLocking.diff

Instead of just solve this particular locking bug, I've reworked the SharedObject framework to use the Scoped Locking pattern.
To lock an object, just creates a <Lock> object passing a pointer to the object to lock. The lock is released automatically at lock destruction or manually calling the unlock method.
This way, the code is more simple and the locks are always unlocked when a exception is raised (don't forget that any allocation, such as the push_back method of the containers, can raise an exception).

What do you think of this change?


> Server thread locks when fails to load the service shared library
> -----------------------------------------------------------------
>
>          Key: AXISCPP-345
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-345
>      Project: Axis-C++
>         Type: Bug
>  Environment: RedHat 9
>     Reporter: Unai Uribarri
>  Attachments: SharedObjectLocking.diff
>
> When HandlerLoader can't load a library, it raises an exception and several locks are left in held state.
> Following request hangups forever.

-- 
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