[ https://jira.jboss.org/jira/browse/JBCACHE-1221?page=com.atlassian.jira.p... ]
Manik Surtani resolved JBCACHE-1221.
------------------------------------
Fix Version/s: 3.0.0.CR2
(was: 3.0.0.GA)
Resolution: Partially Completed
Marking this as partially complete
> JDBCCacheLoader optimizations
> ------------------------------
>
> Key: JBCACHE-1221
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1221
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Cache loaders
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 3.0.0.CR2
>
>
> JDBCCacheLoader optimizations:
> - batch cache put operations during state transfer
> - batch put operations on transactions as follows:
> - batch all the puts and flush on transaction commit
> - if an remove takes place at some point, then flush before the remove (guess I'll also have to flush before a get takes place in the same transaction, have to check that)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/JBCACHE-759?page=com.atlassian.jira.pl... ]
Manik Surtani updated JBCACHE-759:
----------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0.GA)
> Create a set of deadlock-detecting unit tests
> ---------------------------------------------
>
> Key: JBCACHE-759
> URL: https://jira.jboss.org/jira/browse/JBCACHE-759
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Scripts and processes
> Affects Versions: 1.4.0.GA
> Reporter: Manik Surtani
> Assignee: Galder Zamarreno
> Priority: Minor
> Fix For: 3.1.0
>
>
> From email thread:
> "Okay, found out that jconsole also supports it:
> MBeans --> java.lang --> Threading --> Operations --> findMonitorDeadlockedThreads().
> Of course, if we could integrate this into our test suites to regularly check for deadlocks..."
> Article from JavaSpecialists:
> http://www.javaspecialists.co.za/archive/newsletter.do?issue=130&locale=e...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira