OK, Monday 9/26 at 10:00 AM EST it is. Details below. Manik, you had a problem today joining a conf Ram set up using the # below; you guys overseas might test it during your Monday and if there's an issue send me a note by 9:30 EST or so. Main things to discuss are on http://wiki.jboss.org/wiki/Wiki.jsp? page=JBossCacheHibernateAlignment. Participant Passcode: 426146 Listen-only Passcode: 4261469 Phone Numbers: Toll free: 1-866-863-0570 Toll: 1-719-785-1839 Local (Australia, Sydney): + 61 282078345 Local (Austria, Vienna): + 43 2 682 205 6473 Local (Belgium, Brussels): + 32 2 789 7404 Local (Denmark, Copenhagen): + 45 32 71 49 78 Local (France, Paris): + 33 1 7304 1405 Local (Germany, Frankfurt): + 49 69 36507 2085 Local (Hong Kong): + 852 300 80 305 Local (Ireland, Dublin): + 353 1 436 7678 Local (Italy, Milan): + 39 02 896 291 98 Local (Italy, Rome): + 39 06 452 108 385 Local (Italy, Turin): + 39 01 121 792 109 Local (Japan, Tokyo): + 813 4455 1255 Local (Netherlands, Amsterdam): + 31 20 794 8154 Local (Singapore): + 65 64193725 Local (Spain, Barcelona): + 34 93 492 3169 Local (Spain, Madrid): + 34 91 788 9790 Local (Spain, Valencia): + 34 96 047 3045 Local (Sweden, Stockholm): + 46 8 5052 0391 Local (Switzerland, Geneva): + 41 22 592 7323 Local (Switzerland, Zurich): + 41 43 456 9168 Local (UK, London): + 44(0) 207 663 2215 International toll free (Argentina): 0 800 666 2108 International toll free (Australia): 1 800 069 181 International toll free (Austria): 0 800 295 856 International toll free (Bahamas): 1 800 389 0432 International toll free (Belgium): 0 800 73 378 International toll free (Brazil): 0 800 891 9738 International toll free (Chile): 123 0020 6923 International toll free (China, Northern Region): 10 800 714 0955 International toll free (China, Southern Region): 10 800 140 0931 International toll free (Colombia): 01 800 518 0492 International toll free (Costa Rica): 0 800 015 0454 International toll free (Czech Republic): 800 142 019 International toll free (Denmark): 80 887 261 International toll free (Dominican Republic): 1 888 751 4409 International toll free (France): 0 800 908 359 International toll free (Germany): 0 800 182 1595 International toll free (Greece): 00 800 161 2205 1625 International toll free (Hong Kong): 800 933 791 International toll free (Hungary): 06 800 184 16 International toll free (India): 000 800 1006 397 International toll free (Indonesia): 001 803 017 1625 International toll free (Ireland): 1 800 760 193 International toll free (Israel): 1 80 945 1625 International toll free (Italy): 800 870 328 International toll free (Japan): 00531 16 0605 International toll free (Latvia): 800 2487 International toll free (Lithuania): 8 800 9 00 62 International toll free (Luxembourg): 800 2 5774 International toll free (Malaysia): 1 800 812 593 International toll free (Mexico): 001 800 514 1625 International toll free (Monaco): 800 93 297 International toll free (Netherlands): 0 800 022 2653 International toll free (New Zealand): 0 800 450 433 International toll free (Norway): 800 192 42 International toll free (Panama): 00 800 226 1625 International toll free (Poland): 00 800 111 48 26 International toll free (Portugal): 800 819 366 International toll free (Russia): 810 800 2535 1012 International toll free (Singapore): 800 101 1767 International toll free (Slovenia): 0 800 80802 International toll free (South Africa): 0 800 999 571 International toll free (South Korea): 003 0813 1634 International toll free (Spain): 900 987 056 International toll free (Sweden): 02 079 5157 International toll free (Switzerland): 0 800 562 271 International toll free (Thailand): 001 800 156 205 1625 International toll free (Trinidad-Tobago): 1 800 205 1625 International toll free (UK): 0 800 051 3876 International toll free (Uruguay): 0004 019 0088 International toll free (Venezuela): 0 800 100 5202 Manik Surtani wrote: > +1 > On 22 Feb 2007, at 18:19, Steve Ebersole wrote: >> Brian Stansberry wrote: >>> Sent this out a while back, but the conf call didn't come off >>> due to scheduling issues. Time to try again. >>> >>> How does next Monday, Feb 26 at 10:00 AM EST sound? Once we >>> have an agreed time I'll send out conference call details. >>> Those cc'ed on the mailing lists are welcome to join in. >>> >> Also including Owen explicitly, since I am not sure if he is part >> of either list. >> >> That date/time is fine for me. > -- > Manik Surtani > Lead, JBoss Cache > JBoss, a division of Red Hat > Email: manik(a)jboss.org > Telephone: +44 7786 702 706 > MSN: manik(a)surtani.org > Yahoo/AIM/Skype: maniksurtani -- Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat brian.stansberry(a)redhat.com

Ok, so my notes from the call, based on issues from the wiki 1. Multiple caches will probably only formally make it in the next major Hibernate release - 3.3. 2 Notes on putForExternalRead() functionality, in addition to the solution presented on the wiki: - PFER only goes through if node does not exist; no-op otherwise - Force asynchronous mode for replication or invalidation to prevent any blocking - 0ms lock timeout to prevent any blocking here either. If this fails, PFER is a no-op - no to separate thread necessary, since we will be operating with a 0ms timeout, async replication and a no-op if the node exists. The only real chance of any blocking here is JGroups FC which is considered small enough a case. 3. Since JBC 1.4.1.SP1, write locks are not acquired on parents when adding or removing children, to be more accurate to repeatable read semantics. WLs can still be acquired on parents if enabled in the configuration (see "LockParentForChildInsertRemove" in http://labs.jboss.com/file-access/default/members/jbosscache/freezone/doc..., which defaults to false). As such, this contention should no longer be a problem. 4. Brian implemented for EJB3 clustering in AS 4.2, will make it's way back into HIbernate in the 3.3 timeframe? 5. Do nothing for now since the urgency is removed. Only fails on old versions of JBoss TS. In future (JBC 2.1 timeframe) look at what the microcontainer has to offer with synchronisation registrations. 6. Coordination issue 7. Galder to come back with more details here, but general consensus is not to perform transparent retries. Feel free to add stuff I may have missed or further thoughts. Very useful and productive call! Cheers, Manik