[JBoss JIRA] (WFCORE-1622) Worker section in IO subsystem does not allow expressions for io-threads and task-max-threads attributes
by keen user (JIRA)
keen user created WFCORE-1622:
---------------------------------
Summary: Worker section in IO subsystem does not allow expressions for io-threads and task-max-threads attributes
Key: WFCORE-1622
URL: https://issues.jboss.org/browse/WFCORE-1622
Project: WildFly Core
Issue Type: Bug
Reporter: keen user
I want to dynamically configure following section in IO subsystem in standalone.xml of wildfly:
<worker name="default" io-threads="100" task-max-threads="1000"/>
Here if I do something like:
<worker name="default" io-threads="${my.io.threads:100}" task-max-threads="${my.task.max.threads:1000}"/>
And pass parameters as -Dmy.io.threads, -Dmy.task.max.threads while starting wildfly server, it's failing to parse standalone.xml with following exception:
_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.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] Caused by: java.lang.NumberFormatException: For input string: "${my.io.threads:100}" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [rt.jar:1.8.0_45] at java.lang.Integer.parseInt(Integer.java:569) [rt.jar:1.8.0_45] at java.lang.Integer.parseInt(Integer.java:615) [rt.jar:1.8.0_45] at org.jboss.dmr.StringModelValue.asInt(StringModelValue.java:139) [jboss-dmr-1.2.0.Final.jar:1.2.0.Final] at org.jboss.dmr.ModelNode.asInt(ModelNode.java:240) [jboss-dmr-1.2.0.Final.jar:1.2.0.Final] at org.jboss.as.controller.AttributeParser.parse(AttributeParser.java:116) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.AttributeParser.parse(AttributeParser.java:82) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.AttributeParser$DiscardOldDefaultValueParser.parse(AttributeParser.java:177) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.AttributeParser.parseAndSetParameter(AttributeParser.java:61) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.PersistentResourceXMLDescription.parse(PersistentResourceXMLDescription.java:83) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.PersistentResourceXMLDescription.parseChildren(PersistentResourceXMLDescription.java:135) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.controller.PersistentResourceXMLDescription.parse(PersistentResourceXMLDescription.java:107) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final] at org.wildfly.extension.io.IOSubsystemParser_1_0.readElement(IOSubsystemParser_1_0.java:71) at org.wildfly.extension.io.IOSubsystemParser_1_0.readElement(IOSubsystemParser_1_0.java:41) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1131) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:458) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.2.0.Final.jar:8.2.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.2.0.Final.jar:8.2.0.Final] ... 3 more_
This section should allow expressions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1614) Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1614?page=com.atlassian.jira.plugi... ]
Brian Stansberry reopened WFCORE-1614:
--------------------------------------
I'm reopening as I had to revert the change following CI failures.
> Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-1614
> URL: https://issues.jboss.org/browse/WFCORE-1614
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Fix For: 3.0.0.Alpha3
>
>
> We are proposing here to add a Cli option (command line option and an XML element) to make the CLI to echo the command and its options in non interactive mode. This will help to match a given command and its output.
> For example, the "ls -l" command output would be:
> [standalone@localhost:9990 /] ls -l
> ATTRIBUTE VALUE TYPE
> launch-type STANDALONE STRING
> management-major-version 5 INT
> management-micro-version 0 INT
> management-minor-version 0 INT
> ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1379) service.bat points user to wrong directory
by Andrej Tibaut (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1379?page=com.atlassian.jira.plugi... ]
Andrej Tibaut edited comment on WFCORE-1379 at 6/25/16 2:55 PM:
----------------------------------------------------------------
I can confirm that this issue is not resolved yet.
I have installed wildfly-10.0.0.Final on Windows 2012 server and can't get Wildfly running as a service. I downloaded all latest /service files form GitHub and replaced existing wildfly-10.0.0.Final files.
It is installed as a service but cannot start.
Here is the System Event Log:
"The Wildfly service terminated with the following service-specific error:
The extended attributes are inconsistent."
See it here:
https://www.dropbox.com/s/d2uf2awoyxz6k7d/Screenshot%202016-06-25%2020.46...
I need urgent advice...please!
was (Author: andrejt):
I can confirm that this issue is not resolved yet.
I have installed wildfly-10.0.0.Final on Windows 2012 server and can't get Wildfly running as a service. I downloaded all latest /service files form GitHub and replaced existing wildfly-10.0.0.Final files.
It is installed as a service but cannot start.
Here is the System Event Log:
"The Wildfly service terminated with the following service-specific error:
The extended attributes are inconsistent."
See it here:
https://www.dropbox.com/s/d2uf2awoyxz6k7d/Screenshot%202016-06-25%2020.46...
> service.bat points user to wrong directory
> ------------------------------------------
>
> Key: WFCORE-1379
> URL: https://issues.jboss.org/browse/WFCORE-1379
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.10.Final
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
> Priority: Trivial
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Running service.bat from the docs/contrib/scripts/service dir tells user to run the script under bin/service*s* but the binary paths to the services expects bin/service, resulting in service install failure with file not found
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1379) service.bat points user to wrong directory
by Andrej Tibaut (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1379?page=com.atlassian.jira.plugi... ]
Andrej Tibaut edited comment on WFCORE-1379 at 6/25/16 2:54 PM:
----------------------------------------------------------------
I can confirm that this issue is not resolved yet.
I have installed wildfly-10.0.0.Final on Windows 2012 server and can't get Wildfly running as a service. I downloaded all latest /service files form GitHub and replaced existing wildfly-10.0.0.Final files.
It is installed as a service but cannot start.
Here is the System Event Log:
"The Wildfly service terminated with the following service-specific error:
The extended attributes are inconsistent."
See it here:
https://www.dropbox.com/s/d2uf2awoyxz6k7d/Screenshot%202016-06-25%2020.46...
was (Author: andrejt):
I can confirm that this issue is not resolved yet.
I have installed wildfly-10.0.0.Final on Windows 2012 server and can't get Wildfly running as a service. It is installed but cannot start.
Here is the System Event Log:
"The Wildfly service terminated with the following service-specific error:
The extended attributes are inconsistent."
See it here:
https://www.dropbox.com/s/d2uf2awoyxz6k7d/Screenshot%202016-06-25%2020.46...
> service.bat points user to wrong directory
> ------------------------------------------
>
> Key: WFCORE-1379
> URL: https://issues.jboss.org/browse/WFCORE-1379
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.10.Final
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
> Priority: Trivial
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Running service.bat from the docs/contrib/scripts/service dir tells user to run the script under bin/service*s* but the binary paths to the services expects bin/service, resulting in service install failure with file not found
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1379) service.bat points user to wrong directory
by Andrej Tibaut (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1379?page=com.atlassian.jira.plugi... ]
Andrej Tibaut commented on WFCORE-1379:
---------------------------------------
I can confirm that this issue is not resolved yet.
I have installed wildfly-10.0.0.Final on Windows 2012 server and can't get Wildfly running as a service. It is installed but cannot start.
Here is the System Event Log:
"The Wildfly service terminated with the following service-specific error:
The extended attributes are inconsistent."
See it here:
https://www.dropbox.com/s/d2uf2awoyxz6k7d/Screenshot%202016-06-25%2020.46...
> service.bat points user to wrong directory
> ------------------------------------------
>
> Key: WFCORE-1379
> URL: https://issues.jboss.org/browse/WFCORE-1379
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.10.Final
> Reporter: Nicklas Karlsson
> Assignee: Tomaz Cerar
> Priority: Trivial
> Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>
> Running service.bat from the docs/contrib/scripts/service dir tells user to run the script under bin/service*s* but the binary paths to the services expects bin/service, resulting in service install failure with file not found
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6772) Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6772?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6772:
---------------------------------
Labels: graceful_undeploy (was: )
> Intermittent failures in ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-6772
> URL: https://issues.jboss.org/browse/WFLY-6772
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Labels: graceful_undeploy
> Fix For: 10.1.0.Final
>
>
> 172 runs / 5 failures / 0 ignored Success rate: 97.1%
> org.jboss.as.test.clustering.cluster.web (1)
> ConcurrentFineWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover — Muted on 07 Jun 16 14:48 by Tomaz Cerar
>
> First failure: pull/1628 #2988 Changes (73) 22 Jun 16 16:47
> java.lang.AssertionError: Session failed to replicate after container 1 was shutdown. expected:<7> but was:<6>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testFailover(AbstractWebFailoverTestCase.java:207)
> at org.jboss.as.test.clustering.cluster.web.AbstractWebFailoverTestCase.testGracefulUndeployFailover(AbstractWebFailoverTestCase.java:103)
> https://ci.wildfly.org/viewLog.html?buildId=19454&tab=buildResultsDiv&bui...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6775) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-6775?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-6775:
--------------------------------
Description:
Note both WildFly and WildFly Core will need to be updated. It may be possible to remove the dependencies from WildFly and keep everything in core. However it needs to be determined if we should add all the slf4j dependencies to core.
There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
[Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
{quote}
The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
{quote}
Analysis will need to be done to ensure this works as expected before the fork is no longer required.
was:
There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
[Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
{quote}
The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
{quote}
Analysis will need to be done to ensure this works as expected before the fork is no longer required.
> Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
> -----------------------------------------------------
>
> Key: WFLY-6775
> URL: https://issues.jboss.org/browse/WFLY-6775
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
>
> Note both WildFly and WildFly Core will need to be updated. It may be possible to remove the dependencies from WildFly and keep everything in core. However it needs to be determined if we should add all the slf4j dependencies to core.
> There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
> [Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
> {quote}
> The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
> {quote}
> Analysis will need to be done to ensure this works as expected before the fork is no longer required.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFCORE-1621) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
by James Perkins (JIRA)
James Perkins created WFCORE-1621:
-------------------------------------
Summary: Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
Key: WFCORE-1621
URL: https://issues.jboss.org/browse/WFCORE-1621
Project: WildFly Core
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
[Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
{quote}
The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
{quote}
Analysis will need to be done to ensure this works as expected before the fork is no longer required.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
[JBoss JIRA] (WFLY-6775) Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-6775?page=com.atlassian.jira.plugin.... ]
James Perkins moved WFCORE-1621 to WFLY-6775:
---------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-6775 (was: WFCORE-1621)
Component/s: Logging
(was: Logging)
> Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.21
> -----------------------------------------------------
>
> Key: WFLY-6775
> URL: https://issues.jboss.org/browse/WFLY-6775
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
>
> There should no longer be a need for the forked version. The fix for [SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some additional fixes for replaying the previously lost logs.
> [Quote from comment on JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
> {quote}
> The problem of lost logs during initialization in a multi-threaded application is solved by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J version 1.7.15.
> {quote}
> Analysis will need to be done to ensure this works as expected before the fork is no longer required.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 4 months
