[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1041)

[Galder Zamarreno (JIRA)]

Tutorial - GUI/beanshell
 block if node modified within transaction and node status queried via GUI
In-Reply-To: <27496970.1178097510296.JavaMail.jira at cloud.prod.atl2.jboss.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

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

Galder Zamarreno resolved JBCACHE-1041.
---------------------------------------

    Resolution: Done

GUI updates originating from clicking on nodes in the tree structure and 
mouse clicks are now handled in a separate thread to avoid locking the GUI. 
TimeoutExceptions that could be thrown from these code areas provide a 
hint on what might the cause of the exception.

> 
Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1041
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1041
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.CR1
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>          Time Spent: 2 hours
>  Remaining Estimate: 0 minutes
>
> Instructions:
> - add a node to the cache
> - start a transaction
> - do a put on that node
> - clicking on the node via the GUI to check that the node has not been 
> updated blocks both the GUI and the beanshell. This is due to not being able to 
> acquire the read lock on the node to show it.
> - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't.
> Solution:
> - Updates on the GUI should be handled in a different thread so that it does 
> not block the shell? While the shell is blocked, the current transaction cannot be 
> committed, leaving the user no option.

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