Bug 745900 (EDG-16) - Infinispan subsystem configures its transport with invalid timeout values.
Summary: Infinispan subsystem configures its transport with invalid timeout values.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-16
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0.0
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-16
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-13 04:28 UTC by Trustin Lee
Modified: 2012-08-15 16:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-01 08:09:09 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-16 0 Major Closed Infinispan subsystem configures its transport with invalid timeout values. 2012-09-18 16:36:29 UTC

Description Trustin Lee 2011-07-13 04:28:44 UTC
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.

Comment 1 Trustin Lee 2011-07-13 04:29:11 UTC
Link: Added: This issue depends AS7-1272


Comment 2 Michal Linhard 2011-07-13 19:46:58 UTC
added dependency on ISPN-1231

Comment 3 Michal Linhard 2011-07-13 19:46:58 UTC
Link: Added: This issue depends ISPN-1231


Comment 4 Michal Linhard 2011-07-13 19:48:13 UTC
btw in EDG6 build I worked around this by <topology-state-transfer replication-timeout="240000" />

Comment 5 Galder Zamarreño 2011-08-03 07:19:23 UTC
Michal, should this be closed then?

Comment 6 Anne-Louise Tangring 2011-09-26 19:41:24 UTC
Docs QE Status: Removed: NEW 



Note You need to log in before you can comment on or make changes to this bug.