[ http://jira.jboss.com/jira/browse/JBCACHE-111?page=history ]
Bela Ban resolved JBCACHE-111:
--
Resolution: Done
fixed according to solution
> Transaction not available in afterCompletion() of CacheStoreInterceptor
> ---
[
http://jira.jboss.com/jira/browse/JBCACHE-111?page=comments#action_12316073 ]
Bela Ban commented on JBCACHE-111:
--
Original posting:
What might be the reason for receiving the following exception?
java.lang.Exception: entry for transaction :2 not fou
Transaction not available in afterCompletion() of CacheStoreInterceptor
---
Key: JBCACHE-111
URL: http://jira.jboss.com/jira/browse/JBCACHE-111
Project: JBoss Cache
Type: Bug
Versions: 1.2
[ http://jira.jboss.com/jira/browse/JBAS-1561?page=history ]
Bela Ban reassigned JBAS-1561:
--
Assign To: Bela Ban
> Fix for Hibernate/JBossCache integration
>
>
> Key: JBAS-1561
> URL: http://jira.jb
Fix for Hibernate/JBossCache integration
Key: JBAS-1561
URL: http://jira.jboss.com/jira/browse/JBAS-1561
Project: JBoss Application Server
Type: Bug
Components: Hibernate service, JBoss Cache service
Reporter: Bela Ban
[ http://jira.jboss.com/jira/browse/JBCACHE-93?page=history ]
Bela Ban resolved JBCACHE-93:
-
Resolution: Done
attached configs which make for flat memory
> Memory problem at repeated remote PUT
> -
>
> Key:
[
http://jira.jboss.com/jira/browse/JBCACHE-93?page=comments#action_12316025 ]
Bela Ban commented on JBCACHE-93:
-
Needed to change properties of JGroups, use either tcp.xml or fc-fast.xml to
get high sustained throughput.
Mem is flat with either of the
[ http://jira.jboss.com/jira/browse/JBCACHE-93?page=history ]
Bela Ban updated JBCACHE-93:
Attachment: tcp.xml
fc-fast.xml
> Memory problem at repeated remote PUT
> -
>
> Key: JBCACHE-93
>
[ http://jira.jboss.com/jira/browse/JBCACHE-94?page=history ]
Bela Ban resolved JBCACHE-94:
-
Resolution: Done
CreateIfNotExistsInterceptor is currently not used, code for creation is in
LockInterceptor.
Will be externalized into LockTable in 1.3 (JBCACH
[ http://jira.jboss.com/jira/browse/JBCACHE-97?page=history ]
Bela Ban updated JBCACHE-97:
Fix Version: 1.3
(was: 1.2.1)
> ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer
> waiting to upgrade lock
> ---
[ http://jira.jboss.com/jira/browse/JBCACHE-51?page=history ]
Bela Ban updated JBCACHE-51:
Fix Version: 1.2.2
(was: 1.3)
> Create standalone CVS version of JBossCache
> ---
>
> Key: JBCACH
Use context classloader or classloader of current class
---
Key: JBCACHE-109
URL: http://jira.jboss.com/jira/browse/JBCACHE-109
Project: JBoss Cache
Type: Task
Reporter: Bela Ban
Assigned to: Bela Ban
Fix
Make CacheLoader use interface rather than TreeCache implementation
---
Key: JBCACHE-108
URL: http://jira.jboss.com/jira/browse/JBCACHE-108
Project: JBoss Cache
Type: Sub-task
Reporter: Bela Ban
Ass
[
http://jira.jboss.com/jira/browse/JBCACHE-94?page=comments#action_12315987 ]
Bela Ban commented on JBCACHE-94:
-
T0 is under tx to do removeObject("/aop", ...) of which has many sub-cache
operations. But first thing, it does a write on, say, /aop. The
[ http://jira.jboss.com/jira/browse/JBCACHE-94?page=history ]
Bela Ban reopened JBCACHE-94:
-
The following append details a case in which this still fails
> Incorrect synchronization between threads (CreateIfNotExistsInterceptor and
> LockInterceptor)
> -
Extract locks from TreeCache into LockingTable
--
Key: JBCACHE-107
URL: http://jira.jboss.com/jira/browse/JBCACHE-107
Project: JBoss Cache
Type: Feature Request
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1
[ http://jira.jboss.com/jira/browse/JBCACHE-103?page=history ]
Bela Ban updated JBCACHE-103:
-
Fix Version: 1.2.2
(was: 1.2.1)
> ConfiguratorFactory#getConfigStream should not throw a AccessControlException
> -
Override default properties on a method call basis
--
Key: JBCACHE-106
URL: http://jira.jboss.com/jira/browse/JBCACHE-106
Project: JBoss Cache
Type: Feature Request
Versions: 1.2.1
Reporter: Bela Ban
Assign
[ http://jira.jboss.com/jira/browse/JGRP-33?page=comments#action_12315959 ]
Bela Ban commented on JGRP-33:
--
It discards all messages sent by myself. Let's not use JIRA for questions;
let's use the
jgroups dev list in the future
> JGroups throws OutOfMemor
[ http://jira.jboss.com/jira/browse/JGRP-33?page=comments#action_12315957 ]
Bela Ban commented on JGRP-33:
--
You either need to call receive() (and discard the msg), or set Channel.LOCAL
to false.
> JGroups throws OutOfMemoryError after running for a few h
[ http://jira.jboss.com/jira/browse/JBCACHE-105?page=history ]
Bela Ban resolved JBCACHE-105:
--
Assign To: Amit Bansal (was: Bela Ban)
Resolution: Rejected
The doc is more than sufficient
> Please make the proper configuration document of BOSS Ca
[ http://jira.jboss.com/jira/browse/JBCACHE-104?page=history ]
Bela Ban updated JBCACHE-104:
-
Assign To: Ben Wang (was: Bela Ban)
Version: 1.2
Fix Version: 1.2.2
> Mass Removal
>
>
> Key: JBCACHE-104
> URL: http:
[ http://jira.jboss.com/jira/browse/JBCACHE-103?page=history ]
Bela Ban updated JBCACHE-103:
-
Fix Version: 1.2.1
> ConfiguratorFactory#getConfigStream should not throw a AccessControlException
> ---
[ http://jira.jboss.com/jira/browse/JBCACHE-36?page=history ]
Bela Ban resolved JBCACHE-36:
-
Resolution: Done
all tests except TxDeadlockUnitTest (as expected) pass
> Run testsuite on multi-CPU boxes in ATL lab
> ---
[ http://jira.jboss.com/jira/browse/JGRP-44?page=history ]
Bela Ban updated JGRP-44:
-
Version: (was: 2.2.8)
Fix Version: 2.2.8
> RpcDispatcher hangs waiting for response from dead members
> --
>
JGroups-based DelegatingCacheLoader
---
Key: JBCACHE-101
URL: http://jira.jboss.com/jira/browse/JBCACHE-101
Project: JBoss Cache
Type: Feature Request
Versions: 1.2
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1
[ http://jira.jboss.com/jira/browse/JBCACHE-96?page=history ]
Bela Ban resolved JBCACHE-96:
-
Resolution: Done
applied patch, thanks
> Memory leak in FileCacheLoader
> --
>
> Key: JBCACHE-96
> URL: http://ji
[ http://jira.jboss.com/jira/browse/JBCACHE-99?page=history ]
Bela Ban resolved JBCACHE-99:
-
Resolution: Done
> FileCacheLoader uses incorrect classloader
> --
>
> Key: JBCACHE-99
> URL: http://j
[ http://jira.jboss.com/jira/browse/JBCACHE-101?page=history ]
Bela Ban resolved JBCACHE-101:
--
Resolution: Done
done, added (RpcDelegatingCacheLoader)
> JGroups-based DelegatingCacheLoader
> ---
>
> Key: JBCACH
RMI-based DelegatingCacheLoader
---
Key: JBCACHE-100
URL: http://jira.jboss.com/jira/browse/JBCACHE-100
Project: JBoss Cache
Type: Feature Request
Versions: 1.2
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1.2.2
[ http://jira.jboss.com/jira/browse/JBCACHE-99?page=history ]
Bela Ban updated JBCACHE-99:
Fix Version: 1.2.1
done, thanks
> FileCacheLoader uses incorrect classloader
> --
>
> Key: JBCACHE-99
> URL:
[
http://jira.jboss.com/jira/browse/JBCACHE-93?page=comments#action_12315763 ]
Bela Ban commented on JBCACHE-93:
-
Doesn't compile, you have some HM specific classes. Please modify your code and
resubmit it.
Thanks,
> Memory problem at repeated remote
[ http://jira.jboss.com/jira/browse/JBCACHE-94?page=history ]
Bela Ban resolved JBCACHE-94:
-
Resolution: Done
Involved changing synchronization of put() and evict()/remove() methods in
CreateIfNotExistsInterceptor
> Incorrect synchronization between t
ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer
waiting to upgrade lock
-
Key: JBCACHE-97
URL: http://jira.jboss.com/jira/browse/JBCACHE-97
Project: JBo
[ http://jira.jboss.com/jira/browse/JBAS-1482?page=history ]
Bela Ban reassigned JBAS-1482:
--
Assign To: Ovidiu Feodorov (was: Bela Ban)
Deadlock between ReplicantManager and HASingleton. HASingleton blocks in a
callback.
Ovidiu: didn't you change this som
[ http://jira.jboss.com/jira/browse/JBCACHE-96?page=history ]
Bela Ban updated JBCACHE-96:
Attachment: FileCacheLoader.java
> Memory leak in FileCacheLoader
> --
>
> Key: JBCACHE-96
> URL: http://jira.jboss.com/j
Memory leak in FileCacheLoader
--
Key: JBCACHE-96
URL: http://jira.jboss.com/jira/browse/JBCACHE-96
Project: JBoss Cache
Type: Bug
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1.2.1
Attachments: FileCacheLoader.java
Ther
[
http://jira.jboss.com/jira/browse/JBCACHE-89?page=comments#action_12315646 ]
Bela Ban commented on JBCACHE-89:
-
You can do this even now, albeit programmatically. You get the interceptor
list, just modify it.
> Allow Specifying Custom Interceptors i
[ http://jira.jboss.com/jira/browse/JGRP-31?page=comments#action_12315624 ]
Bela Ban commented on JGRP-31:
--
This is configurable (you can switch it off via a property). I'd use the file
system and temp storage.
> Problem with MERGE2 when not using multica
[ http://jira.jboss.com/jira/browse/JBCACHE-95?page=history ]
Bela Ban resolved JBCACHE-95:
-
Resolution: Done
fixed
> Class cast exception in TreeCacheView2
> --
>
> Key: JBCACHE-95
> URL: http://ji
[ http://jira.jboss.com/jira/browse/JBCACHE-95?page=history ]
Bela Ban updated JBCACHE-95:
Original Estimate: 300
Remaining Estimate: 300
Fix Version: 1.2.1
> Class cast exception in TreeCacheView2
> --
>
>
Incorrect synchronization between threads (CreateIfNotExistsInterceptor and
LockInterceptor)
Key: JBCACHE-94
URL: http://jira.jboss.com/jira/browse/JBCACHE-94
Project: JBoss Cache
[ http://jira.jboss.com/jira/browse/JGRP-31?page=comments#action_12315542 ]
Bela Ban commented on JGRP-31:
--
In this case, the timeout for purging of idle members in the persistent cache
should be higher than the longest anticipated network partition.
We c
[ http://jira.jboss.com/jira/browse/JGRP-38?page=history ]
Bela Ban resolved JGRP-38:
--
Resolution: Done
> Deprecate DistributedTree,ReplicatedTree,DistrHashtable,ReplHashtable
> -
>
>
Use persistent storage to store results of initial discovery
Key: JGRP-43
URL: http://jira.jboss.com/jira/browse/JGRP-43
Project: JGroups
Type: Feature Request
Reporter: Bela Ban
Assigned to: Bela Ban
[ http://jira.jboss.com/jira/browse/JGRP-31?page=comments#action_12315540 ]
Bela Ban commented on JGRP-31:
--
I actually had in mind to use a little temp persistence store which would store
the approximate membership (including mnop). Elements here would sim
[ http://jira.jboss.com/jira/browse/JBCACHE-93?page=history ]
Bela Ban updated JBCACHE-93:
Fix Version: 1.2.1
If this is a real bug, we will hold the 1.2.1 release until this has been fixed
> Memory problem at repeated remote PUT
> -
[
http://jira.jboss.com/jira/browse/JBCACHE-91?page=comments#action_12315517 ]
Bela Ban commented on JBCACHE-91:
-
Works for me. How did they set the isolation level ?
I can't seem to reply on the java.net forum, even though I'm logged in.
Can they atta
[ http://jira.jboss.com/jira/browse/JGRP-39?page=comments#action_12315514 ]
Bela Ban commented on JGRP-39:
--
does that occur with FD_SOCK as well ?
> A TCP stack does not correctly detect failure (pulled cable) for certain
> TCPPING configurations
> --
Hierarchical message dissemination
--
Key: JGRP-41
URL: http://jira.jboss.com/jira/browse/JGRP-41
Project: JGroups
Type: Feature Request
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 2.2.9
Scheme proposed by EPFL
--
[ http://jira.jboss.com/jira/browse/JGRP-39?page=history ]
Bela Ban reassigned JGRP-39:
Assign To: Ovidiu Feodorov (was: Bela Ban)
> A TCP stack does not correctly detect failure (pulled cable) for certain
> TCPPING configurations
> ---
[ http://jira.jboss.com/jira/browse/JGRP-40?page=history ]
Bela Ban updated JGRP-40:
-
Fix Version: 2.2.8
> Connections remain open even after the channel port changes, while using TCP
>
[ http://jira.jboss.com/jira/browse/JGRP-39?page=history ]
Bela Ban updated JGRP-39:
-
Fix Version: 2.2.8
> A TCP stack does not correctly detect failure (pulled cable) for certain
> TCPPING configurations
> --
[
http://jira.jboss.com/jira/browse/JBCACHE-86?page=comments#action_12315511 ]
Bela Ban commented on JBCACHE-86:
-
yes
> invalidate() across cluster
> ---
>
> Key: JBCACHE-86
> URL: http://jira.jboss.com/jira/br
Deprecate DistributedTree,ReplicatedTree,DistrHashtable,ReplHashtable
-
Key: JGRP-38
URL: http://jira.jboss.com/jira/browse/JGRP-38
Project: JGroups
Type: Task
Reporter: Bela Ban
Assigned to: Be
TCP should generate a SUSPECT event when connection is closed
-
Key: JGRP-37
URL: http://jira.jboss.com/jira/browse/JGRP-37
Project: JGroups
Type: Feature Request
Reporter: Bela Ban
Assigned to: Bela Ba
[
http://jira.jboss.com/jira/browse/JBCACHE-92?page=comments#action_12315486 ]
Bela Ban commented on JBCACHE-92:
-
1. Are there any plans in the roadmap to support the kind of forceful eviction
policy I need in JBoss Cache?
2. Are there any side effects
[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=history ]
Bela Ban updated JBCACHE-89:
Fix Version: 1.3
This feature is planned. Currently, one has to add their interceptor(s)
dynamically using the getInterceptors() method
> Allow Specifying Custom Int
[
http://jira.jboss.com/jira/browse/JBCACHE-86?page=comments#action_12315484 ]
Bela Ban commented on JBCACHE-86:
-
There is a nodeEvicted(Fqn) callback
> invalidate() across cluster
> ---
>
> Key: JBCACHE-86
> U
[ http://jira.jboss.com/jira/browse/JBCACHE-88?page=history ]
Bela Ban updated JBCACHE-88:
Fix Version: 1.3
> Add RemoteDelegatingCacheLoader
> ---
>
> Key: JBCACHE-88
> URL: http://jira.jboss.com/jira/browse/JBC
TCP:PING, TCP transport combined with multicast discovery
-
Key: JGRP-36
URL: http://jira.jboss.com/jira/browse/JGRP-36
Project: JGroups
Type: Feature Request
Reporter: Bela Ban
Assigned to: Bela Ban
[
http://jira.jboss.com/jira/browse/JBAS-1481?page=comments#action_12315483 ]
Bela Ban commented on JBAS-1481:
Here's the class that notifies listeners of view changes (in HAPartitionImpl):
private class AsynchViewChangeHandler implements Runnable
HAPartitionImpl.viewAccepted()
--
Key: JBAS-1481
URL: http://jira.jboss.com/jira/browse/JBAS-1481
Project: JBoss Application Server
Type: Bug
Components: Clustering
Reporter: Bela Ban
Here's the end of the method:
// Put the vie
[
http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315474 ]
Bela Ban commented on JBAS-1476:
// 1) At cluster formation (first node in cluster), create a cluster instance
GUID
Yes
// 2) At cluster join (second+ node in cluster) get
[
http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315473 ]
Bela Ban commented on JBAS-1476:
// 1) Is this the correct solution
I would suggest to also include a timestamp, generated on the server side.
So we have timestamp, versionId
Provide optimized JGroups config for Clustering as default
--
Key: JBAS-1475
URL: http://jira.jboss.com/jira/browse/JBAS-1475
Project: JBoss Application Server
Type: Task
Components: Clustering
Reporter:
[ http://jira.jboss.com/jira/browse/JBCACHE-86?page=history ]
Bela Ban updated JBCACHE-86:
Fix Version: 1.3
(was: 1.2.1)
> invalidate() across cluster
> ---
>
> Key: JBCACHE-86
> URL: http://jira
[ http://jira.jboss.com/jira/browse/JBCACHE-91?page=history ]
Bela Ban updated JBCACHE-91:
Fix Version: 1.2.1
> TX Isolation always REPEATABLE_READ
> ---
>
> Key: JBCACHE-91
> URL: http://jira.jboss.com/jira/
[ http://jira.jboss.com/jira/browse/JGRP-34?page=history ]
Bela Ban updated JGRP-34:
-
Fix Version: 2.2.8
> NPE when using bootstrap or system class loader
> ---
>
> Key: JGRP-34
> URL: http://jira.jbo
NPE when using bootstrap or system class loader
---
Key: JGRP-35
URL: http://jira.jboss.com/jira/browse/JGRP-35
Project: JGroups
Type: Bug
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 2.2.8
Some classes a
Eviction of entire subtrees
---
Key: JBCACHE-92
URL: http://jira.jboss.com/jira/browse/JBCACHE-92
Project: JBoss Cache
Type: Feature Request
Versions: 1.2
Reporter: Bela Ban
Assigned to: Ben Wang
Fix For: 1.3
--
This me
[ http://jira.jboss.com/jira/browse/JGRP-35?page=history ]
Bela Ban closed JGRP-35:
Resolution: Duplicate Issue
duplicate of 34
> NPE when using bootstrap or system class loader
> ---
>
> Key: JGRP-35
>
invalidate() across cluster
---
Key: JBCACHE-86
URL: http://jira.jboss.com/jira/browse/JBCACHE-86
Project: JBoss Cache
Type: Feature Request
Versions: 1.2
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1.2.1
--
This
[ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]
Bela Ban updated JGRP-33:
-
Fix Version: 2.2.8
> JGroups throws OutOfMemoryError after running for a few hours
> -
>
> Key: JGRP-33
>
[ http://jira.jboss.com/jira/browse/JGRP-27?page=history ]
Bela Ban updated JGRP-27:
-
Fix Version: 2.2.8
(was: 2.2.9)
> UNICAST: use cases that test window_size and min_threshold
> --
>
UnicastTest too slow
Key: JGRP-32
URL: http://jira.jboss.com/jira/browse/JGRP-32
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 thin
[ http://jira.jboss.com/jira/browse/JGRP-31?page=history ]
Bela Ban updated JGRP-31:
-
Fix Version: 2.2.8
(was: 2.2.9)
> Problem with MERGE2 when not using multicast
>
>
> Key: JGRP-31
>
[ http://jira.jboss.com/jira/browse/JBAS-1381?page=history ]
Bela Ban updated JBAS-1381:
---
Assign To: Ben Wang (was: Bela Ban)
> Clustering with CrossContext Enabled generates exception
>
>
> Ke
[ http://jira.jboss.com/jira/browse/JGRP-31?page=history ]
Bela Ban updated JGRP-31:
-
Fix Version: 2.2.9
> Problem with MERGE2 when not using multicast
>
>
> Key: JGRP-31
> URL: http://jira.jboss.com
Check whether the same bug exists in TCP:TCPPING
Key: JGRP-30
URL: http://jira.jboss.com/jira/browse/JGRP-30
Project: JGroups
Type: Sub-task
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 2.2.8
Does TCP
[ http://jira.jboss.com/jira/browse/JGRP-29?page=history ]
Bela Ban updated JGRP-29:
-
Priority: Major (was: Critical)
Version: (was: 2.2.8)
Fix Version: 2.2.8
downgraded to major b/c nobody uses the UDP:TCPPING combo
> Messages are not sent
[ http://jira.jboss.com/jira/browse/JGRP-30?page=history ]
Bela Ban resolved JGRP-30:
--
Resolution: Done
Bug doesn't exist
> Check whether the same bug exists in TCP:TCPPING
>
>
> Key: JGRP-30
>
[ http://jira.jboss.com/jira/browse/JGRP-29?page=history ]
Bela Ban resolved JGRP-29:
--
Resolution: Done
Fixed
> Messages are not sent to all members when using UDP with ip_mcast disabled
> --
UNICAST: use cases that test window_size and min_threshold
--
Key: JGRP-27
URL: http://jira.jboss.com/jira/browse/JGRP-27
Project: JGroups
Type: Task
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For:
[
http://jira.jboss.com/jira/browse/JBCACHE-31?page=comments#action_12314983 ]
Bela Ban commented on JBCACHE-31:
-
Okay, since I'm not able to reproduce it on JDK 1.5, I'm going to re-open it,
but under the JBossCache 1.3 release. I don't have time to t
unable to call getKeys using JNDI
-
Key: JBCACHE-84
URL: http://jira.jboss.com/jira/browse/JBCACHE-84
Project: JBoss Cache
Type: Bug
Versions: 1.2
Reporter: Bela Ban
Assigned to: Bela Ban
Priority: Minor
Fix For:
[ http://jira.jboss.com/jira/browse/JBCACHE-84?page=history ]
Bela Ban resolved JBCACHE-84:
-
Resolution: Done
fixed in 1.2.1
> unable to call getKeys using JNDI
> -
>
> Key: JBCACHE-84
> URL: http://jir
[ http://jira.jboss.com/jira/browse/JBCACHE-31?page=history ]
Bela Ban reopened JBCACHE-31:
-
re-opened, but downgraded to major, as testing under JDK 1.5 reveals mo problems
> Out of memory problem
> -
>
> Key: JBCACHE-31
>
[ http://jira.jboss.com/jira/browse/JGRP-28?page=comments#action_12315012 ]
Bela Ban commented on JGRP-28:
--
[Lez Haslewoord]
We don't want to use the bind.address property, as it sets that value for the
entire VM and all components that reference it (i.e.
Remove sendDummyPacket() in UDP
---
Key: JGRP-28
URL: http://jira.jboss.com/jira/browse/JGRP-28
Project: JGroups
Type: Task
Reporter: Bela Ban
Assigned to: Bela Ban
Priority: Minor
Fix For: 2.2.8
--
This message is auto
[ http://jira.jboss.com/jira/browse/JBCACHE-69?page=history ]
Bela Ban updated JBCACHE-69:
Fix Version: 1.3
(was: 1.5)
> Optimistic Locking
> --
>
> Key: JBCACHE-69
> URL: http://jira.jboss.com/jira/brow
[
http://jira.jboss.com/jira/browse/JBCACHE-31?page=comments#action_12314976 ]
Bela Ban commented on JBCACHE-31:
-
What JDK ? SUN 1.4.2_05 ?
Can you try on 1.5
> Out of memory problem
> -
>
> Key: JBCACHE-31
> URL:
[ http://jira.jboss.com/jira/browse/JBCACHE-31?page=history ]
Bela Ban updated JBCACHE-31:
Fix Version: 1.3
(was: 1.2.1)
> Out of memory problem
> -
>
> Key: JBCACHE-31
> URL: http://jira.jboss.com/j
[
http://jira.jboss.com/jira/browse/JBAS-1273?page=comments#action_12314924 ]
Bela Ban commented on JBAS-1273:
The error message you saw was definitely not causing any problems, and no
erroneous behavior. Has been fixed (a.k.a. 'removed') in 1.2.1.
Th
[
http://jira.jboss.com/jira/browse/JBCACHE-31?page=comments#action_12314904 ]
Bela Ban commented on JBCACHE-31:
-
I'm now 45 mins into the tests, and the numbers don't move at all.
I'm going to close this issue. Please feel free to re-open if you can s
[ http://jira.jboss.com/jira/browse/JBAS-1273?page=history ]
Bela Ban resolved JBAS-1273:
Resolution: Done
fixed in JBossCache 1.2.1
> Clustering Error: UnsupportedOperationException
> ---
>
> Key: J
[
http://jira.jboss.com/jira/browse/JBCACHE-31?page=comments#action_12314903 ]
Bela Ban commented on JBCACHE-31:
-
Tried on JDK 5 with 5 different CacheMemTest processes (arg is 1-5).
After 15 minutes of running, heap is unchanged at ca 1.8MB and non-hea
[ http://jira.jboss.com/jira/browse/JBCACHE-83?page=history ]
Bela Ban updated JBCACHE-83:
Original Estimate: 28800
Remaining Estimate: 28800
Fix Version: 1.2.1
> java.lang.IllegalStateException: addWriter(): owner already existed
> -
[ http://jira.jboss.com/jira/browse/JBCACHE-39?page=history ]
Bela Ban resolved JBCACHE-39:
-
Resolution: Done
> Correct restart of JBossCache (inside JBoss)
>
>
> Key: JBCACHE-39
> URL: http
[ http://jira.jboss.com/jira/browse/JBCACHE-31?page=history ]
Bela Ban resolved JBCACHE-31:
-
Resolution: Cannot Reproduce Bug
See comments
> Out of memory problem
> -
>
> Key: JBCACHE-31
> URL: http://jira.jboss.co
101 - 200 of 398 matches
Mail list logo