10:35 a.m.
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: exc.txt
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:35 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech updated JBCACHE-1565:
---------------------------
Attachment: exc.txt
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: exc.txt
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:37 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech updated JBCACHE-1565:
---------------------------
Attachment: JBossCache321Wrapper.java
GetPutTest.java
ConcurrentWritersTest.java
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutTest.java,
JBossCache321Wrapper.java
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:39 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech updated JBCACHE-1565:
---------------------------
Attachment: GetPutCachebenchCluster.xml
mvcc-repl-sync.xml
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:39 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech commented on JBCACHE-1565:
--------------------------------
I've attached files which I've created for the test.
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:53 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
Manik Surtani commented on JBCACHE-1565:
----------------------------------------
Hi there. In addition to this, you may want to take a look at
http://cachebenchfwk.sourceforge.net - the benchmark framework has been moved to its own
project on SourceForge and has been heavily modernized (including using Maven to build,
which makes updating versions of products trivial). The framework itself is much more
robust too, so despite the current "Alpha" tag on the project page, we use it
extensively to benchmark JBoss Cache and Infinispan.
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
12:08 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech commented on JBCACHE-1565:
--------------------------------
I had a short look on new project - I don't see there that
cache.getInvocationContext().getOptionOverrides().setForceWriteLock(true) is tested there.
Feel free to use my tests in any way - it would be good to have it them out of the box in
the framework.
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Manik Surtani
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
12:31 p.m.
New subject: [JBoss JIRA] Assigned: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
Manik Surtani reassigned JBCACHE-1565:
--------------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
May be a useful configuration option, if supported by the cache product, to have this
switched on in the wrapper. I wouldn't put it on the wrapper interface though since
that forces impls that do not support such a feature to somehow implement it.
Mircea, do you want to port this issue to the new cache bench fwk's TRAC issue
tracker?
Thanks
Manik
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Mircea Markus
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
1:37 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
tbech commented on JBCACHE-1565:
--------------------------------
Btw, it is already done in this way for startTransaction and endTransaction, where for
Ehcache there is simply exception 'notsupported' thrown.
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Mircea Markus
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
2:33 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
Brett Cave commented on JBCACHE-1565:
-------------------------------------
the same exception occurs when using pojocache (3.0, core 3.1 "casabel") that is
distributed with JBoss AS5.
* Pojocache configured via JMX (pojocache-service.xml) with JBossTransactionManagerLookup
class and REPL_SYNC (other variations not tested).
* Retrieve reference to PojoCache via the JmxWrapper, and attach a pojo to the cache.
The exception occurs.
Disabling the transactionmanager on the cache results in a different exception:
Caused by: com.test.system.exception.MyPojoCacheException: Error writing to pojo cache:
/cache/9ec2c1bb-e37f-4592-9348-953dc164ed04
at
com.test.system.session.PojoCacheManagerBean.writeToCache(PojoCacheManagerBean.java:42)
....
Caused by: org.jboss.cache.pojo.PojoCacheException: attach failed
/cache/9ec2c1bb-e37f-4592-9348-953dc164ed04
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:111)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:88)
at
com.test.system.session.PojoCacheManagerBean.writeToCache(PojoCacheManagerBean.java:39)
... 246 more
Caused by: org.jboss.cache.CacheException: java.io.EOFException
at
org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:304)
at
org.jboss.cache.invocation.CacheInvocationDelegate.invokePut(CacheInvocationDelegate.java:705)
at
org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:519)
at org.jboss.cache.pojo.impl.InternalHelper.put(InternalHelper.java:110)
at
org.jboss.cache.pojo.impl.SerializableObjectHandler.putIntoCache(SerializableObjectHandler.java:86)
at
org.jboss.cache.pojo.impl.SerializableObjectHandler.put(SerializableObjectHandler.java:71)
at
org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:138)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
... 249 more
Caused by: java.io.EOFException
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Mircea Markus
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
10:43 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1565) Locking doesn't work when replication is used
[
https://jira.jboss.org/jira/browse/JBCACHE-1565?page=com.atlassian.jira.p...
]
Lillian Andres commented on JBCACHE-1565:
-----------------------------------------
Our team is also experiencing the same problem when we have the unfortunate case of
multiple writers on the same exact pojo object. A partial stack dump follows.
Unfortunately, the problem is a show stopper for us. Is there any workaround?
1. Can we use the a different locking scheme besides MVCC?
2. Can we catch the timeout exception and totally remove the node and re- add it? Is
there a way where we can via software program release the lock?
Thank you for your help.
Caused by: org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/testcache/Test] after [60000] milliseconds for requestor
[GlobalTransaction:<127.0.0.0:2103>:294]! Lock held by
[GlobalTransaction:<127.0.0.0:2103>:274]
at
org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:170)
at
org.jboss.cache.mvcc.MVCCNodeHelper.wrapNodeForWriting(MVCCNodeHelper.java:226)
at
org.jboss.cache.interceptors.MVCCLockingInterceptor.handlePutKeyValueCommand(MVCCLockingInterceptor.java:98)
at
org.jboss.cache.interceptors.base.PrePostProcessingCommandInterceptor.visitPutKeyValueCommand(PrePostProcessingCommandInterceptor.java:88)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at
org.jboss.cache.interceptors.ReplicationInterceptor.handleCrudMethod(ReplicationInterceptor.java:150)
at
org.jboss.cache.interceptors.ReplicationInterceptor.visitPutKeyValueCommand(ReplicationInterceptor.java:107)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at
org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:131)
at
org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at
org.jboss.cache.interceptors.TxInterceptor.attachGtxAndPassUpChain(TxInterceptor.java:284)
at
org.jboss.cache.interceptors.TxInterceptor.handleDefault(TxInterceptor.java:271)
at
org.jboss.cache.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:65)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at
org.jboss.cache.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:119)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
at
org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:178)
at
org.jboss.cache.interceptors.InvocationContextInterceptor.visitPutKeyValueCommand(InvocationContextInterceptor.java:82)
at
org.jboss.cache.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:100)
at
org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:265)
at
org.jboss.cache.invocation.CacheInvocationDelegate.put(CacheInvocationDelegate.java:560)
at
org.jboss.cache.pojo.impl.InternalHelper.lockPojo(InternalHelper.java:342)
at
org.jboss.cache.pojo.impl.PojoCacheDelegate.putObject(PojoCacheDelegate.java:101)
at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:102)
... 43 more
Locking doesn't work when replication is used
---------------------------------------------
Key: JBCACHE-1565
URL: https://jira.jboss.org/jira/browse/JBCACHE-1565
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.1.GA
Environment: Linux, Sun Java 5.0
Reporter: tbech
Assignee: Mircea Markus
Priority: Critical
Attachments: ConcurrentWritersTest.java, exc.txt, GetPutCachebenchCluster.xml,
GetPutTest.java, JBossCache321Wrapper.java, mvcc-repl-sync.xml
During performance tests of JBossCache, I've tried to test transactions with
cache.getInvocationContext().getOptionOverrides().setForceWriteLock operation
('select-for-update'). I've used standard jbosscache benchmark from svn.
I've created new product jbosscache3.2.1 based on 3.1.0 and new test. Basicaly it
did:
try
{
long startTime = System.nanoTime();
if (concurrentWrites) {
cacheWrapper.startTransaction();
cacheWrapper.setForceWriteLock(true);
}
ObjectInCache o = (ObjectInCache) cacheWrapper.get(path, key);
o = new ObjectInCache(Integer.valueOf(o.getVal().intValue() + 1),
randStr[taskNumber%randStr.length]);
cacheWrapper.put(path, key, o);
if (concurrentWrites) {
cacheWrapper.endTransaction(true);
}
long statValue = (System.nanoTime() - startTime);
descriptiveStatistics.addValue(statValue);
}
catch (Throwable e)
{
log.error("Error appeared whilst writing to cache:" +
e.getMessage(), e);
try {
if (concurrentWrites) {
cacheWrapper.endTransaction(false);
}
} finally {
}
} finally {
logRunCount(taskNumber);
}
concurrentWrites was set to true.
This tests passes nicely in one node (local mode). However in 2,3,4 nodes it fails after
first usage of the same object by different node with exception:
org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn
[/concurrent/Intermediate-0/Node 0] after [240000] milliseconds for requestor
[GlobalTransaction:<10.118.236.212:40325>:0]! Lock held by
[GlobalTransaction:<10.118.236.211:8112>:40]
at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:159)
It looks like, in replication the node is not beeing releases after transaction commit.
--
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
5136
days inactive
5219
days old
jbosscache-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Brett Cave (JIRA) -
Lillian Andres (JIRA)
-
Manik Surtani (JIRA)
-
tbech (JIRA)