[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-4567:
----------------------------------------
Sending a PR with a change to add more logging on what Arquillian does WRT container lifecycle. Example output can be found here: https://gist.github.com/galderz/1275c4b7e6adcc997400
This output can be found in:
{{./integrationtests/as-integration-clien/target/failsafe-reports/org.infinispan.test.integration.as.HotRodClientIT-output.txt}} file
> InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-4567
> URL: https://issues.jboss.org/browse/ISPN-4567
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha5
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
>
> {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server:
> {noformat}
> [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server:
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR!
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4730) CacheStore is cleared after stopped
by Radim Vansa (JIRA)
Radim Vansa created ISPN-4730:
---------------------------------
Summary: CacheStore is cleared after stopped
Key: ISPN-4730
URL: https://issues.jboss.org/browse/ISPN-4730
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 7.0.0.Beta1
Reporter: Radim Vansa
Assignee: Dan Berindei
When a RemoveCacheCommand.perform() is called, the component registry is stopped and *after that*, all cache stores are cleared.
I believe that it's not correct to call the clear method when the store is in stopped state, and some cachestores don't anticipate that (such as SingleFileStore which throws NullPointerException).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-4567:
----------------------------------------
WRT kill_server, if you pass in multiple PIDs to `kill -9`, it'll kill them all, so if the other PID was arquillian container, it should have killed it :|
> InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-4567
> URL: https://issues.jboss.org/browse/ISPN-4567
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha5
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
>
> {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server:
> {noformat}
> [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server:
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR!
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4567) InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4567?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-4567:
----------------------------------------
I've looked into this in more detail:
- There are two servers involved here. One, a plain Infinispan server started according to the settings in build.xml. There's a second server, which runs an Arquillian test which is built from base Wildfly with Infinispan client modules and tries to communicate with the first server.
- IMO, the issue arises when the 2nd container, the Arquillian one which is started in 2nd position, does not stop correctly. As a result of that, kill_server script finds two servers, but it only kills one of them, leaving the Arquillian one still up. Arquillian tests after that fail to run cos there's a server already up.
- It's impossible to tell from the logs what caused the Arquillian server not to stop.
Things that we can (and can't) do to improve this:
- Bringing InfinispanServerKillProcessor to this module. That won't work since that processor is only used for situations when kill() is called on it.
- Improving kill_server so that it kills multiple servers might help in case the issue appears again.
- Enable console logging for client Arquillian so that it's clearer what it does.
> InfinispanLuceneDirectoryIT random failure: LifecycleException: The server is already running
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-4567
> URL: https://issues.jboss.org/browse/ISPN-4567
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Alpha5
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
>
> {{ManagedDeployableContainer}} detects a running container, even though the previous module killed its server:
> {noformat}
> [10:25:05] : [org.infinispan:infinispan-as-module-client-integrationtests] kill_server:
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [echo] Killing Infinispan server with PID - 3658 29739
> [10:25:06] : [org.infinispan:infinispan-as-module-client-integrationtests] [delete] Deleting: /mnt/ebs/TeamCity/buildAgent/work/master/integrationtests/as-integration-client/jps.pid
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT Time elapsed: 3.285 sec <<< ERROR!
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] org.jboss.arquillian.container.spi.client.container.LifecycleException: The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.failDueToRunning(ManagedDeployableContainer.java:358)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:88)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> [10:25:20] : [org.infinispan:infinispan-as-lucene-integration] at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4563) Race condition in JCache creation for interceptors
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-4563?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-4563:
-------------------------------------------
The root cause of this bug is in JCacheManager.java:
{code}
public <K, V, C extends Configuration<K, V>> Cache<K, V> createCache(
String cacheName, C configuration) {
...
// re-register attempt with different configuration
if (cache.getConfiguration(Configuration.class).equals(configuration)) {
throw log.cacheAlreadyRegistered(cacheName,
cache.getConfiguration(Configuration.class), configuration);
}
{code}
Above code should be replaced by:
{code}
public <K, V, C extends Configuration<K, V>> Cache<K, V> createCache(
String cacheName, C configuration) {
...
// re-register attempt with different configuration
// Note that configuration should not be equal...
if (!cache.getConfiguration(Configuration.class).equals(configuration)) {
throw log.cacheAlreadyRegistered(cacheName,
cache.getConfiguration(Configuration.class), configuration);
}
{code}
However with this change, JCache testing suite (org.jsr107.tck.CacheManagerTest#getOrCreateCache_Same()) blows out:
{code}
@Test
public void createCache_Same() {
String name = "c1";
CacheManager cacheManager = getCacheManager();
try {
cacheManager.createCache(name, new MutableConfiguration());
Cache cache1 = cacheManager.getCache(name);
cacheManager.createCache(name, new MutableConfiguration());
Cache cache2 = cacheManager.getCache(name);
fail();
} catch (CacheException exception) {
//expected
}
}
{code}
This happens because configurations created by {{new MutableConfiguration()}} are logically equal ({{config1.equals(config2)}}).
There are two solutions here:
* Compare configurations using {{==}} rather then {{equals}} method (I don't think we should follow this direction).
* There is a mistake in JCache testing suite and it should be fixed in the upstream.
> Race condition in JCache creation for interceptors
> --------------------------------------------------
>
> Key: ISPN-4563
> URL: https://issues.jboss.org/browse/ISPN-4563
> Project: Infinispan
> Issue Type: Bug
> Components: CDI Integration
> Affects Versions: 6.0.2.Final
> Reporter: Elias Ross
> Assignee: Sebastian Łaskawiec
> Fix For: 7.0.0.Final
>
>
> Intercepted methods, annotated like @CacheResult, if called from multiple threads, can attempt to create multiple caches.
> Work-around is to create the cache in a @PostContruct block.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4699) Non indexed query fails when a cachestore is used
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4699?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4699:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1140383|https://bugzilla.redhat.com/show_bug.cgi?id=1140383] from ON_QA to VERIFIED
> Non indexed query fails when a cachestore is used
> -------------------------------------------------
>
> Key: ISPN-4699
> URL: https://issues.jboss.org/browse/ISPN-4699
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Beta2
>
>
> {quote}
> 2014-05-08 16:32:05,586 WARN [LocalEntryRetriever] (transport-thread-NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest-NodeA-p3871-t3) ISPN000300: There was an exception while processing retrieval of entry values
> java.lang.IllegalArgumentException: argument cannot be null
> at org.infinispan.objectfilter.impl.BaseMatcher$3.filter(BaseMatcher.java:152)
> at org.infinispan.query.dsl.embedded.impl.FilterAndConverter.filterAndConvert(FilterAndConverter.java:91)
> at org.infinispan.query.dsl.embedded.impl.FilterAndConverter.filterAndConvert(FilterAndConverter.java:28)
> at org.infinispan.filter.AbstractKeyValueFilterConverter.accept(AbstractKeyValueFilterConverter.java:23)
> at org.infinispan.filter.KeyValueFilterAsKeyFilter.accept(KeyValueFilterAsKeyFilter.java:17)
> at org.infinispan.filter.CompositeKeyFilter.accept(CompositeKeyFilter.java:19)
> at org.infinispan.persistence.dummy.DummyInMemoryStore.process(DummyInMemoryStore.java:158)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.processOnAllStores(PersistenceManagerImpl.java:414)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.processOnAllStores(PersistenceManagerImpl.java:399)
> at org.infinispan.iteration.impl.LocalEntryRetriever$1.run(LocalEntryRetriever.java:256)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months