[JBoss-dev] [JBoss JIRA] Created: (JGRP-54) Remove flow control from UNICAST (provided by FC)

Remove flow control from UNICAST (provided by FC) - Key: JGRP-54 URL: http://jira.jboss.com/jira/browse/JGRP-54 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 Flow

[JBoss-dev] [JBoss JIRA] Closed: (JGRP-3) Timer in UDP.bundling is implemented incorrectly

[ http://jira.jboss.com/jira/browse/JGRP-3?page=history ] Bela Ban closed JGRP-3: --- Resolution: Done rewrote bundling - uses its own thread now, no needfor timer Timer in UDP.bundling is implemented incorrectly

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-4) UDP.bundling too slow

[ http://jira.jboss.com/jira/browse/JGRP-4?page=history ] Bela Ban resolved JGRP-4: - Resolution: Done Rewrote impl. General problem is that bundling usually exceeds ethernet MTU of 1500 bytes, so is counter-productive. See JGroups wiki for details

[JBoss-dev] [JBoss JIRA] Closed: (JGRP-16) GMS.getDigest() needs to be run in a separate thread

[ http://jira.jboss.com/jira/browse/JGRP-16?page=history ] Bela Ban closed JGRP-16: Resolution: Done analyzed it; not needed GMS.getDigest() needs to be run in a separate thread Key: JGRP

[JBoss-dev] [JBoss JIRA] Created: (JGRP-52) Replace RWLock with util.concurrent

Replace RWLock with util.concurrent --- Key: JGRP-52 URL: http://jira.jboss.com/jira/browse/JGRP-52 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- This message is automatically

[JBoss-dev] [JBoss JIRA] Created: (JGRP-53) NakReceiverWindow: replace updateLowestSeen() with more efficient function

NakReceiverWindow: replace updateLowestSeen() with more efficient function -- Key: JGRP-53 URL: http://jira.jboss.com/jira/browse/JGRP-53 Project: JGroups Type: Task Reporter: Bela Ban

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-52) Replace RWLock with util.concurrent

[ http://jira.jboss.com/jira/browse/JGRP-52?page=history ] Bela Ban resolved JGRP-52: -- Resolution: Done Replace RWLock with util.concurrent --- Key: JGRP-52 URL: http://jira.jboss.com/jira/browse/JGRP

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-53) NakReceiverWindow: replace updateHighestSeen() with more efficient function

[ http://jira.jboss.com/jira/browse/JGRP-53?page=history ] Bela Ban updated JGRP-53: - Summary: NakReceiverWindow: replace updateHighestSeen() with more efficient function (was: NakReceiverWindow: replace updateLowestSeen() with more efficient function

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-53) NakReceiverWindow: replace updateHighestSeen() with more efficient function

[ http://jira.jboss.com/jira/browse/JGRP-53?page=history ] Bela Ban resolved JGRP-53: -- Resolution: Done done NakReceiverWindow: replace updateHighestSeen() with more efficient function

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-126) CacheLoader doesn't load children after loading an attribute

CacheLoader doesn't load children after loading an attribute Key: JBCACHE-126 URL: http://jira.jboss.com/jira/browse/JBCACHE-126 Project: JBoss Cache Type: Bug Reporter: Bela Ban Assigned to: Bela Ban

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-126) CacheLoader doesn't load children after loading an attribute

[ http://jira.jboss.com/jira/browse/JBCACHE-126?page=history ] Bela Ban resolved JBCACHE-126: -- Resolution: Done Added children_loaded to Node, changed CacheLoaderInterceptor CacheLoader doesn't load children after loading an attribute

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-39) A TCP stack does not correctly detect failure (pulled cable) for certain TCPPING configurations

[ http://jira.jboss.com/jira/browse/JGRP-39?page=history ] Bela Ban resolved JGRP-39: -- Resolution: Done Works with 2.2.8 (CVS head) A TCP stack does not correctly detect failure (pulled cable) for certain TCPPING configurations

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-48) Add version number of manifest

