[JBoss JIRA] (WFCORE-784) standalone.sh does not handle correctly situation when CDPATH environment variable is set
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-784?page=com.atlassian.jira.plugin... ]
Jason Greene updated WFCORE-784:
--------------------------------
Fix Version/s: 2.0.0.Final
(was: 2.0.0.CR9)
> standalone.sh does not handle correctly situation when CDPATH environment variable is set
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-784
> URL: https://issues.jboss.org/browse/WFCORE-784
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Martin Petricek
> Assignee: Tomaz Cerar
> Fix For: 2.0.0.Final
>
> Attachments: bin-fix.patch
>
>
> bin/standalone.sh does not use "shift" correctly when parsing commandline option, failing with "bin/standalone.sh: 34: shift: can't shift that many" if "--debug" without a parameter is used on dash (default shell in debian)
> Second issue is that the script does not handle correctly situation when CDPATH environment variable is set, failing completely.
> Attaching patch that fixes both these issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1075) Deploying a file results in HC logging "WFLYCTL0019: Graceful shutdown" warn on shutdown or reload
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1075?page=com.atlassian.jira.plugi... ]
Jason Greene updated WFCORE-1075:
---------------------------------
Fix Version/s: 2.0.0.Final
(was: 2.0.0.CR9)
> Deploying a file results in HC logging "WFLYCTL0019: Graceful shutdown" warn on shutdown or reload
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1075
> URL: https://issues.jboss.org/browse/WFCORE-1075
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.CR8
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.0.0.Final
>
>
> Host Controllers frequently take 15 seconds to shutdown and reload, logging the following after a 15s pause:
> {code}
> WFLYCTL0019: Graceful shutdown of the handler used for native management requests did not complete within [15000] ms but shutdown of the underlying communication channel is proceeding
> {code}
> This is because MasterDomainControllerOperationHandlerImpl and ServerToHostProtocolHandler both handle a GET_FILE_REQUEST by registering an ActiveOperation with ActiveOperationSupport, but then the GetFileOperation handlers for the request never call "done" or "failed" on the ActiveOperation.ResultHandler. The activeRequests map in the ActiveOperationSupport therefore ends up with extraneous data resulting in the shutdown delay.
> This is also a minor memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1052) Add server-config parameter to :reload op
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1052?page=com.atlassian.jira.plugi... ]
Jason Greene updated WFCORE-1052:
---------------------------------
Fix Version/s: 2.0.0.Final
(was: 2.0.0.CR9)
> Add server-config parameter to :reload op
> -----------------------------------------
>
> Key: WFCORE-1052
> URL: https://issues.jboss.org/browse/WFCORE-1052
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Kabir Khan
> Assignee: Kabir Khan
> Fix For: 2.0.0.Final
>
>
> {code}
> [13:48] Kabir Khan: @BrianStansberry @JasonGreene $./build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/bin/standalone.sh --server-config=20151013-134726769standalone.xml
looks for that file in the snapshots directory
> [13:48] Kabir Khan:
> [standalone@localhost:9990 /] :list-snapshots
> {
> "outcome" => "success",
> "result" => {
> "directory" => "/Users/kabir/sourcecontrol/wildfly/git/wildfly-core/build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/standalone/configuration/standalone_xml_history/snapshot",
> "names" => [
> "20151013-134523280standalone.xml",
> "20151013-134726769standalone.xml"
> ]
> }
> }
> Show less
> [13:50] Kabir Khan: server-config should probably be a parameter to the :reload operation
> {code}
> Similarly we should add host-config and domain-config parameters to the host's reload operation. Using domain-config on a non-DC host should fail.
> For a domain server, we should not have the server-config parameter.
> We should check the existence of the file before the reload actually is done, or we will end up in a sticky situation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-601) Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-601?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-601:
---------------------------------------
Assignee: ehsavoie Hugonnet (was: Stuart Douglas)
Emmanuel, since you are looking into WFCORE-1074 as well, and Stuart's PR has a CI failure he can't reproduce, can you take this over? Thanks.
> Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-601
> URL: https://issues.jboss.org/browse/WFCORE-601
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Stuart Douglas
> Assignee: ehsavoie Hugonnet
>
> I observed this today, looks to be some kind of race in the deployment scanner on boot
> {code}
> 21:52:08,618 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final
> 21:52:10,370 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
> 21:52:10,440 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting
> 21:52:11,390 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 20) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
> 21:52:11,409 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment mysql-ds.xml
> 21:52:11,413 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wildfly-ee7.war
> 21:52:11,488 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/48/032d14f289775249a004205c059588ab0f44d4/content
> 21:52:11,504 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c6/7babde4791697ddc6509fbd43ba1ec25952d47/content
> 21:52:11,506 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wildfly-ee7.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"wildfly-ee7.war\")]"
> 21:52:11,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations"
> 21:52:11,512 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations\""
> 21:52:11,514 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 21:52:11,514 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months