[JBoss JIRA] (ISPN-1942) State transfer timeout confusion
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-1942:
--------------------------------------
Summary: State transfer timeout confusion
Key: ISPN-1942
URL: https://issues.jboss.org/browse/ISPN-1942
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 5.1.3.CR1
Reporter: Galder Zamarreño
Assignee: Dan Berindei
Fix For: 5.1.3.FINAL
Several things are not right in the forum post above:
1. The XML file should not allow both stateRetrieval (deprecated) and stateTransfer to be defined:
{code}<?xml version="1.0" encoding="UTF-8"?>
<infinispan
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:infinispan:config:5.1 http://www.infinispan.org/schemas/infinispan-config-5.1.xsd"
xmlns="urn:infinispan:config:5.1">
<global>
<transport clusterName="hotrod-test" distributedSyncTimeout="16000000">
<properties>
<property name="configurationFile" value="/opt/infinispan-5.1.1.FINAL/etc/gossip-router-config.xml"/>
</properties>
</transport>
<globalJmxStatistics enabled="true"/>
</global>
<default>
<jmxStatistics enabled="true"/>
<locking
lockAcquisitionTimeout="16000000"
/>
<clustering mode="replicated">
<sync replTimeout="16000000"/>
<!-- for replication -->
<stateRetrieval timeout="16000000"/>
<stateTransfer timeout="16000000"/>
</clustering>
</default>
<namedCache name="A"/>
<namedCache name="B"/>
<namedCache name="C"/>
<namedCache name="D"/>
</infinispan>{code}
2. In spite of setting the stateTransfer timeout, state transfer is looking for hash.rehashRpcTimeout which by default is 10 minutes? @Dan, shouldn't the state transfer timeout be passed onto the hash.rehashTimeout?
Also @Dan, do we have any docu on how this really should be configured in 5.1?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (ISPN-1921) Non-existing jGroups config file gives unclear exception
by Jens Rantil (JIRA)
Jens Rantil created ISPN-1921:
---------------------------------
Summary: Non-existing jGroups config file gives unclear exception
Key: ISPN-1921
URL: https://issues.jboss.org/browse/ISPN-1921
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Core API
Affects Versions: 5.1.2.FINAL
Reporter: Jens Rantil
Assignee: Manik Surtani
Priority: Minor
Took me a long to figure this out, so I'm creating an issue for it.
When initializing an EmbeddedCacheManager with a transport (jGroups) configuration file that does not exist the following exception is eventually given:
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:222)
at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:654)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:619)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:516)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:489)
[...]
Caused by: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object
at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:238)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:882)
at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:637)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:626)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:200)
... 38 more
Caused by: org.infinispan.CacheException: java.lang.NullPointerException: the specifed protocol stack configuration was null
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:333)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannel(JGroupsTransport.java:252)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:292)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:170)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:236)
... 43 more
Caused by: java.lang.NullPointerException: the specifed protocol stack configuration was null
at org.jgroups.conf.ConfiguratorFactory.checkForNullConfiguration(ConfiguratorFactory.java:228)
at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:60)
at org.jgroups.JChannel.<init>(JChannel.java:136)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:330)
... 51 more
I guess the reason why the exception is given first when DefaultCacheManager.getCache(...) is called, is because it is initialized lazily. Sadly, this goes against "Fail early" and it would be useful if the file could not be read at configuration time.
Also, if the file cannot be found/read there should a be a separate Exception thrown for this that states that fact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (ISPN-1936) FileCacheStore does not seem to close open files on Windows
by Matthew Farwell (JIRA)
Matthew Farwell created ISPN-1936:
-------------------------------------
Summary: FileCacheStore does not seem to close open files on Windows
Key: ISPN-1936
URL: https://issues.jboss.org/browse/ISPN-1936
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.1.2.FINAL
Environment: Windows 7
Reporter: Matthew Farwell
Assignee: Manik Surtani
Using the following java (see Test.java):
public static void main(String[] args) throws Exception {
DefaultCacheManager manager = new DefaultCacheManager("config/config.xml");
Cache<String, String> cache = manager.getCache("evictionCache");
for (int i = 0; i < 10000; i++) {
cache.put("key" + i, "value" + i);
}
cache.stop();
manager.stop();
}
with the following config (see config.xml):
<infinispan>
<namedCache name="evictionCache">
<loaders passivation="false" shared="false" preload="true">
<loader class="org.infinispan.loaders.file.FileCacheStore"
fetchPersistentState="true" ignoreModifications="false"
purgeOnStartup="false">
<properties>
<property name="location" value="d:\code\infinispan\store" />
</properties>
</loader>
</loaders>
<eviction maxEntries="5000" strategy="LRU" />
<expiration lifespan="60000" maxIdle="10000" wakeUpInterval="500" />
</namedCache>
</infinispan>
running under Windows 7, there are two problems:
1) There are lots INFO: Unable to remove empty file
d:\code\infinispan\store\evictionCache\-1134715904 - will try again
later. I'm running under windows, so this may have something to do
with it, but the process which is holding on to the file handles is
the jvm. Is it possible that something somewhere is holding the files
open somewhere? Looking at the code in FileCacheStore, there doesn't
seem to be anything obvious.
2) This may be related to the above, but the process eventually falls
over with java.nio.channels.ClosedByInterruptException (with
iterations = 1000) see console-1000.txt or a java.io.EOFException: The
stream ended unexpectedly. for iterations = 10000 (see
console-10000.txt).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months