[JBoss JIRA] (ISPN-4129) Add Query, CDI, JCache, LevelDB and REST to the AS modules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4129?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4129:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1076093|https://bugzilla.redhat.com/show_bug.cgi?id=1076093] from VERIFIED to CLOSED
> Add Query, CDI, JCache, LevelDB and REST to the AS modules
> ----------------------------------------------------------
>
> Key: ISPN-4129
> URL: https://issues.jboss.org/browse/ISPN-4129
> Project: Infinispan
> Issue Type: Feature Request
> Components: Build process
> Affects Versions: 7.0.0.Alpha1
> Reporter: Tristan Tarrant
> Assignee: Pedro Ruivo
> Fix For: 7.0.0.Beta1, 7.0.0.Final
>
>
> Query, CDI, JCache, LevelDB and REST modules need to be added to the AS modules we ship
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-4406) Stabilise security manager integration testsuite
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4406?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4406:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1091373|https://bugzilla.redhat.com/show_bug.cgi?id=1091373] from VERIFIED to CLOSED
> Stabilise security manager integration testsuite
> ------------------------------------------------
>
> Key: ISPN-4406
> URL: https://issues.jboss.org/browse/ISPN-4406
> Project: Infinispan
> Issue Type: Bug
> Components: Security
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.Alpha5
>
>
> integrationtests/security-manager-it tests randomly fail, which might be related to the fact that a lot of these tests rely on static initialisation, and I think that's causing messing up between tests initialising/uninitialising these static variables. The fact that the errors are random seems to back this up.
> However, enabling sequential testing results in:
> {code}[ERROR] java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'LIFECYCLE' permission
> [ERROR] at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:56)
> [ERROR] at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:70)
> [ERROR] at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:75)
> [ERROR] at org.infinispan.manager.DefaultCacheManager.getStatus(DefaultCacheManager.java:677)
> [ERROR] at org.infinispan.test.fwk.TestCacheManagerFactory$PerThreadCacheManagers.checkManagersClosed(TestCacheManagerFactory.java:435)
> [ERROR] at org.infinispan.test.fwk.TestCacheManagerFactory.testFinished(TestCacheManagerFactory.java:422)
> [ERROR] at org.infinispan.test.fwk.UnitTestTestNGListener.onFinish(UnitTestTestNGListener.java:104){code}
> This error is also present in paralell testing but in this case it's just logged rather than halting the process.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-4237) Security manager test QueryAuthorizationTest.testQuery fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4237?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4237:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1091373|https://bugzilla.redhat.com/show_bug.cgi?id=1091373] from VERIFIED to CLOSED
> Security manager test QueryAuthorizationTest.testQuery fails
> ------------------------------------------------------------
>
> Key: ISPN-4237
> URL: https://issues.jboss.org/browse/ISPN-4237
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 7.0.0.Alpha3
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
> Attachments: QueryAuthorizationTest.log.zip
>
>
> {{org.infinispan.security.QueryAuthorizationTest.testQuery}} fails (no matter which JDK is used) with
> {noformat}
> java.lang.IllegalArgumentException: Indexing was not enabled on this cache. interface org.hibernate.search.spi.SearchFactoryIntegrator not found in registry
> at org.infinispan.query.impl.ComponentRegistryUtils.getComponent(ComponentRegistryUtils.java:27)
> at org.infinispan.query.impl.ComponentRegistryUtils.getComponent(ComponentRegistryUtils.java:20)
> at org.infinispan.query.impl.SearchManagerImpl.<init>(SearchManagerImpl.java:42)
> at org.infinispan.query.Search.getSearchManager(Search.java:21)
> at org.infinispan.security.QueryAuthorizationTest.queryTest(QueryAuthorizationTest.java:97)
> at org.infinispan.security.QueryAuthorizationTest.access$300(QueryAuthorizationTest.java:32)
> at org.infinispan.security.QueryAuthorizationTest$4.run(QueryAuthorizationTest.java:113)
> at org.infinispan.security.QueryAuthorizationTest$4.run(QueryAuthorizationTest.java:109)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.infinispan.security.QueryAuthorizationTest.testQuery(QueryAuthorizationTest.java:109)
> {noformat}
> Example of test failure in Jenkins on RHEL6 and Oracle JDK 7 is e.g. [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-tes...].
> Maybe it's some setup issue, as on Jenkins it fails on all platforms, while I;m not able to reproduce it on my machine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-4719) Race condition in QueryCache initialization
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4719?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4719:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1140652|https://bugzilla.redhat.com/show_bug.cgi?id=1140652] from VERIFIED to CLOSED
> Race condition in QueryCache initialization
> -------------------------------------------
>
> Key: ISPN-4719
> URL: https://issues.jboss.org/browse/ISPN-4719
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 7.0.0.Beta2
>
>
> {noformat}07:48:54,189 DEBUG [org.infinispan.interceptors.InterceptorChain] (Stressor-2) Interceptor chain size: 6
> 07:48:54,189 DEBUG [org.infinispan.interceptors.InterceptorChain] (Stressor-2) Interceptor chain is:
> >> org.infinispan.interceptors.InvocationContextInterceptor
> >> org.infinispan.interceptors.CacheMgmtInterceptor
> >> org.infinispan.interceptors.NotificationInterceptor
> >> org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor
> >> org.infinispan.interceptors.EntryWrappingInterceptor
> >> org.infinispan.interceptors.CallInterceptor
> 07:48:54,206 DEBUG [org.infinispan.jmx.JmxUtil] (Stressor-2) Object name org.infinispan:type=Cache,name="__query_cache__(local)",manager="DefaultCacheManager",component=Cache already registered
> 07:48:54,207 DEBUG [org.infinispan.CacheImpl] (Stressor-2) Started cache __query_cache__ on edg-perf10-33989
> 07:48:54,208 ERROR [org.radargun.stages.test.Stressor] (Stressor-8) Unexpected error in stressor!
> java.lang.NullPointerException
> at org.infinispan.query.dsl.embedded.impl.QueryCache.get(QueryCache.java:58)
> at org.infinispan.query.dsl.embedded.impl.EmbeddedLuceneQueryBuilder.build(EmbeddedLuceneQueryBuilder.java:50)
> at org.infinispan.query.dsl.embedded.impl.EmbeddedLuceneQueryBuilder.build(EmbeddedLuceneQueryBuilder.java:20)
> at org.radargun.service.AbstractInfinispanQueryable$QueryBuilderImpl.build(AbstractInfinispanQueryable.java:169)
> at org.radargun.stages.cache.test.QueryStage$Logic.run(QueryStage.java:153)
> at org.radargun.stages.test.Stressor.runInternal(Stressor.java:75)
> at org.radargun.stages.test.Stressor.run(Stressor.java:53){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-4490) Members can miss the rebalance cancellation on coordinator change
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4490?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4490:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1104045|https://bugzilla.redhat.com/show_bug.cgi?id=1104045] from VERIFIED to CLOSED
> Members can miss the rebalance cancellation on coordinator change
> -----------------------------------------------------------------
>
> Key: ISPN-4490
> URL: https://issues.jboss.org/browse/ISPN-4490
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.0.Alpha4
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 7.0.0.Alpha5
>
>
> The new coordinator sends first a CH_UPDATE command to cancel the existing rebalance, and then a REBALANCE_START command to start a new rebalance. But the CH_UPDATE command is sent asynchronously, so it's possible for some members to receive it after the REBALANCE_START command.
> If that happens, that node will assume that it will receive the segments it requested for the previous rebalance. But with the ISPN-4484 fix, the provider node cancels the outbound transfer tasks when receiving a CH_UPDATE without a pendingCH, so the state requestor will never receive its segments.
> Even without the ISPN-4484 fix this is a problem, although less obvious. Between the provider node receiving the CH_UPDATE and the REBALANCE_START commands, it won't have the requestor in its write CH, so the requestor can miss transactions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-4484) Outbound transfers can be cancelled by old CANCEL_STATE_TRANSFER command
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4484?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4484:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1104045|https://bugzilla.redhat.com/show_bug.cgi?id=1104045] from VERIFIED to CLOSED
> Outbound transfers can be cancelled by old CANCEL_STATE_TRANSFER command
> ------------------------------------------------------------------------
>
> Key: ISPN-4484
> URL: https://issues.jboss.org/browse/ISPN-4484
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 6.0.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.0.0.Alpha5
>
>
> This appeared during the 32-nodes elasticity test in the Hyperion environment.
> Just as apex947 left, it started a rebalance, which apex948 dutifully cancelled as it became the new coordinator. apex949 had already requested segments from apex959, so it sent a StateRequestCommand(CANCEL_STATE_TRANSFER) asynchronously to apex959. Then apex948 started a new rebalance, and apex949 asked apex959 for the same segments. When apex959 finally received the cancel request, it didn't check the topology id and it incorrectly cancelled the outbound transfer to apex949.
> The solution would be to verify the topology id in the CANCEL_STATE_TRANSFER command before cancelling the transfer. I also think we can avoid sending the cancel command completely in this case, and only send it as we are about to stop.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months