[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:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1091373|https://bugzilla.redhat.com/show_bug.cgi?id=1091373] from MODIFIED to ON_QA
> Stabilise security manager integration testsuite
> ------------------------------------------------
>
> Key: ISPN-4406
> URL: https://issues.jboss.org/browse/ISPN-4406
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> 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.1#6329)
11 years, 7 months
[JBoss JIRA] (ISPN-4667) Query DSL fails to load entity class in Wildfly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4667?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4667:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1134112|https://bugzilla.redhat.com/show_bug.cgi?id=1134112] from MODIFIED to ON_QA
> Query DSL fails to load entity class in Wildfly
> -----------------------------------------------
>
> Key: ISPN-4667
> URL: https://issues.jboss.org/browse/ISPN-4667
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Embedded Querying
> Affects Versions: 7.0.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Beta2
>
>
> When using the as modules and an application that depends on those modules, the following code:
> {code}
> Cache cache = ...
> Query query = Search.getQueryFactory(cache).from(Book.class).having("field").contains("value").toBuilder().build();
> List<Object> results = query.list();
> {code}
> fails with
> {code}
> java.lang.IllegalStateException: Unknown entity name org.infinispan.test.integration.as.query.Book
> at org.hibernate.hql.lucene.internal.ClassBasedLuceneQueryResolverDelegate.registerPersisterSpace(ClassBasedLuceneQueryResolverDelegate.java:104)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.entityName(GeneratedHQLResolver.java:12729)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.persisterSpaceRoot(GeneratedHQLResolver.java:3064)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.persisterSpace(GeneratedHQLResolver.java:2956)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.persisterSpaces(GeneratedHQLResolver.java:2893)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.fromClause(GeneratedHQLResolver.java:2803)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.selectFrom(GeneratedHQLResolver.java:2704)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.querySpec(GeneratedHQLResolver.java:2182)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.queryExpression(GeneratedHQLResolver.java:2106)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.queryStatement(GeneratedHQLResolver.java:1745)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.queryStatementSet(GeneratedHQLResolver.java:1658)
> at org.hibernate.hql.ast.origin.hql.resolve.GeneratedHQLResolver.statement(GeneratedHQLResolver.java:654)
> at org.hibernate.hql.ast.spi.QueryResolverProcessor.process(QueryResolverProcessor.java:52)
> at org.hibernate.hql.QueryParser.parseQuery(QueryParser.java:82)
> at org.infinispan.query.dsl.embedded.impl.EmbeddedLuceneQueryBuilder.build(EmbeddedLuceneQueryBuilder.java:43)
> at org.infinispan.query.dsl.embedded.impl.EmbeddedLuceneQueryBuilder.build(EmbeddedLuceneQueryBuilder.java:19)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (ISPN-4569) Inserting into cache with indexing fails for XA transactions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4569?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4569:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1130493|https://bugzilla.redhat.com/show_bug.cgi?id=1130493] from POST to MODIFIED
> Inserting into cache with indexing fails for XA transactions
> ------------------------------------------------------------
>
> Key: ISPN-4569
> URL: https://issues.jboss.org/browse/ISPN-4569
> Project: Infinispan
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Embedded Querying, Transactions
> Affects Versions: 7.0.0.Alpha5
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Fix For: 7.0.0.Beta1
>
>
> If I setup XA transactions in {{ClusteredQueryDslConditionsTest}} using
> {code}
> cacheCfg.transaction().transactionMode(TransactionMode.TRANSACTIONAL).useSynchronization(false);
> {code}
> the test fails. The reason is in deadlock while updating {{ScopedKey}} in __cluster_registry_cache__ : It seems that on originator we create transaction with modified inserted key and the {{ScopedKey}} for inserted class, and send it in two prepare commands to the other node. In the {{ScopedKey}}-prepare, the lock is acquired, but the regular prepare on the other node does not see it (it is not committed yet) and also tries to update this {{ScopedKey}} in __cluster_registry_cache__ . This fails with lock timeout, as the commit is waiting on the regular prepare to finish.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months