Infinispan subsystem configures its transport with invalid timeout values. -------------------------------------------------------------------------- Key: AS7-1272 URL: https://issues.jboss.org/browse/AS7-1272 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Final Reporter: Trustin Lee Assignee: Paul Ferraro Whenever I start the Infinispan subsystem, I see the following warning: {code} 13:20:23,854 WARN [org.infinispan.config.TimeoutConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN00148: Invalid <transport>: distributedSyncTimout value of 240000. It can not be higher than <stateRetrieval>:timeout which is 10000 {code} The current subsystem configuration looks like the following: {code} <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="default"> <cache-container name="default" default-cache="default" listener-executor="infinispan-listener" eviction-executor="infinispan-eviction" replication-queue-executor="infinispan-repl-queue"> <transport executor="infinispan-transport" lock-timeout="240000"/> <distributed-cache name="default" start="EAGER" mode="SYNC" virtual-nodes="1" owners="2" batching="false" indexing="NONE" l1-lifespan="0" remote-timeout="30000"> <locking isolation="REPEATABLE_READ" acquire-timeout="30000" concurrency-level="1000" striping="false" /> <rehashing enabled="true" timeout="600000" /> </distributed-cache> </cache-container> </subsystem> {code} It seems like there are not all attribute that correspond to all transport timeout properties. If that's intended, as least the subsystem should feed the sensible defaults to Infinispan. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira