[JBoss JIRA] (WFLY-5464) JDR report contains reference to AS7
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFLY-5464?page=com.atlassian.jira.plugin.... ]
Ingo Weiss commented on WFLY-5464:
----------------------------------
What about this approach, https://github.com/wildfly/wildfly/pull/8922?
> JDR report contains reference to AS7
> ------------------------------------
>
> Key: WFLY-5464
> URL: https://issues.jboss.org/browse/WFLY-5464
> Project: WildFly
> Issue Type: Bug
> Components: JDR
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Minor
>
> *Description of problem:*
> JDR report contains some legacy reference to AS7
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # Create a JDR report using one of provided scripts (depends on OS)
> # Check the created report
> ## cd $JDR_LOCATION
> ## find | grep as7
> *Actual results:*
> {noformat}
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/configuration.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/tree.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/dump-services.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/deployment-dependencies.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jarcheck.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/cluster-proxies-configuration.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/local-module-dependencies.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/system-properties.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jndi-view.json
> {noformat}
> *Expected results:*
> No references to AS7
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-5464) JDR report contains reference to AS7
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFLY-5464?page=com.atlassian.jira.plugin.... ]
Ingo Weiss edited comment on WFLY-5464 at 5/20/16 11:59 AM:
------------------------------------------------------------
What about this approach, https://github.com/wildfly/wildfly/pull/8922 instead?
was (Author: iweiss):
What about this approach, https://github.com/wildfly/wildfly/pull/8922?
> JDR report contains reference to AS7
> ------------------------------------
>
> Key: WFLY-5464
> URL: https://issues.jboss.org/browse/WFLY-5464
> Project: WildFly
> Issue Type: Bug
> Components: JDR
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Minor
>
> *Description of problem:*
> JDR report contains some legacy reference to AS7
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # Create a JDR report using one of provided scripts (depends on OS)
> # Check the created report
> ## cd $JDR_LOCATION
> ## find | grep as7
> *Actual results:*
> {noformat}
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/configuration.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/tree.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/dump-services.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/deployment-dependencies.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jarcheck.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/cluster-proxies-configuration.json
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/local-module-dependencies.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/system-properties.txt
> ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jndi-view.json
> {noformat}
> *Expected results:*
> No references to AS7
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1563) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1563?page=com.atlassian.jira.plugi... ]
ted won moved WFLY-6633 to WFCORE-1563:
---------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1563 (was: WFLY-6633)
Component/s: CLI
(was: CLI)
Affects Version/s: 3.0.0.Alpha1
(was: 10.0.0.Final)
Fix Version/s: 3.0.0.Alpha2
(was: 10.1.0.Final)
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFCORE-1563
> URL: https://issues.jboss.org/browse/WFCORE-1563
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha1
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 3.0.0.Alpha2
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> {panel:title=Error message}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> {panel}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Description:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{panel:title=Error message}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{panel}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
was:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{panel}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{panel}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> {panel:title=Error message}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> {panel}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Description:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{panel}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{panel}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
was:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{panel}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{panel}
{noformat}
*no* further _formatting_ is done here
{noformat}
{warning}
{warning}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> {panel}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> {panel}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Description:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{panel}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{panel}
{noformat}
*no* further _formatting_ is done here
{noformat}
{warning}
{warning}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
was:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{warning}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{warning}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> {panel}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> {panel}
> {noformat}
> *no* further _formatting_ is done here
> {noformat}
> {warning}
> {warning}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Description:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
{warning}
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
{warning}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
was:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> {warning}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> {warning}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Description:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
{code}
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
{code}
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
was:
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> {code}
> batch
> deploy --force ./jboss-ejb-in-ear.ear
> run-batch
> {code}
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Steps to Reproduce:
1. %WILDFLY_HOME/bin/domain.sh
2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
3. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully
4. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
5. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
was:
1. %WILDFLY_HOME/bin/domain.sh
2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
3. %WILDFLY_HOME/bin/jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully
4. %WILDFLY_HOME/bin/jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
5. %WILDFLY_HOME/bin/jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ]
ted won updated WFLY-6633:
--------------------------
Steps to Reproduce:
1. %WILDFLY_HOME/bin/domain.sh
2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
3. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully
4. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
5. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
was:
1. %WILDFLY_HOME/bin/domain.sh
2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch
3. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully
4. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
5. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
> Failed CLI batch command with "deploy --force" for replace deployment
> ---------------------------------------------------------------------
>
> Key: WFLY-6633
> URL: https://issues.jboss.org/browse/WFLY-6633
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 10.0.0.Final
> Reporter: ted won
> Assignee: ted won
> Priority: Minor
> Labels: cli, jboss
> Fix For: 10.1.0.Final
>
> Attachments: jboss-ejb-in-ear.ear
>
>
> Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
> However, it's working in CLI interactive mode without error.
> There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
> Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
> -------------------------------------------------------------------------------------------
> * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
> {code}
> {
> "operation" => "add",
> "address" => {"deployment" => "jboss-ejb-in-ear.ear"},
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
> * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
> {code}
> {
> "operation" => "full-replace-deployment",
> "name" => "jboss-ejb-in-ear.ear",
> "address" => [],
> "enabled" => true,
> "content" => [{"bytes" => bytes {
> ...
> }}]
> }
> {code}
> -------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month