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 "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2007/09/11 14:33:35 UTC

[jira] Commented: (SANDESHA2-111) InMemory StorageManager deadlocks

    [ https://issues.apache.org/jira/browse/SANDESHA2-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526443 ] 

Hans G Knudsen commented on SANDESHA2-111:
------------------------------------------

Hi!


I just checked out the new changes to BRANCH_1_3


The problem with deadlocks has not gone away - but the problem is not as persistent as before - and only occurs once in a while.


I have seen the problem on both client and server.


Sandesha is setup to resemble the MS sync RM 1.0 implementation..



org.apache.sandesha2.storage.SandeshaStorageException: Sandesha2 Internal Error: deadlock detected. Transaction details '[InMemoryTransaction, id:6084521, name: Axis2 Task, locks: 1]', Bean details 'org.apache.sandesha2.storage.beans.RMDBean
Next Msg # : 1
Ref Msg Key: urn:uuid:794587D1E302DC8EF81189509699342
HishestInMessageNumber: 1
HishestInMessageKey: urn:uuid:C5377F97777EA642761189509700128
LastInMessageId: null
OutOfOrderRanges   : null
ServerCompletedMsgs: [1,1]
Outbound int seq   : http://localhost:8080/raspaxis13/services/NotificationRMWSS'.
	at org.apache.sandesha2.storage.inmemory.InMemoryTransaction.enlist(InMemoryTransaction.java:94)
	at org.apache.sandesha2.storage.inmemory.InMemoryStorageManager.enlistBean(InMemoryStorageManager.java:168)
	at org.apache.sandesha2.storage.inmemory.InMemoryBeanMgr.findUnique(InMemoryBeanMgr.java:141)
	at org.apache.sandesha2.storage.inmemory.InMemoryRMDBeanMgr.findUnique(InMemoryRMDBeanMgr.java:76)
	at org.apache.sandesha2.util.SandeshaUtil.getRMDBeanFromSequenceId(SandeshaUtil.java:607)
	at org.apache.sandesha2.workers.InvokerWorker.run(InvokerWorker.java:62)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
	at java.lang.Thread.run(Thread.java:613) 



> 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