[jira] [Created] (IGNITE-11086) IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of seconds.
Vitaliy Biryukov created IGNITE-11086:
-
Summary: IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in
deciseconds instead of seconds.
Key: IGNITE-11086
URL: https://issues.apache.org/jira/browse/IGNITE-11086
Project: Ignite
Issue Type: Bug
Components: rest
Affects Versions: 2.7
Reporter: Vitaliy Biryukov
According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should sit in seconds.
Can be fixed by multiplying this parameter by 1000 instead of 100 in
GridRestProcessor's constructor:
{code:java}
sesTokTtl = IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT,
DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10731) ZookeeperDiscoverySpiTestSuite4: IgniteCacheReplicatedQuerySelfTest.testNodeLeft fails
Vitaliy Biryukov created IGNITE-10731:
-
Summary: ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft fails
Key: IGNITE-10731
URL: https://issues.apache.org/jira/browse/IGNITE-10731
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.7
Environment: {noformat}
junit.framework.AssertionFailedError:
Expected :0
Actual :312
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at
org.apache.ignite.internal.processors.cache.distributed.replicated.IgniteCacheReplicatedQuerySelfTest.testNodeLeft(IgniteCacheReplicatedQuerySelfTest.java:348)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:151)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2102)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2117)
at java.lang.Thread.run(Thread.java:745)
{noformat}
Reporter: Vitaliy Biryukov
Assignee: Vitaliy Biryukov
Fix For: 2.8
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9861) Authorization object names must always be non-null.
Vitaliy Biryukov created IGNITE-9861: Summary: Authorization object names must always be non-null. Key: IGNITE-9861 URL: https://issues.apache.org/jira/browse/IGNITE-9861 Project: Ignite Issue Type: Improvement Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov Fix For: 2.8 Currently, sometimes *null* name parameter passing to a method *GridSecurityProcessor:authorize*. This leads to the fact that it is impossible to determine the authorization object by authorization event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9267) Deadlock between unsuccessful client reconnecting and stopping.
Vitaliy Biryukov created IGNITE-9267:
Summary: Deadlock between unsuccessful client reconnecting and
stopping.
Key: IGNITE-9267
URL: https://issues.apache.org/jira/browse/IGNITE-9267
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Vitaliy Biryukov
Fix For: 2.7
Reconnecting thread:
{noformat}
"zk-internal.IgniteClientReconnectCacheTest3-EventThread" #593633 daemon prio=5
os_prio=0 tid=0x7ff8e4063800 nid=0x478e waiting for monitor entry
[0x7ff90f2f]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2565)
- waiting to lock <0xe9429280> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2557)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3417)
at
org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3904)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:831)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:590)
- locked <0xe9429468> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processLocalJoin(ZookeeperDiscoveryImpl.java:2960)
- locked <0xe9429478> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2760)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2623)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2598)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.access$2000(ZookeeperDiscoveryImpl.java:108)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl$ZkWatcher.processResult(ZookeeperDiscoveryImpl.java:4108)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient$DataCallbackWrapper.processResult(ZookeeperClient.java:1219)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)
{noformat}
Stopping thread:
{noformat}
"main" #1 prio=5 os_prio=0 tid=0x7ffba000e000 nid=0x6aa3 waiting for
monitor entry [0x7ffba8c83000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.stop0(ZookeeperDiscoveryImpl.java:3838)
- waiting to lock <0xe9429478> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.stop(ZookeeperDiscoveryImpl.java:3813)
at
org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStop(ZookeeperDiscoverySpi.java:501)
at
org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1683)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2206)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2081)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2594)
- locked <0xe9429280> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2557)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1153)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1193)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1174)
at
org.apache.ignite.internal.IgniteClientReconnectCacheTest.afterTest(IgniteClientReconnectCacheTest.java:151)
at
org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1763)
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:503)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9243) Avoid test suit hangs on stopAllGrids
Vitaliy Biryukov created IGNITE-9243: Summary: Avoid test suit hangs on stopAllGrids Key: IGNITE-9243 URL: https://issues.apache.org/jira/browse/IGNITE-9243 Project: Ignite Issue Type: Improvement Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov Fix For: 2.7 Tests sometimes hang on node join to topology, and this leads to the hang of the whole suite. Solution: Do not wait for nodes to join a topology in *stopAllGrids* method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9169) Cache (Deadlock Detection) hangs
Vitaliy Biryukov created IGNITE-9169: Summary: Cache (Deadlock Detection) hangs Key: IGNITE-9169 URL: https://issues.apache.org/jira/browse/IGNITE-9169 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9138) ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails if zk cluster was stpped before nodes.
Vitaliy Biryukov created IGNITE-9138: Summary: ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails if zk cluster was stpped before nodes. Key: IGNITE-9138 URL: https://issues.apache.org/jira/browse/IGNITE-9138 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9134) ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME
Vitaliy Biryukov created IGNITE-9134: Summary: ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME Key: IGNITE-9134 URL: https://issues.apache.org/jira/browse/IGNITE-9134 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
Vitaliy Biryukov created IGNITE-9130: Summary: ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails Key: IGNITE-9130 URL: https://issues.apache.org/jira/browse/IGNITE-9130 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9127) ZooKeeper (Discovery) 1 suite hang.
Vitaliy Biryukov created IGNITE-9127: Summary: ZooKeeper (Discovery) 1 suite hang. Key: IGNITE-9127 URL: https://issues.apache.org/jira/browse/IGNITE-9127 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8699) ZookeeperDiscoverySpiTest#testDisconnectOnServersLeft flaky fails (rarely)
Vitaliy Biryukov created IGNITE-8699: Summary: ZookeeperDiscoverySpiTest#testDisconnectOnServersLeft flaky fails (rarely) Key: IGNITE-8699 URL: https://issues.apache.org/jira/browse/IGNITE-8699 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8257) GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)
Vitaliy Biryukov created IGNITE-8257:
Summary: GridFutureAdapterSelfTest#testChaining flaky-fails on TC
(rarely)
Key: IGNITE-8257
URL: https://issues.apache.org/jira/browse/IGNITE-8257
Project: Ignite
Issue Type: Test
Reporter: Vitaliy Biryukov
Assignee: Vitaliy Biryukov
Fix For: 2.6
{code:java}
class org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout
was reached before computation completed.
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:242)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
at
org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.checkChaining(GridFutureAdapterSelfTest.java:283)
at
org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.testChaining(GridFutureAdapterSelfTest.java:237)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7986) GridPartitionStateMap.entrySet() optimization.
Vitaliy Biryukov created IGNITE-7986: Summary: GridPartitionStateMap.entrySet() optimization. Key: IGNITE-7986 URL: https://issues.apache.org/jira/browse/IGNITE-7986 Project: Ignite Issue Type: Improvement Reporter: Vitaliy Biryukov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-6557) Test IgniteTxRemoveTimeoutObjectsTest has flaky fails
Vitaliy Biryukov created IGNITE-6557:
Summary: Test IgniteTxRemoveTimeoutObjectsTest has flaky fails
Key: IGNITE-6557
URL: https://issues.apache.org/jira/browse/IGNITE-6557
Project: Ignite
Issue Type: Bug
Reporter: Vitaliy Biryukov
Build log:
{noformat}
[org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects]
junit.framework.AssertionFailedError: Grids contain LockTimeoutObjects.
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.assertDoesNotContainLockTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:135)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:92)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6527) Deadlock detection work incorrect with deadlocks that are not the cause of the timeout.
Vitaliy Biryukov created IGNITE-6527: Summary: Deadlock detection work incorrect with deadlocks that are not the cause of the timeout. Key: IGNITE-6527 URL: https://issues.apache.org/jira/browse/IGNITE-6527 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov Assignee: Vitaliy Biryukov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6445) IgniteTxManager.txLocksInfo method misses locks
Vitaliy Biryukov created IGNITE-6445: Summary: IgniteTxManager.txLocksInfo method misses locks Key: IGNITE-6445 URL: https://issues.apache.org/jira/browse/IGNITE-6445 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov In some cases "IgniteTxManager.txLocksInfo" method (searches for locks) misses locks. For example: In case of a configuration with near cache, entities are created for the near cache and for the ordinal cache. For each entity, their own MVCC candidates are created. For non-custom objects of type (Integer, etc.), the entity stored in "GridNearTxLocal" is not associated with MVCC candidates with which the same entity is associated in another format stored in "GridDhtTxLocal" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6442) Deadlock detection doesn't execute.
Vitaliy Biryukov created IGNITE-6442: Summary: Deadlock detection doesn't execute. Key: IGNITE-6442 URL: https://issues.apache.org/jira/browse/IGNITE-6442 Project: Ignite Issue Type: Bug Reporter: Vitaliy Biryukov In case of a configuration with near cache and if all entities of one of the transactions involved in the deadlock are on the node being the initiator of this transaction, then immediately after the timeout, the transaction rolls back (without calling DD). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
