You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Andrew Gatford (JIRA)" <ji...@apache.org> on 2007/11/12 17:59:51 UTC
[jira] Resolved: (SANDESHA2-111) InMemory StorageManager deadlocks
[ https://issues.apache.org/jira/browse/SANDESHA2-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gatford resolved SANDESHA2-111.
--------------------------------------
Resolution: Fixed
This was fixed in revision 575314
> InMemory StorageManager deadlocks
> ---------------------------------
>
> Key: SANDESHA2-111
> URL: https://issues.apache.org/jira/browse/SANDESHA2-111
> Project: Sandesha2
> Issue Type: Bug
> Environment: Mac OS X 10.4. Java 1.5.0. Sandesha2 Branch 1_3
> Reporter: Hans G Knudsen
> Priority: Critical
>
> Building Sandesha2 1_3 branch I see deadlock in the InMemory StorageManager in the build log.
> - org.apache.sandesha2.storage.SandeshaStorageException: Sandesha2 Internal Error: deadlock detected. Transaction details '[InMemoryTransaction, id:11435693, name: Axis2 Task, locks: 1]', Bean details 'org.apache.sandesha2.storage.beans.RMDBean
> Testing the 1_3 Sandesha2 on 1_3 Axis2 testing my own setup I see the Deadlock a lot. Running a sequence of 100 requests I see the deadlock on the server on almost all requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org