[JBoss JIRA] (ISPN-2550) NoSuchElementException in Hot Rod Encoder
by Michal Linhard (JIRA)
Michal Linhard created ISPN-2550:
------------------------------------
Summary: NoSuchElementException in Hot Rod Encoder
Key: ISPN-2550
URL: https://issues.jboss.org/browse/ISPN-2550
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.2.0.Beta4
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Tomas noticed this a while ago in a specific functional test:
https://bugzilla.redhat.com/show_bug.cgi?id=875151
I'm creating a more general JIRA, cause I'm having this in resilience test.
What I found by quick debug, is that here:
https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/ma...
{code}
for (segmentIdx <- 0 until numSegments) {
val denormalizedSegmentHashIds = allDenormalizedHashIds(segmentIdx)
val segmentOwners = ch.locateOwnersForSegment(segmentIdx)
for (ownerIdx <- 0 until segmentOwners.length) {
val address = segmentOwners(ownerIdx % segmentOwners.size)
val serverAddress = members(address)
val hashId = denormalizedSegmentHashIds(ownerIdx)
log.tracef("Writing hash id %d for %s:%s", hashId, serverAddress.host, serverAddress.port)
writeString(serverAddress.host, buf)
writeUnsignedShort(serverAddress.port, buf)
buf.writeInt(hashId)
}
}
{code}
we're trying to obtain serverAddress for nonexistent address and NoSuchElementException is not handled properly.
It hapens after I kill a node in a resilience test and the exception appears when querying for the node in the members cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-2592) Add description resource for cache store stores metric
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-2592:
-------------------------------------
Summary: Add description resource for cache store stores metric
Key: ISPN-2592
URL: https://issues.jboss.org/browse/ISPN-2592
Project: Infinispan
Issue Type: Bug
Components: Server
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
The server-side metrics descriptors fail to load a key
14:44:59,931 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 1) JBAS014612: Operation ("read-resource") failed - address: ([
{"subsystem" => "infinispan"},
{"cache-container" => "clustered"},
{"distributed-cache" => "default"}
]): java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key infinispan.distributed-cache.cache-loader-stores
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-2588) Lock leak during state transfer (causing StaleLocksTransactionTest to fail)
by Mircea Markus (JIRA)
Mircea Markus created ISPN-2588:
-----------------------------------
Summary: Lock leak during state transfer (causing StaleLocksTransactionTest to fail)
Key: ISPN-2588
URL: https://issues.jboss.org/browse/ISPN-2588
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.2.0.Beta5
Reporter: Mircea Markus
Assignee: Dan Berindei
Fix For: 5.2.0.Beta6
numOwners=1, pessimistic cache (same applies if A is the only node in cluster)
1. tx1 running on A with writes on k, lockOwner(k) == {A}
2. A.tx1.lock(k), this doesn't go remotely, and control returns in the InterceptorStack
3. at this point B is started and lockOwner(k) == {B}
4. the StateTransferInterceptor forwards the command to B which acquires the lock locally
5. this is followed by a tx.commit/rollback that would not send the message to B. The logic which determines whether the message to be sent remotely or not is in DistributionInterceptor.visitCommitCommand, which invokes:
{code:java}
protected boolean shouldInvokeRemoteTxCommand(TxInvocationContext ctx) {
return ctx.isOriginLocal() && (ctx.hasModifications() ||
!((LocalTxInvocationContext) ctx).getRemoteLocksAcquired().isEmpty());
}
{code}
The problem here is that, when forwarding, we don't register the remote node as a locked.I think a more generic solution would also work, e.g. if the viewId of the tx is different from the viewId of the cluster at commit time, always go remotely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-2576) API documentation navigation bar is broken
by Dan Berindei (JIRA)
Dan Berindei created ISPN-2576:
----------------------------------
Summary: API documentation navigation bar is broken
Key: ISPN-2576
URL: https://issues.jboss.org/browse/ISPN-2576
Project: Infinispan
Issue Type: Bug
Components: Build process
Affects Versions: 5.2.0.Beta5
Reporter: Dan Berindei
Assignee: Mircea Markus
Fix For: 5.2.0.Beta6
This is probably related to the plugin updates we made recently: the javadocs navigation bar now appears as a plain list of links.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-2380) OfflineStatusTest.timeBasedTakeOffline failure
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-2380:
-----------------------------------
Summary: OfflineStatusTest.timeBasedTakeOffline failure
Key: ISPN-2380
URL: https://issues.jboss.org/browse/ISPN-2380
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication
Affects Versions: 5.2.0.Beta1
Reporter: Adrian Nistor
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
This test fails constantly on my machine.
2012-10-11 10:36:35,388 ERROR [org.infinispan.test.fwk.UnitTestTestNGListener] (testng-OfflineStatusTest) Test timeBasedTakeOffline(org.infinispan.xsite.offline.OfflineStatusTest) failed.
java.lang.AssertionError: expected:<true> but was:<false>
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:480)
at org.testng.Assert.assertTrue(Assert.java:37)
at org.testng.Assert.assertTrue(Assert.java:47)
at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:76)
at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:59)
at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:132)
at org.infinispan.xsite.offline.OfflineStatusTest.timeBasedTakeOffline(OfflineStatusTest.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1147)
at org.testng.TestRunner.privateRun(TestRunner.java:749)
at org.testng.TestRunner.run(TestRunner.java:600)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)
at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month