[JBoss JIRA] (WFLY-9420) Cluster partitions can take up to cca 2 minutes to merge
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9420:
--------------------------------------
Needs to be retested after jgroups 4 upgrade.
> Cluster partitions can take up to cca 2 minutes to merge
> --------------------------------------------------------
>
> Key: WFLY-9420
> URL: https://issues.jboss.org/browse/WFLY-9420
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Labels: partition_handling
>
> Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen.
> The info sender interval is up to 45 seconds
> {code:java}
> public long nextInterval() {
> return Math.max(min_interval, Util.random(max_interval) + max_interval/2);
> }
> {code}
> and the view consistency checker interval is 48 seconds
> {code:java}
> protected long computeCheckInterval() {
> return (long)(max_interval * 1.6);
> }
> {code}
> which depending on the timing seem to take significant amount of time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFCORE-3685) Use org.jboss.modules.ClassTransformer for transformation DUPs
by David Lloyd (JIRA)
David Lloyd created WFCORE-3685:
-----------------------------------
Summary: Use org.jboss.modules.ClassTransformer for transformation DUPs
Key: WFCORE-3685
URL: https://issues.jboss.org/browse/WFCORE-3685
Project: WildFly Core
Issue Type: Enhancement
Components: Server
Reporter: David Lloyd
Priority: Minor
Once the JBoss Modules 1.8.0.Final upgrade is in to core, switch to using {{org.jboss.modules.ClassTransformer}} in {{org.jboss.as.server.deployment.module.ClassFileTransformerProcessor}} and {{org.jboss.as.server.deployment.module.DelegatingClassFileTransformer}} if possible.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10025) Use new org.jboss.modules.ClassTransformer interface instead of j.l.i.ClassFileTransformer
by David Lloyd (JIRA)
David Lloyd created WFLY-10025:
----------------------------------
Summary: Use new org.jboss.modules.ClassTransformer interface instead of j.l.i.ClassFileTransformer
Key: WFLY-10025
URL: https://issues.jboss.org/browse/WFLY-10025
Project: WildFly
Issue Type: Enhancement
Components: JPA / Hibernate
Reporter: David Lloyd
Assignee: Scott Marlow
Priority: Minor
The JPA classes use {{java.lang.instrument.ClassFileTransformer}} for class transformation, however this style of transformer incurs an extra whole-byte-array copy when loading memory-mapped classes or using other resource loaders which operate on byte buffers.
After the Modules 1.8.0.Final upgrade, switch to using {{org.jboss.modules.ClassTransformer}} instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10024) Stale session data on failover
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10024?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10024:
-----------------------------------
Description:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225
Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
was:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
> Stale session data on failover
> ------------------------------
>
> Key: WFLY-10024
> URL: https://issues.jboss.org/browse/WFLY-10024
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Labels: clustering, wildfly
>
> Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
> When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
> {code:java}
> 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225
> Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10024) Stale session data on failover
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10024?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10024:
-----------------------------------
Description:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225
Full log : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
was:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225
Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
> Stale session data on failover
> ------------------------------
>
> Key: WFLY-10024
> URL: https://issues.jboss.org/browse/WFLY-10024
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Labels: clustering, wildfly
>
> Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
> When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
> {code:java}
> 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Looks like this bug is related to a previous one marked as VERIFIED : https://issues.jboss.org/browse/WFLY-6225
> Full log : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10024) Stale session data on failover
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10024?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10024:
-----------------------------------
Description:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
was:
The version used is the latest at the time of execution i.e. WildFly Full 13.0.0.Alpha1-SNAPSHOT
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
> Stale session data on failover
> ------------------------------
>
> Key: WFLY-10024
> URL: https://issues.jboss.org/browse/WFLY-10024
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Labels: clustering, wildfly
>
> Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
> When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
> {code:java}
> 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10024) Stale session data on failover
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10024?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10024:
-----------------------------------
Description:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
was:
Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
{code:java}
2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:748)
{code}
Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
> Stale session data on failover
> ------------------------------
>
> Key: WFLY-10024
> URL: https://issues.jboss.org/browse/WFLY-10024
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Labels: clustering, wildfly
>
> Scenario: failover-http-session-jvmkill-repl-sync (i.e. with REPL cache and SYNC replication)
> When the node failover process starts (node JVMs start getting killed) we see the following exception on the client side:
> {code:java}
> 2018/03/09 12:13:03:209 EST [WARN ][Runner - 1597] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597>
> org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 64, received 63, Runner: 1597
> at org.jboss.smartfrog.loaddriver.http.AbstractSerialNumberValidatorFactoryImpl$SerialNumberValidator.processRequest(AbstractSerialNumberValidatorFactoryImpl.java:133)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Looks like this bug is related to a previous one marked as verified : https://issues.jboss.org/browse/WFLY-6225
> Complete logs : https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-f...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months