[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1096) UpgradeException should print IdentityLock instances

[Manik Surtani (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-1096?page=all ]

Manik Surtani closed JBCACHE-1096.
----------------------------------

    Resolution: Done

> UpgradeException should print IdentityLock instances
> ----------------------------------------------------
>
>                 Key: JBCACHE-1096
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1096
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP3, 2.0.0.CR2
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.0.0.CR3, 1.4.1.SP4
>
>
> When a TimeoutException is reported, the exception prints lock information (IdentityLock.toString(true)), ie.
> Read lock owners: []
> Write lock owner: GlobalTransaction:<172.26.250.183:35277>:13350
> , lock info: write owner=GlobalTransaction:<172.26.250.183:35277>:13350 (activeReaders=0, activeWriter=Thread[http-172.26.250.183-8180-10,5,jboss], waitingReaders=0, waitingWriters=0, waitingUpgrader=0)
> This is quite useful for debugging purpouses because it reports which thread is holding the lock as well 
> as the transaction id.
> However, when an UpgradeException is reported, this information is not provided:
> Read lock owners: [GlobalTransaction:<adrxww03:32804>:1628]
> Write lock owner: null
> It'd be nice if UpgradeException could print IdentityLock information as it would help debugging which thread is holding the locks

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira