[JBoss JIRA] (AS7-5379) CLONE - Stale data received with SYNC on failover
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-5379?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar commented on AS7-5379:
-------------------------------------
I ll try to pick this up for testing ASAP.
> CLONE - Stale data received with SYNC on failover
> -------------------------------------------------
>
> Key: AS7-5379
> URL: https://issues.jboss.org/browse/AS7-5379
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Environment: affected 6.0.0 DR CI build
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: as713tracking
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> After verifying fix for JBPAPP-8937 I am instead seeing stale data received when using DIST SYNC replication.
> REPL SYNC: On a failover after the application has been gracefully undeployed, a request can be getting data older by cca 40 seconds:
> {noformat}
> 2012/08/14 15:12:53:327 EDT [WARN ][Runner - 1295] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 46, received 35, Runner: 1295
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> DIST SYNC: On server crash stale data can be received:
> {noformat}
> 2012/08/04 05:13:49:714 EDT [WARN ][Runner - 8] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 43, received 42, Runner: 8
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:125)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
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, 2 months
[JBoss JIRA] (AS7-5397) Support for expression in JGroups property element
by Jochen Cordes (JIRA)
Jochen Cordes created AS7-5397:
----------------------------------
Summary: Support for expression in JGroups property element
Key: AS7-5397
URL: https://issues.jboss.org/browse/AS7-5397
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, Server
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jochen Cordes
Assignee: Paul Ferraro
When trying to set a property for the protocol TCPPING like this:
<protocol type="TCPPING" socket-binding="jgroups-tcpping">
<property name=”initial_hosts”>${initial_hosts}</property>
</protocol>
we get a parser error on startup (${initial_hosts} is set in a property
file we have specified with -P). Doing a :read-resource-attributes via
CLI reveals that the property element doesn't support expressions.
Are there plans to support this in the future or is there a specific
reason why this isn't supported for this specific element?
--
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, 2 months