[
https://issues.apache.org/jira/browse/SANDESHA2-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527454
]
Hans G Knudsen commented on SANDESHA2-111:
------------------------------------------
Hi!
I just builded with Andrews suggestion - but now build does not finish...
Included is a patch which adds the the if-transaction block and keeps the
exsisting...
Until now it seems that the deadlock situations have gone - but I have not had
time to do some long running tests... I have only run som test on the server
starting 10 programs at the same time each running 10 RM requests...
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
