[JBoss JIRA] (WFLY-3008) System property substitution does not work in subnet-match
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3008?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3008:
---------------------------------
Assignee: Tomaz Cerar
> System property substitution does not work in subnet-match
> ----------------------------------------------------------
>
> Key: WFLY-3008
> URL: https://issues.jboss.org/browse/WFLY-3008
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Tomaz Cerar
> Priority: Minor
>
> Specifying a system property in subnet-match when defining an interface causes an exception on startup. Example:
> {code:xml}
> <property name="subnet" value="192.168.0.0/16"/>
> ...
> <interface name="public">
> <subnet-match value="${subnet}"/>
> </interface>
> {code}
> Causes:
> {code}
> 12:36:13,457 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[311,46]
> Message: JBAS014693: Invalid 'value' ${subnet} -- must be of the form address/mask
> at org.jboss.as.server.parsing.CommonXml.validateAddressMask(CommonXml.java:605) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseSimpleInterfaceCriterion(CommonXml.java:587) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaceCriteria(CommonXml.java:467) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaces(CommonXml.java:644) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:465) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3008) System property substitution does not work in subnet-match
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3008?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3008:
------------------------------
Assignee: Brian Stansberry (was: Tomaz Cerar)
> System property substitution does not work in subnet-match
> ----------------------------------------------------------
>
> Key: WFLY-3008
> URL: https://issues.jboss.org/browse/WFLY-3008
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Brian Stansberry
> Priority: Minor
>
> Specifying a system property in subnet-match when defining an interface causes an exception on startup. Example:
> {code:xml}
> <property name="subnet" value="192.168.0.0/16"/>
> ...
> <interface name="public">
> <subnet-match value="${subnet}"/>
> </interface>
> {code}
> Causes:
> {code}
> 12:36:13,457 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[311,46]
> Message: JBAS014693: Invalid 'value' ${subnet} -- must be of the form address/mask
> at org.jboss.as.server.parsing.CommonXml.validateAddressMask(CommonXml.java:605) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseSimpleInterfaceCriterion(CommonXml.java:587) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaceCriteria(CommonXml.java:467) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaces(CommonXml.java:644) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:465) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3008) System property substitution does not work in subnet-match
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3008?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3008:
------------------------------
Component/s: Domain Management
> System property substitution does not work in subnet-match
> ----------------------------------------------------------
>
> Key: WFLY-3008
> URL: https://issues.jboss.org/browse/WFLY-3008
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Rich DiCroce
>
> Specifying a system property in subnet-match when defining an interface causes an exception on startup. Example:
> {code:xml}
> <property name="subnet" value="192.168.0.0/16"/>
> ...
> <interface name="public">
> <subnet-match value="${subnet}"/>
> </interface>
> {code}
> Causes:
> {code}
> 12:36:13,457 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[311,46]
> Message: JBAS014693: Invalid 'value' ${subnet} -- must be of the form address/mask
> at org.jboss.as.server.parsing.CommonXml.validateAddressMask(CommonXml.java:605) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseSimpleInterfaceCriterion(CommonXml.java:587) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaceCriteria(CommonXml.java:467) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.CommonXml.parseInterfaces(CommonXml.java:644) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:465) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3013) Cannot add exploded deployments through CLI on Windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3013?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3013:
------------------------------
Assignee: (was: Jason Greene)
> Cannot add exploded deployments through CLI on Windows
> ------------------------------------------------------
>
> Key: WFLY-3013
> URL: https://issues.jboss.org/browse/WFLY-3013
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Jan Martiska
> Priority: Minor
>
> Try to deploy a directory (exploded deployment) in Windows like this:
> {noformat}
> /deployment=eardeployment1.ear:add(content=[{"path"=>"C:\QA\jmartisk\exploded_deployments\eardeployment1.ear","archive"=>false}],enabled=true)
> {noformat}
> it fails with an error like this:
> {noformat}
> "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE"
> => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE: JBAS018733:
> Failed to process phase STRUCTURE of deployment \"eardeployment1.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment
> content
> Caused by: java.io.FileNotFoundException: C:\\QA\\jmartisk\\wildfly-8.0.1.Final-SNAPSHOT\\QAjmartiskexploded_deploymentseardeployment1.ear (The filename, directory name, or volume label synt
> ax is incorrect)"}},
> {noformat}
> The same command works in Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3013) Cannot add exploded deployments through CLI on Windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3013?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3013:
-----------------------------------
you should escape \
so this should work:
{noformat}
/deployment=eardeployment1.ear:add(content=[{"path"=>"C:\\QA\\jmartisk\\exploded_deployments\\eardeployment1.ear","archive"=>false}],enabled=true)
{noformat}
> Cannot add exploded deployments through CLI on Windows
> ------------------------------------------------------
>
> Key: WFLY-3013
> URL: https://issues.jboss.org/browse/WFLY-3013
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Jan Martiska
> Priority: Minor
>
> Try to deploy a directory (exploded deployment) in Windows like this:
> {noformat}
> /deployment=eardeployment1.ear:add(content=[{"path"=>"C:\QA\jmartisk\exploded_deployments\eardeployment1.ear","archive"=>false}],enabled=true)
> {noformat}
> it fails with an error like this:
> {noformat}
> "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE"
> => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE: JBAS018733:
> Failed to process phase STRUCTURE of deployment \"eardeployment1.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment
> content
> Caused by: java.io.FileNotFoundException: C:\\QA\\jmartisk\\wildfly-8.0.1.Final-SNAPSHOT\\QAjmartiskexploded_deploymentseardeployment1.ear (The filename, directory name, or volume label synt
> ax is incorrect)"}},
> {noformat}
> The same command works in Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3013) Cannot add exploded deployments through CLI on Windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3013?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3013:
------------------------------
Component/s: Domain Management
(was: Server)
> Cannot add exploded deployments through CLI on Windows
> ------------------------------------------------------
>
> Key: WFLY-3013
> URL: https://issues.jboss.org/browse/WFLY-3013
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Jan Martiska
> Assignee: Jason Greene
> Priority: Minor
>
> Try to deploy a directory (exploded deployment) in Windows like this:
> {noformat}
> /deployment=eardeployment1.ear:add(content=[{"path"=>"C:\QA\jmartisk\exploded_deployments\eardeployment1.ear","archive"=>false}],enabled=true)
> {noformat}
> it fails with an error like this:
> {noformat}
> "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE"
> => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"eardeployment1.ear\".STRUCTURE: JBAS018733:
> Failed to process phase STRUCTURE of deployment \"eardeployment1.ear\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018740: Failed to mount deployment
> content
> Caused by: java.io.FileNotFoundException: C:\\QA\\jmartisk\\wildfly-8.0.1.Final-SNAPSHOT\\QAjmartiskexploded_deploymentseardeployment1.ear (The filename, directory name, or volume label synt
> ax is incorrect)"}},
> {noformat}
> The same command works in Linux.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-1904) Usage of vault for system-properties throws java.lang.SecurityException
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1904?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-1904:
-----------------------------------
Fix Version/s: 8.0.1.Final
> Usage of vault for system-properties throws java.lang.SecurityException
> -----------------------------------------------------------------------
>
> Key: WFLY-1904
> URL: https://issues.jboss.org/browse/WFLY-1904
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: 8.0.0.Beta1
> Reporter: Navin Surtani
> Assignee: Brian Stansberry
> Fix For: 8.0.1.Final
>
>
> Steps to Reproduce: 1. add the lines in standalone.xml:-
> {code}
> <system-properties>
> <property name="javax.net.ssl.trustStore" value="/dir/truststore.jks"/>
> <property name="javax.net.ssl.trustStorePassword" value="${VAULT::blk::attr::MTBlYWUzNDEtMjI2MC00NWYzLWFiZmUtM2EyYjZkNDgyZWM4TElORV9CUkVBS215YWxpYXM=}" />
> </system-properties>
> <vault>
> <vault-option name="KEYSTORE_URL" value="/opt/jboss-eap-6.0/standalone/configuration/vault.jks"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-2gTQPnrWJaqrh0pURMKAOw"/>
> <vault-option name="KEYSTORE_ALIAS" value="myalias"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="44"/>
> <vault-option name="ENC_FILE_DIR" value="/opt/jboss-eap-6.0/standalone/configuration/"/>
> </vault>
> {code}
> 2. start EAP6 in standalone mode
> project_key: JBPAPP6
> Usage of vault for system-properties throws java.lang.SecurityException.
> boot.log:-
> {code}
> 20:35:30,267 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([("system-property" => "javax.net.ssl.trustStorePassword")]): java.lang.SecurityException: JBAS013322: Vault is not initialized
> at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:98) [jboss-as-security-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.RuntimeExpressionResolver.resolvePluggableExpression(RuntimeExpressionResolver.java:45) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressionsRecursively(ExpressionResolverImpl.java:58) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressions(ExpressionResolverImpl.java:40) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ModelControllerImpl.resolveExpressions(ModelControllerImpl.java:455) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.OperationContextImpl.resolveExpressions(OperationContextImpl.java:689) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.operations.common.SystemPropertyAddHandler.execute(SystemPropertyAddHandler.java:112) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:175) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:295) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_37]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1735) JChannel.startFlush() does not attempt back-off on flush collision
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1735?page=com.atlassian.jira.plugin.... ]
Bela Ban reassigned JGRP-1735:
------------------------------
Assignee: Vladimir Blagojevic (was: Bela Ban)
> JChannel.startFlush() does not attempt back-off on flush collision
> ------------------------------------------------------------------
>
> Key: JGRP-1735
> URL: https://issues.jboss.org/browse/JGRP-1735
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4
> Reporter: Rich DiCroce
> Assignee: Vladimir Blagojevic
> Fix For: 3.5
>
>
> The Javadoc for JChannel.startFlush() says:
> {quote}
> In case of flush collisions, a random sleep time backoff algorithm is employed and the flush is reattempted for numberOfAttempts. Therefore this method is guaranteed to return after timeout x numberOfAttempts milliseconds.
> {quote}
> This does not appear to be true. I had two nodes call this method at the same time and immediately got an exception due to a flush collision. The salient part of the stack trace is:
> {noformat}
> Caused by: java.lang.Exception: Flush failed for EITSQL2-33698
> at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:435) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:501) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.RSVP.up(RSVP.java:221) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:182) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:796) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.UNICAST3.handleBatchReceived(UNICAST3.java:752) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:466) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:662) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.FD.up(FD.java:274) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.stack.Protocol.up(Protocol.java:409) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.TP.passBatchUp(TP.java:1422) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> at org.jgroups.protocols.TP$BatchHandler.run(TP.java:1574) [jgroups-3.4.0.Final.jar:3.4.0.Final]
> ... 3 more
> {noformat}
> The Javadoc talks about "timeout" and "numberOfAttempts" as if they were method parameters, but they aren't. Were those part of an earlier version of JGroups? If they're still present, where are they? Will JGroups still retry a flush that failed due to a collision?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1697) Timeout in FLUSH will block all cluster
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1697?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1697:
--------------------------------
[~vblagojevic] I think you can close this one Vladimir, as there is zero information provided
> Timeout in FLUSH will block all cluster
> ---------------------------------------
>
> Key: JGRP-1697
> URL: https://issues.jboss.org/browse/JGRP-1697
> Project: JGroups
> Issue Type: Bug
> Environment: 3.4.0.Alpha2
> Reporter: shen kim
> Assignee: Vladimir Blagojevic
> Fix For: 3.5
>
>
> When I defined FLUSH like this:
> <UDP />
> <PING />
> <MERGE2 />
> <FD_SOCK />
> <FD_ALL />
> <VERIFY_SUSPECT />
> <pbcast.NAKACK2 />
> <UNICAST3 />
> <pbcast.STABLE />
> <pbcast.GMS />
> <UFC />
> <MFC />
> <FRAG2 />
> <pbcast.STATE_TRANSFER />
> <pbcast.FLUSH timeout="0"/>
> If I set timeout to 0, and sending message to all cluster, the all cluster would be block until the new member join cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months