[JBoss JIRA] (ISPN-5152) Custom interceptor with Position.OTHER_THAN_FIRST_OR_LAST causes CacheManager start to fail
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5152?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5152:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1182561|https://bugzilla.redhat.com/show_bug.cgi?id=1182561] from ON_QA to VERIFIED
> Custom interceptor with Position.OTHER_THAN_FIRST_OR_LAST causes CacheManager start to fail
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-5152
> URL: https://issues.jboss.org/browse/ISPN-5152
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Listeners
> Affects Versions: 7.1.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Pedro Ruivo
> Fix For: 7.2.0.Beta1
>
>
> Use case (done via declarative config, but doesn't matter):
> 1) Add CustomInterceptor1 with position="FIRST"
> 2) Add CustomInterceptor2 with position="LAST"
> 3) Add CustomInterceptor3 with position="OTHER_THAN_FIRST_OR_LAST"
> Expected that order of interceptors 1, 3, 2, or at least it would work. Unfortunately, this configuration fails during start of CacheManager with:
> org.infinispan.commons.CacheConfigurationException: ISPN000225: Custom interceptor 'testpackage.CustomInterceptor3' doesn't specify a position
> Thus (and by looking at the code), option OTHER_THAN_FIRST_OR_LAST doesn't do anything.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5293) Create generic execution framework from EntryIterator
by William Burns (JIRA)
William Burns created ISPN-5293:
-----------------------------------
Summary: Create generic execution framework from EntryIterator
Key: ISPN-5293
URL: https://issues.jboss.org/browse/ISPN-5293
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Reporter: William Burns
Assignee: William Burns
This framework could be used to power a segment aware map/reduce framework and other events that require execution across the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5270) Deadlock in InfinispanDirectoryProvider startup
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-5270?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-5270:
-----------------------------------------
I'd be nice to avoid bootstrapping the query for those 3 index caches, as it will create threads, executors, interceptors, etc that don't make sense at runtime. So I think #2 is not worth the hassle.
Another alternative is, when a cache is starting, we detect from the configuration if this cache is a lucene cache, and simply don't bootstrap search on it, logging a WARN like "Cache LuceneIndexesData is configured as indexed, but it will be ignored, please check you config". This solves the deadlock problem, but we loose a very dubious corner case: storing the index and the data in the same cache - I don't think it is needed anyway
> Deadlock in InfinispanDirectoryProvider startup
> -----------------------------------------------
>
> Key: ISPN-5270
> URL: https://issues.jboss.org/browse/ISPN-5270
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.2.0.Alpha1, 7.1.1.Final
> Reporter: Dan Berindei
> Assignee: Gustavo Fernandes
> Priority: Minor
> Attachments: surefire.stacks, surefire2.stacks
>
>
> The InfinispanDirectoryProvider tries to start the metadata, data, and locking caches when it starts up, with {{DefaultCacheManager.startCaches()}}.
> However, when one of these caches (e.g. the metadata cache) starts, the {{LifecycleManager.cacheStarting()}}, which can then try to start the InfinispanDirectoryProvider again:
> {noformat}
> "CacheStartThread,null,LuceneIndexesMetadata" prio=10 tid=0x00007f5f74484000 nid=0xe42 in Object.wait() [0x00007f5efff48000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000000c2180000> (a org.infinispan.manager.DefaultCacheManager$1)
> at java.lang.Thread.join(Thread.java:1281)
> - locked <0x00000000c2180000> (a org.infinispan.manager.DefaultCacheManager$1)
> at java.lang.Thread.join(Thread.java:1355)
> at org.infinispan.manager.DefaultCacheManager.startCaches(DefaultCacheManager.java:465)
> at org.hibernate.search.infinispan.spi.InfinispanDirectoryProvider.start(InfinispanDirectoryProvider.java:84)
> at org.hibernate.search.indexes.spi.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:88)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:256)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:513)
> - locked <0x00000000ce6001d0> (a org.hibernate.search.indexes.impl.IndexManagerHolder)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManagers(IndexManagerHolder.java:482)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.buildEntityIndexBinding(IndexManagerHolder.java:91)
> - locked <0x00000000ce6001d0> (a org.hibernate.search.indexes.impl.IndexManagerHolder)
> at org.hibernate.search.spi.SearchIntegratorBuilder.initDocumentBuilders(SearchIntegratorBuilder.java:366)
> at org.hibernate.search.spi.SearchIntegratorBuilder.buildNewSearchFactory(SearchIntegratorBuilder.java:204)
> at org.hibernate.search.spi.SearchIntegratorBuilder.buildSearchIntegrator(SearchIntegratorBuilder.java:122)
> at org.hibernate.search.spi.SearchFactoryBuilder.buildSearchFactory(SearchFactoryBuilder.java:35)
> at org.infinispan.query.impl.LifecycleManager.getSearchFactory(LifecycleManager.java:260)
> at org.infinispan.query.impl.LifecycleManager.cacheStarting(LifecycleManager.java:102)
> at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:230)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:814)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:591)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:546)
> at org.infinispan.manager.DefaultCacheManager.access$100(DefaultCacheManager.java:115)
> at org.infinispan.manager.DefaultCacheManager$1.run(DefaultCacheManager.java:452)
> {noformat}
> This can hang the test, the attached thread dumps show {{EmbeddedCompatTest}} and {{IndexCacheStopTest}}.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-4322) AS Remote Client Module Integration Tests module fails with IBM JDK
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-4322?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-4322:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3281
> AS Remote Client Module Integration Tests module fails with IBM JDK
> -------------------------------------------------------------------
>
> Key: ISPN-4322
> URL: https://issues.jboss.org/browse/ISPN-4322
> Project: Infinispan
> Issue Type: Bug
> Components: Integration
> Affects Versions: 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4
> Environment: IBM JDK, RHEL
> Reporter: Vitalii Chepeliuk
> Assignee: Vitalii Chepeliuk
> Labels: testsuite_stability
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Infinispan BOM .................................... SUCCESS [10.419s]
> [INFO] Infinispan Common Parent .......................... SUCCESS [16.691s]
> [INFO] Infinispan Commons ................................ SUCCESS [30.414s]
> [INFO] Infinispan Core ................................... SUCCESS [1:20:24.345s]
> [INFO] Parent pom for server modules ..................... SUCCESS [2.764s]
> [INFO] Infinispan Server - Core Components ............... SUCCESS [1:39.998s]
> [INFO] Infinispan Query DSL API .......................... SUCCESS [3.182s]
> [INFO] Parent pom for cachestore modules ................. SUCCESS [1.421s]
> [INFO] Infinispan JDBC CacheStore ........................ SUCCESS [7:13.024s]
> [INFO] Parent pom for the Lucene integration modules ..... SUCCESS [1.302s]
> [INFO] Infinispan integration with Lucene v.3.x .......... SUCCESS [1:22.270s]
> [INFO] Infinispan Lucene Directory Implementation ........ SUCCESS [5.801s]
> [INFO] Infinispan Query API .............................. SUCCESS [16:27.946s]
> [INFO] Infinispan Tools .................................. SUCCESS [12.958s]
> [INFO] Infinispan Remote Query Client .................... SUCCESS [3.958s]
> [INFO] Infinispan Remote Query Server .................... SUCCESS [16.646s]
> [INFO] Infinispan JPA CacheStore ......................... SUCCESS [54.680s]
> [INFO] Infinispan Hot Rod Server ......................... SUCCESS [6:13.951s]
> [INFO] Infinispan Hot Rod Client ......................... SUCCESS [9:17.450s]
> [INFO] Parent pom for compatibility modules .............. SUCCESS [0.876s]
> [INFO] infinispan-custom52x-store ........................ SUCCESS [33.084s]
> [INFO] infinispan-adaptor52x ............................. SUCCESS [4:05.587s]
> [INFO] Infinispan remote CacheStore ...................... SUCCESS [53.506s]
> [INFO] Infinispan LevelDB CacheStore ..................... SUCCESS [1:19.592s]
> [INFO] Infinispan REST Server ............................ SUCCESS [2:08.409s]
> [INFO] Infinispan REST CacheStore ........................ SUCCESS [16.715s]
> [INFO] Infinispan Memcached Server ....................... SUCCESS [2:22.394s]
> [INFO] Infinispan RHQ Plugin ............................. SUCCESS [42.140s]
> [INFO] Infinispan CLI Server ............................. SUCCESS [48.143s]
> [INFO] Infinispan CLI Client ............................. SUCCESS [16.878s]
> [INFO] Infinispan CDI support ............................ SUCCESS [1:24.550s]
> [INFO] Infinispan AS/EAP modules for library ............. SUCCESS [18.319s]
> [INFO] Infinispan AS/EAP modules for remote client ....... SUCCESS [2.329s]
> [INFO] Integration tests: Security Tests ................. SUCCESS [2:11.936s]
> [INFO] Integration tests: SecurityManager tests .......... SUCCESS [13.313s]
> [INFO] Integration tests: AS Module Integration Tests .... SUCCESS [1:10.370s]
> [INFO] Integration tests: AS Remote Client Module Integration Tests FAILURE [57.162s]
> [INFO] Integration tests: Lucene Directory with Infinispan Query SUCCESS [23.074s]
> [INFO] Integration tests: Infinispan compatibility mode .. SUCCESS [35.351s]
> [INFO] Infinispan Distribution ........................... SUCCESS [1.090s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2:26:30.994s
> [INFO] Finished at: Fri May 23 21:38:55 EDT 2014
> [INFO] Final Memory: 227M/542M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (infinispan-server-shutdown) on project infinispan-as-module-remote-client-integrationtests: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program "/qa/tools/opt/amd64/ibm-java-70/bin/jps" (in directory "/mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client"): error=2, No such file or directory
> [ERROR] around Ant part ...<exec executable="/qa/tools/opt/amd64/ibm-java-70/bin/jps" output="jps.pid" osfamily="unix"/>... @ 4:96 in /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :infinispan-as-module-remote-client-integrationtests
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years