[JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
by ted won (JIRA)
ted won created WFLY-6633:
-----------------------------
Summary: 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
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)
9 years, 11 months
[JBoss JIRA] (WFLY-6616) Problems in DomainHostExcludes700TestCase
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6616?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-6616:
----------------------------------
The setup() method sets ignore-unused-configuration to false for an EAP 7 slave, it is defined and false in the model before shutting down the slave. At the time it calls startSlave() at the end of the setup() method the xml looks fine, i.e ignore-unused-configuration=false:
{code}
$more /Users/kabir/sourcecontrol/wildfly/git/wildfly/testsuite/mixed-domain/target/domains/LegacyConfig700TestSuite/slave/configuration/testing-host-slave.xml
<?xml version='1.0' encoding='UTF-8'?>
<host name="slave" xmlns="urn:jboss:domain:4.1">
--- SNIP ----
<domain-controller>
<remote host="${jboss.test.host.master.address}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm" ignore-unused-configuration="false"/>
</domain-controller>
{code}
However, following the boot of the slave this value is unset in the slave's model:
{code}
[domain@localhost:19999 /] /host=slave:read-attribute(name=domain-controller, include-defaults=true)
{
"outcome" => "success",
"result" => {"remote" => {
"protocol" => undefined,
"port" => expression "${jboss.domain.master.port:9999}",
"host" => expression "${jboss.test.host.master.address}",
"username" => undefined,
"ignore-unused-configuration" => undefined,
"admin-only-policy" => undefined,
"security-realm" => "ManagementRealm"
}}
}
{code}
Trying this with a copy of master and an EAP7 slave on the command line the same value in the xml results in
{code}
[domain@localhost:9999 /] /host=localhost:read-attribute(name=domain-controller)
{
"outcome" => "success",
"result" => {"remote" => {
"protocol" => undefined,
"port" => undefined,
"host" => undefined,
"username" => undefined,
"ignore-unused-configuration" => false,
{code}
in the slave's model following a boot.
> Problems in DomainHostExcludes700TestCase
> -----------------------------------------
>
> Key: WFLY-6616
> URL: https://issues.jboss.org/browse/WFLY-6616
> Project: WildFly
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Kabir Khan
> Assignee: Brian Stansberry
> Fix For: 11.0.0.Alpha1
>
>
> The profile clone operation in the new DomainHostExcludes700TestCase.test003PostBootUpdates() in testsuite/mixed-domain fails with the following message:
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.messaging.activemq.server.default' is already registered in context 'profile=clone'."},
> "rolled-back" => true
> }
> {code}
> And we also see an error in
> {code}
> DomainHostExcludes700TestCase.test001SlaveBoot:45->DomainHostExcludesTest.test001SlaveBoot:217->DomainHostExcludesTest.checkSocketBindingGroups:300 ["full-ha-sockets"] expected:<2> but was:<1>
> {code}
> Some WIP to create this test is in my https://github.com/kabir/wildfly/tree/WFLY-6616 branch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6632) Unable to create replicated cache
by Vinay Lodha (JIRA)
[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ]
Vinay Lodha updated WFLY-6632:
------------------------------
Steps to Reproduce:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tompOtp" default-cache="default" jndi-name="java:jboss/infinispan/tompOtp" aliases="test123" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/tomp" aliases="test1234" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
{code:java}
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
{code}
4. Try adding trasport configuration manually
{code:xml}
<cache-container name="tompOtp" default-cache="default" jndi-name="java:jboss/infinispan/tompOtp" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/tomp" aliases="test1234" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
5. server still fail to start
was:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
{code:java}
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
{code}
4. Try adding trasport configuration manually
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
5. server still fail to start
> Unable to create replicated cache
> ----------------------------------
>
> Key: WFLY-6632
> URL: https://issues.jboss.org/browse/WFLY-6632
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Vinay Lodha
> Assignee: Paul Ferraro
> Attachments: server.log, spring2-mvc-xml-hello-world-1.0-SNAPSHOT.war
>
>
> servers is unable to create replicated or distributed infinispan cache,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6632) Unable to create replicated cache
by Vinay Lodha (JIRA)
[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ]
Vinay Lodha updated WFLY-6632:
------------------------------
Steps to Reproduce:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
4. Try adding trasport configuration manually
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
5. server still fail to start
was:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
4. Try adding trasport configuration manually
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
5. server still fail to start
> Unable to create replicated cache
> ----------------------------------
>
> Key: WFLY-6632
> URL: https://issues.jboss.org/browse/WFLY-6632
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Vinay Lodha
> Assignee: Paul Ferraro
>
> servers is unable to create replicated or distributed infinispan cache,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6632) Unable to create replicated cache
by Vinay Lodha (JIRA)
[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ]
Vinay Lodha updated WFLY-6632:
------------------------------
Steps to Reproduce:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
{code:java}
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
{code}
4. Try adding trasport configuration manually
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
5. server still fail to start
was:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
4. Try adding trasport configuration manually
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
5. server still fail to start
> Unable to create replicated cache
> ----------------------------------
>
> Key: WFLY-6632
> URL: https://issues.jboss.org/browse/WFLY-6632
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Vinay Lodha
> Assignee: Paul Ferraro
>
> servers is unable to create replicated or distributed infinispan cache,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6632) Unable to create replicated cache
by Vinay Lodha (JIRA)
[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ]
Vinay Lodha updated WFLY-6632:
------------------------------
Steps to Reproduce:
1. Add new cache in infinispan subsystem
{code:xml}
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
{code}
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
4. Try adding trasport configuration manually
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
5. server still fail to start
was:
1. Add new cache in infinispan subsystem
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
2. Deploy a sample application which use that cache. (You will need to update web.xml also as mentioned in https://issues.jboss.org/browse/WFLY-4562)
3. Server startup fail saying
2016-05-20 17:33:52,308 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.tompOtp.default.config: org.jboss.msc.service.StartException in service jboss.infinispan.tompOtp.default.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
4. Try adding trasport configuration manually
<cache-container name="tomp" default-cache="default" jndi-name="java:jboss/infinispan/test" aliases="test123" statistics-enabled="false">
<transport channel="TCP" lock-timeout="60000"/>
<replicated-cache name="default" mode="SYNC"/>
</cache-container>
5. server still fail to start
> Unable to create replicated cache
> ----------------------------------
>
> Key: WFLY-6632
> URL: https://issues.jboss.org/browse/WFLY-6632
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.2.Final
> Reporter: Vinay Lodha
> Assignee: Paul Ferraro
>
> servers is unable to create replicated or distributed infinispan cache,
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months