| Summary: | Infinispan subsystem configures its transport with invalid timeout values. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Trustin Lee <trustin> |
| Component: | unspecified | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | galder.zamarreno, jdg-bugs, mlinhard |
| Target Milestone: | --- | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/EDG-16 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-01 08:09:09 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Link: Added: This issue depends AS7-1272 added dependency on ISPN-1231 Link: Added: This issue depends ISPN-1231 btw in EDG6 build I worked around this by <topology-state-transfer replication-timeout="240000" /> Michal, should this be closed then? Docs QE Status: Removed: NEW |
project_key: EDG 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.