[ http://jira.jboss.com/jira/browse/JGRP-48?page=history ] Bela Ban resolved JGRP-48: -- Resolution: Done Add version number of manifest -- Key: JGRP-48 URL: http://jira.jboss.com/jira/browse/JGRP-48

[JBoss-dev] [JBoss JIRA] Created: (JGRP-51) Update manifest and Version.java with version number

Update manifest and Version.java with version number Key: JGRP-51 URL: http://jira.jboss.com/jira/browse/JGRP-51 Project: JGroups Type: Sub-task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP

[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: ShunTest.java Example Connections remain open even after the channel port changes, while using TCP

[JBoss-dev] [JBoss JIRA] Commented: (JGRP-40) Connections remain open even after the channel port changes, while using TCP

[ http://jira.jboss.com/jira/browse/JGRP-40?page=comments#action_12316766 ] Bela Ban commented on JGRP-40: -- Ran the attached example with both default.xml and tcp.xml (attached as well). Works okay with 2.2.8 CVS head Connections remain open even after

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP

[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: default.xml Connections remain open even after the channel port changes, while using TCP

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-40) Connections remain open even after the channel port changes, while using TCP

[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban resolved JGRP-40: -- Resolution: Done Please re-open the case if you find the problem still exists Connections remain open even after the channel port changes, while using TCP

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-40) Connections remain open even after the channel port changes, while using TCP

[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ] Bela Ban updated JGRP-40: - Attachment: tcp.xml Connections remain open even after the channel port changes, while using TCP

[JBoss-dev] [JBoss JIRA] Closed: (JGRP-45) JVM Crashes when starting three groups at the same time

[ http://jira.jboss.com/jira/browse/JGRP-45?page=history ] Bela Ban closed JGRP-45: Resolution: Done This has nothing to do with JGroups; the log clearly shows that it was the JMS invocation layer which crashed. Although I doubt that code can crash the VM

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-31) Problem with MERGE2 when not using multicast

[ http://jira.jboss.com/jira/browse/JGRP-31?page=history ] Bela Ban resolved JGRP-31: -- Resolution: Done I added the merge_leader flag to GMS. Another possibility to solve this is to use the TCP:MPING combination Problem with MERGE2 when not using

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-22) Enhance the ENCRYPT or the ENCRYPT1_4 protocol

[ http://jira.jboss.com/jira/browse/JGRP-22?page=history ] Bela Ban resolved JGRP-22: -- Resolution: Done Fix Version: 2.2.8 (was: 2.2.9) Enhance the ENCRYPT or the ENCRYPT1_4 protocol

[JBoss-dev] [JBoss JIRA] Commented: (JGRP-28) Remove sendDummyPacket() in UDP

[ http://jira.jboss.com/jira/browse/JGRP-28?page=comments#action_12316770 ] Bela Ban commented on JGRP-28: -- Was caused by sendDummyPacket() in UDP - will remove it shortly Remove sendDummyPacket() in UDP --- Key

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-28) Remove sendDummyPacket() in UDP

[ http://jira.jboss.com/jira/browse/JGRP-28?page=history ] Bela Ban resolved JGRP-28: -- Resolution: Done Removed sendDummyPacket() Remove sendDummyPacket() in UDP --- Key: JGRP-28 URL: http

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ] Bela Ban updated JGRP-33: - Priority: Major (was: Critical) downgraded to major; probably due to incorrect use of JGroups JGroups throws OutOfMemoryError after running for a few hours

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-19) MERGE2 slows down traffic

[ http://jira.jboss.com/jira/browse/JGRP-19?page=history ] Bela Ban resolved JGRP-19: -- Resolution: Done Presence of MERGE2 doesn't make a diff in CVS head anymore MERGE2 slows down traffic - Key: JGRP-19 URL

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-122) Convert JBoss Logger to commons-logging

[ http://jira.jboss.com/jira/browse/JBCACHE-122?page=history ] Bela Ban resolved JBCACHE-122: -- Resolution: Done Convert JBoss Logger to commons-logging --- Key: JBCACHE-122 URL: http

[JBoss-dev] [JBoss JIRA] Closed: (JBCACHE-123) Get rid of JBoss-dependent libs

[ http://jira.jboss.com/jira/browse/JBCACHE-123?page=history ] Bela Ban closed JBCACHE-123: Resolution: Done This task will be done later (in 1.3, when we convert to interfaces) Get rid of JBoss-dependent libs

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-51) Create standalone CVS version of JBossCache

[ http://jira.jboss.com/jira/browse/JBCACHE-51?page=history ] Bela Ban resolved JBCACHE-51: - Resolution: Done New module is JBossCache, check out: cvs co JBossCache Create standalone CVS version of JBossCache

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-124) Concurrent access problem in Node

Concurrent access problem in Node - Key: JBCACHE-124 URL: http://jira.jboss.com/jira/browse/JBCACHE-124 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.3

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-124) Concurrent access problem in Node

[ http://jira.jboss.com/jira/browse/JBCACHE-124?page=history ] Bela Ban resolved JBCACHE-124: -- Resolution: Done Made it a ConcurrentReaderHashMap Concurrent access problem in Node - Key: JBCACHE-124

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-125) Release 1.2.3 final

Release 1.2.3 final --- Key: JBCACHE-125 URL: http://jira.jboss.com/jira/browse/JBCACHE-125 Project: JBoss Cache Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.3 -- This message is automatically generated by JIRA

[JBoss-dev] [JBoss JIRA] Created: (JGRP-50) Release 2.2.8 final

Release 2.2.8 final --- Key: JGRP-50 URL: http://jira.jboss.com/jira/browse/JGRP-50 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- This message is automatically generated by JIRA. - If you think

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-70) Make JBossCache an XAResource

[ http://jira.jboss.com/jira/browse/JBCACHE-70?page=comments#action_12316637 ] Bela Ban commented on JBCACHE-70: - Interesting read: http://www.jboss.org/wiki/Wiki.jsp?page=TransactionRecovery Make JBossCache an XAResource

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-49) org.jgroups.protocols.UDP.stopThreads() doesn't stop outgoing_packet_handler

[ http://jira.jboss.com/jira/browse/JGRP-49?page=history ] Bela Ban updated JGRP-49: - Fix Version: 2.2.8 org.jgroups.protocols.UDP.stopThreads() doesn't stop outgoing_packet_handler

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-49) org.jgroups.protocols.UDP.stopThreads() doesn't stop outgoing_packet_handler

[ http://jira.jboss.com/jira/browse/JGRP-49?page=history ] Bela Ban resolved JGRP-49: -- Resolution: Done Fixed. Although this didn't cause multiple outgoing packet threads to be created b/c OutgoingPacketHandler.start() would not start a new thread

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-20) Address translation in transport (NAT support)

[ http://jira.jboss.com/jira/browse/JGRP-20?page=history ] Bela Ban updated JGRP-20: - Summary: Address translation in transport (NAT support) (was: Address translation in transport) Address translation in transport (NAT support

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE

[ http://jira.jboss.com/jira/browse/JBCACHE-117?page=history ] Bela Ban updated JBCACHE-117: - Fix Version: 1.2.3 (was: 1.2.2) Unnecessary lock acquisition with IsolationLevel.NONE

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-121) Update JBoss head, 3.x and 4.x with jboss-cache.jar

Update JBoss head, 3.x and 4.x with jboss-cache.jar --- Key: JBCACHE-121 URL: http://jira.jboss.com/jira/browse/JBCACHE-121 Project: JBoss Cache Type: Task Versions: 1.2.1 Reporter: Bela Ban Assigned

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-104) Mass Removal

[ http://jira.jboss.com/jira/browse/JBCACHE-104?page=history ] Bela Ban updated JBCACHE-104: - Fix Version: 1.2.4 (was: 1.2.3) Mass Removal Key: JBCACHE-104 URL: http://jira.jboss.com/jira/browse

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-54) JBossCacheAop nees a customized interceptor option

[ http://jira.jboss.com/jira/browse/JBCACHE-54?page=history ] Bela Ban updated JBCACHE-54: Fix Version: 1.2.4 (was: 1.2.3) JBossCacheAop nees a customized interceptor option

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-100) RMI-based DelegatingCacheLoader

[ http://jira.jboss.com/jira/browse/JBCACHE-100?page=history ] Bela Ban updated JBCACHE-100: - Fix Version: 1.2.4 (was: 1.2.3) RMI-based DelegatingCacheLoader --- Key: JBCACHE-100 URL

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-53) JBossCacheAop can use prepare annotation

[ http://jira.jboss.com/jira/browse/JBCACHE-53?page=history ] Bela Ban updated JBCACHE-53: Fix Version: 1.2.4 (was: 1.2.3) JBossCacheAop can use prepare annotation -- Key: JBCACHE-53

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-7) JBossCacheAop benchmark and performance tuning

[ http://jira.jboss.com/jira/browse/JBCACHE-7?page=history ] Bela Ban updated JBCACHE-7: --- Fix Version: 1.2.4 (was: 1.2.3) JBossCacheAop benchmark and performance tuning -- Key

[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=history ] Bela Ban reassigned JBCACHE-98: --- Assign To: Ben Wang (was: Bela Ban) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-53) JBossCacheAop can use prepare annotation

[ http://jira.jboss.com/jira/browse/JBCACHE-53?page=history ] Bela Ban reassigned JBCACHE-53: --- Assign To: Ben Wang (was: Bela Ban) JBossCacheAop can use prepare annotation -- Key: JBCACHE-53

[JBoss-dev] [JBoss JIRA] Closed: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[ http://jira.jboss.com/jira/browse/JBCACHE-116?page=history ] Bela Ban closed JBCACHE-116: Resolution: Duplicate Issue duplicate of JBCACHE-118 CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[JBoss-dev] [JBoss JIRA] Resolved: (JGRP-36) TCP:PING, TCP transport combined with multicast discovery

[ http://jira.jboss.com/jira/browse/JGRP-36?page=history ] Bela Ban resolved JGRP-36: -- Resolution: Done Implemented as MPING. Stack would be for example TCP:MPING, check JGroups/conf/mtcp.xml for an example. MPING uses its own IP multicast socket

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-110) Cache aop Overriding toString or hashCode will trigger stack overflow

[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=history ] Bela Ban updated JBCACHE-110: - Fix Version: 1.2.4 (was: 1.2.3) Cache aop Overriding toString or hashCode will trigger stack overflow

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-85) TreeCacheAop object event listener

[ http://jira.jboss.com/jira/browse/JBCACHE-85?page=history ] Bela Ban updated JBCACHE-85: Fix Version: 1.2.4 (was: 1.2.3) TreeCacheAop object event listener -- Key: JBCACHE-85 URL

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-123) Get rid of JBoss-dependent libs

Get rid of JBoss-dependent libs --- Key: JBCACHE-123 URL: http://jira.jboss.com/jira/browse/JBCACHE-123 Project: JBoss Cache Type: Sub-task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.3 -- This message

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-122) Convert JBoss Logger to commons-logging

Convert JBoss Logger to commons-logging Key: JBCACHE-122 URL: http://jira.jboss.com/jira/browse/JBCACHE-122 Project: JBoss Cache Type: Sub-task Reporter: Bela Ban Assigned to: Bela Ban get rid of jboss-common

[JBoss-dev] [JBoss JIRA] Reopened: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[ http://jira.jboss.com/jira/browse/JBCACHE-116?page=history ] Bela Ban reopened JBCACHE-116: -- There is always a exists() followed by a get() on the CacheLoader. We should club these 2 methods together into 1 CacheLoaderInterceptor calls

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[ http://jira.jboss.com/jira/browse/JBCACHE-116?page=history ] Bela Ban updated JBCACHE-116: - Fix Version: 1.2.4 (was: 1.2.2) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-118) Inefficient CacheLoader.exists() followed by CacheLoader.get()

[ http://jira.jboss.com/jira/browse/JBCACHE-118?page=history ] Bela Ban updated JBCACHE-118: - Fix Version: 1.2.4 (was: 1.2.3) Inefficient CacheLoader.exists() followed by CacheLoader.get

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-103) ConfiguratorFactory#getConfigStream should not throw a AccessControlException

[ http://jira.jboss.com/jira/browse/JBCACHE-103?page=history ] Bela Ban updated JBCACHE-103: - Fix Version: 1.2.4 (was: 1.2.3) ConfiguratorFactory#getConfigStream should not throw a AccessControlException

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-119) Missing notification for remove() and addChild()

[ http://jira.jboss.com/jira/browse/JBCACHE-119?page=history ] Bela Ban updated JBCACHE-119: - Fix Version: 1.2.3 (was: 1.2.2) Missing notification for remove() and addChild

[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-54) JBossCacheAop nees a customized interceptor option

[ http://jira.jboss.com/jira/browse/JBCACHE-54?page=history ] Bela Ban reassigned JBCACHE-54: --- Assign To: Ben Wang (was: Bela Ban) JBossCacheAop nees a customized interceptor option -- Key

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-42) White paper on AOP (for session repl)

[ http://jira.jboss.com/jira/browse/JBCACHE-42?page=history ] Bela Ban updated JBCACHE-42: Fix Version: 1.2.4 (was: 1.2.3) White paper on AOP (for session repl) - Key: JBCACHE-42

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-4) UDP.bundling too slow

[ http://jira.jboss.com/jira/browse/JGRP-4?page=history ] Bela Ban updated JGRP-4: Summary: UDP.bundling too slow (was: UDB.bundling too slow) Environment: UDP.bundling too slow - Key: JGRP-4 URL: http

[JBoss-dev] [JBoss JIRA] Updated: (JGRP-36) TCP:PING, TCP transport combined with multicast discovery

[ http://jira.jboss.com/jira/browse/JGRP-36?page=history ] Bela Ban updated JGRP-36: - Fix Version: 2.2.8 (was: 2.2.9) TCP:PING, TCP transport combined with multicast discovery

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-122) Convert JBoss Logger to commons-logging

[ http://jira.jboss.com/jira/browse/JBCACHE-122?page=history ] Bela Ban updated JBCACHE-122: - Fix Version: 1.2.3 Convert JBoss Logger to commons-logging --- Key: JBCACHE-122 URL: http

[JBoss-dev] [JBoss JIRA] Created: (JGRP-48) Add version number of manifest

Add version number of manifest -- Key: JGRP-48 URL: http://jira.jboss.com/jira/browse/JGRP-48 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- This message is automatically generated

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316533 ] Bela Ban commented on JBCACHE-98: - Yes, but I'm talking about 1.2.2 not 1.2.1 Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE

Unnecessary lock acquisition with IsolationLevel.NONE - Key: JBCACHE-117 URL: http://jira.jboss.com/jira/browse/JBCACHE-117 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE

[ http://jira.jboss.com/jira/browse/JBCACHE-117?page=comments#action_12316510 ] Bela Ban commented on JBCACHE-117: -- added test case IsolationLevelNoneTest Unnecessary lock acquisition with IsolationLevel.NONE

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-117) Unnecessary lock acquisition with IsolationLevel.NONE

[ http://jira.jboss.com/jira/browse/JBCACHE-117?page=history ] Bela Ban resolved JBCACHE-117: -- Resolution: Done LockInterceptor.lock() does *not* acquire a lock if isolation level == NONE Unnecessary lock acquisition with IsolationLevel.NONE

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-118) Inefficient CacheLoader.exists() followed by CacheLoader.get()

: Bela Ban Assigned to: Bela Ban Priority: Minor Fix For: 1.2.2 I have a CacheLoader that I am using to allow a TreeCache to act as the primary interface to a DAV/JDBC data model. Each access to the backend can be quite expensive. I note that a CacheLoader.get() is always preceeded

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-118) Inefficient CacheLoader.exists() followed by CacheLoader.get()

[ http://jira.jboss.com/jira/browse/JBCACHE-118?page=history ] Bela Ban updated JBCACHE-118: - Fix Version: 1.2.3 (was: 1.2.2) Inefficient CacheLoader.exists() followed by CacheLoader.get

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-119) Missing notification for remove() and addChild()

Missing notification for remove() and addChild() Key: JBCACHE-119 URL: http://jira.jboss.com/jira/browse/JBCACHE-119 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-119) Missing notification for remove() and addChild()

[ http://jira.jboss.com/jira/browse/JBCACHE-119?page=history ] Bela Ban resolved JBCACHE-119: -- Resolution: Done Testcase is TreeCacheListenerTest Missing notification for remove() and addChild

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316531 ] Bela Ban commented on JBCACHE-98: - Looks like 4.0.2 might be delayed by 1 week, this gives me time to release 1.2.2 and create a thirdparty lib jboss-cache.jar that 4.0.2

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316538 ] Bela Ban commented on JBCACHE-98: - no, it is not: java -jar jboss-cache.jar will reveal the version # Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=history ] Bela Ban updated JBCACHE-98: Attachment: jboss-cache.jar attached JBossCache 1.2.2beta Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-98) Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=comments#action_12316550 ] Bela Ban commented on JBCACHE-98: - done Backporting JBossCache 1.2.2 in JBossAS 4.0.x and 3.2.x releases

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-110) Cache aop Overriding toString or hashCode will trigger stack overflow

[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=history ] Bela Ban updated JBCACHE-110: - Fix Version: 1.2.3 (was: 1.2.2) Cache aop Overriding toString or hashCode will trigger stack overflow

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-103) ConfiguratorFactory#getConfigStream should not throw a AccessControlException

[ http://jira.jboss.com/jira/browse/JBCACHE-103?page=history ] Bela Ban updated JBCACHE-103: - Fix Version: 1.2.3 (was: 1.2.2) ConfiguratorFactory#getConfigStream should not throw a AccessControlException

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-54) JBossCacheAop nees a customized interceptor option

[ http://jira.jboss.com/jira/browse/JBCACHE-54?page=history ] Bela Ban updated JBCACHE-54: Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop nees a customized interceptor option

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-104) Mass Removal

[ http://jira.jboss.com/jira/browse/JBCACHE-104?page=history ] Bela Ban updated JBCACHE-104: - Fix Version: 1.2.3 (was: 1.2.2) Mass Removal Key: JBCACHE-104 URL: http://jira.jboss.com/jira/browse

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-100) RMI-based DelegatingCacheLoader

[ http://jira.jboss.com/jira/browse/JBCACHE-100?page=history ] Bela Ban updated JBCACHE-100: - Fix Version: 1.2.3 (was: 1.2.2) RMI-based DelegatingCacheLoader --- Key: JBCACHE-100 URL

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-85) TreeCacheAop object event listener

[ http://jira.jboss.com/jira/browse/JBCACHE-85?page=history ] Bela Ban updated JBCACHE-85: Fix Version: 1.2.3 (was: 1.2.2) TreeCacheAop object event listener -- Key: JBCACHE-85 URL

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-7) JBossCacheAop benchmark and performance tuning

[ http://jira.jboss.com/jira/browse/JBCACHE-7?page=history ] Bela Ban updated JBCACHE-7: --- Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop benchmark and performance tuning -- Key

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-42) White paper on AOP (for session repl)

[ http://jira.jboss.com/jira/browse/JBCACHE-42?page=history ] Bela Ban updated JBCACHE-42: Fix Version: 1.2.3 (was: 1.2.2) White paper on AOP (for session repl) - Key: JBCACHE-42

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-53) JBossCacheAop can use prepare annotation

[ http://jira.jboss.com/jira/browse/JBCACHE-53?page=history ] Bela Ban updated JBCACHE-53: Fix Version: 1.2.3 (was: 1.2.2) JBossCacheAop can use prepare annotation -- Key: JBCACHE-53

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[ http://jira.jboss.com/jira/browse/JBCACHE-116?page=history ] Bela Ban resolved JBCACHE-116: -- Resolution: Done accepted patch CacheLoaderInterceptor calls CacheLoader.exists() spuriously

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-116) CacheLoaderInterceptor calls CacheLoader.exists() spuriously

Ban Assigned to: Bela Ban Fix For: 1.2.2 -- 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 - If you want more information on JIRA, or have a bug to report

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-3) Expose JGroups (protocols, channel) via JMX, provide common JGroups MBean

[ http://jira.jboss.com/jira/browse/JBCACHE-3?page=history ] Bela Ban resolved JBCACHE-3: Resolution: Duplicate Issue Duplicate of JBCACHE-43 Expose JGroups (protocols, channel) via JMX, provide common JGroups MBean

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes

[ http://jira.jboss.com/jira/browse/JBAS-1579?page=comments#action_12316432 ] Bela Ban commented on JBAS-1579: Fixed all classes in org.jboss.cache package Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes

[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-114) Standalone Build

[ http://jira.jboss.com/jira/browse/JBCACHE-114?page=history ] Bela Ban reassigned JBCACHE-114: Assign To: Bela Ban (was: Ryan Campbell) Standalone Build Key: JBCACHE-114 URL: http://jira.jboss.com/jira/browse

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-115) beforeEviction() callback

beforeEviction() callback - Key: JBCACHE-115 URL: http://jira.jboss.com/jira/browse/JBCACHE-115 Project: JBoss Cache Type: Feature Request Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.3

[JBoss-dev] [JBoss JIRA] Created: (JGRP-47) Support for IPv6

Support for IPv6 Key: JGRP-47 URL: http://jira.jboss.com/jira/browse/JGRP-47 Project: JGroups Type: Feature Request Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.3 Requires changes to IpAddress, maybe Ipv6Address (subclass

[JBoss-dev] [JBoss JIRA] Closed: (JBCACHE-113) ConcurrentModificationException in TransactionTable

[ http://jira.jboss.com/jira/browse/JBCACHE-113?page=history ] Bela Ban closed JBCACHE-113: Resolution: Done This is fixed in 1.2.2 (not yet checked in) ConcurrentModificationException in TransactionTable

[JBoss-dev] [JBoss JIRA] Created: (JGRP-46) RpcDispatcher eats Throwables

RpcDispatcher eats Throwables - Key: JGRP-46 URL: http://jira.jboss.com/jira/browse/JGRP-46 Project: JGroups Type: Bug Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 handle() re-throws Exception, but eats Throwables

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-113) ConcurrentModificationException in TransactionTable

ConcurrentModificationException in TransactionTable --- Key: JBCACHE-113 URL: http://jira.jboss.com/jira/browse/JBCACHE-113 Project: JBoss Cache Type: Bug Versions: 1.2.1 Reporter: Bela Ban Assigned

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-113) ConcurrentModificationException in TransactionTable

[ http://jira.jboss.com/jira/browse/JBCACHE-113?page=history ] Bela Ban resolved JBCACHE-113: -- Resolution: Done Fixed by switching HashMap to ConcurrentReaderHashMap ConcurrentModificationException in TransactionTable

[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-112) Added putFailFast(Fqn, ...)

Added putFailFast(Fqn, ...) --- Key: JBCACHE-112 URL: http://jira.jboss.com/jira/browse/JBCACHE-112 Project: JBoss Cache Type: Feature Request Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.2

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-112) Added putFailFast(Fqn, ...)

[ http://jira.jboss.com/jira/browse/JBCACHE-112?page=history ] Bela Ban resolved JBCACHE-112: -- Resolution: Done Added putFailFast(Fqn, ...) --- Key: JBCACHE-112 URL: http://jira.jboss.com/jira/browse

[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-57) Interfaces for accessing JBossCache

[ http://jira.jboss.com/jira/browse/JBCACHE-57?page=history ] Bela Ban updated JBCACHE-57: Fix Version: 1.3 (was: 1.4) Interfaces for accessing JBossCache --- Key: JBCACHE-57 URL

[JBoss-dev] [JBoss JIRA] Commented: (JBCACHE-106) Override default properties on a method call basis

[ http://jira.jboss.com/jira/browse/JBCACHE-106?page=comments#action_12316092 ] Bela Ban commented on JBCACHE-106: -- Another option: dirty access, acquire no locks at all Override default properties on a method call basis

[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-52) Use ant docbook build for doc generation

[ http://jira.jboss.com/jira/browse/JBCACHE-52?page=history ] Bela Ban resolved JBCACHE-52: - Resolution: Done done by Norman Richards and Michael Yuan Use ant docbook build for doc generation Key

  1   2   3   4   5   >