[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-9746:
------------------------------------
WFLY-9271 changed the jgroups-stack capability reference to refer to a CommandDispatcherFactory capability. This breaks configuration that specified a JGroups-stack based JChannelFactory. To restore compatibility, we should revert this capability reference and in the event that a corresponding CommandDispatcherFactory capability does not exist, auto-create the missing JGroups channel resource required to create it.
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="udp" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9746?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-14176 to WFLY-9746:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9746 (was: JBEAP-14176)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
JMS
(was: Clustering)
(was: JMS)
Affects Version/s: 12.0.0.Alpha1
(was: 7.2.0.GA)
> Revert JGroups capability reference to ChannelFactory
> -----------------------------------------------------
>
> Key: WFLY-9746
> URL: https://issues.jboss.org/browse/WFLY-9746
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JMS
> Affects Versions: 12.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with:
> {code}
> 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.messaging-activemq.default",
> "org.wildfly.clustering.command-dispatcher-factory.tcp"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]",
> "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]"
> ]
> }
> 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager]
> service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default]
> 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management
> 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990
> {code}
> Configuration of jgroups and messaging-activemq subsystem:
> {code}
> <subsystem xmlns="urn:jboss:domain:jgroups:5.0">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> ...
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="org.jgroups.protocols.TCPPING">
> <property name="port_range">
> 10
> </property>
> <property name="num_initial_members">
> 1
> </property>
> <property name="initial_hosts">
> 127.0.0.1[9600]
> </property>
> <property name="timeout">
> 3000
> </property>
> </protocol>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </stacks>
> </subsystem>
> ....
> <subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
> <server name="default" persistence-enabled="true" id-cache-size="200000">
> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/>
> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="udp" refresh-timeout="10000"/>
> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/>
> ...
> </server>
> </subsystem>
> {code}
> Attaching the whole config: standalone-full-ha.xml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3566) Different results of disabling commands already disabled deployment
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3566?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-3566:
---------------------------------------
Warning message should be similar in both cases and this warning message should be user-friendly.
Anyway, this is not regression against EAP 7.1.
*Experiments for EAP 7.1:*
Domain:
{noformat}
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group ~/erase15/app01.war
Unexpected command 'deployment deploy-file --server-groups=main-server-group ~/erase15/app01.war'. Type 'help --commands' for the list of supported commands.
[domain@localhost:9990 /] deploy ~/erase15/app01.war --server-groups=main-server-group
[domain@localhost:9990 /] undeploy app01.war --keep-content --server-groups=main-server-group
[domain@localhost:9990 /] undeploy app01.war --keep-content --server-groups=main-server-group
[domain@localhost:9990 /]
{noformat}
Standalone:
{noformat}
[standalone@localhost:9990 /] deploy ~/erase15/app01.war
[standalone@localhost:9990 /] undeploy app01.war --keep-content
[standalone@localhost:9990 /] undeploy app01.war --keep-content
Undeploy failed: WFLYCTL0155: 'steps' may not be null
[standalone@localhost:9990 /]
{noformat}
> Different results of disabling commands already disabled deployment
> -------------------------------------------------------------------
>
> Key: WFCORE-3566
> URL: https://issues.jboss.org/browse/WFCORE-3566
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
>
> *Different command result of disabling already disabled deployment in standalone and domain mode*
> * In standalone return
> {noformat}
> WFLYCTL0155: 'steps' may not be null
> {noformat}
> * In domain return nothing, no warning or error
> {noformat}
> [standalone@localhost:9990 /] deployment info
> NAME RUNTIME-NAME PERSISTENT ENABLED STATUS
> cli-test-another-deploy.war cli-test-another-deploy.war true true OK
> cli-test-app1-deploy.war cli-test-app1-deploy.war true false STOPPED
> cli-test-app2-deploy.war cli-test-app2-deploy.war true true OK
> [standalone@localhost:9990 /] deployment disable cli-test-app1-deploy-all.war
> WFLYCTL0155: 'steps' may not be null
> [standalone@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] deployment info --server-groups=main-server-group
> NAME RUNTIME-NAME STATE
> cli-test-another-deploy-all.war cli-test-another-deploy-all.war enabled
> cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added
> cli-test-app2-deploy-all.war cli-test-app2-deploy-all.war not added
> cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled
> [domain@localhost:9990 /] deployment disable --server-groups=main-server-group cli-test-app1-deploy-all.war
> [domain@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3562) Deployment disable-all doesn't correct function at domain
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3562?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-3562:
---------------------------------------
I'm able to reproduce this issue with three deployments too. I attached deployments that I used.
This is not a regression against EAP 7.1, because legacy deploy commands works correctly, but new deployment command doesn't work in this scenario.
*These are my experiments:*
*New way:*
{noformat}
deployment deploy-file --server-groups=main-server-group ~/erase15/app01.war
deployment deploy-file --server-groups=main-server-group ~/erase15/app02.war
deployment deploy-file --server-groups=other-server-group,main-server-group ~/erase15/app03.war
deployment disable --server-groups=main-server-group app01.war
deployment info --server-group=main-server-group
deployment disable-all --all-relevant-server-groups
deployment info --server-group=main-server-group
{noformat}
WF master results (error occurs):
{noformat}
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group ~/erase15/app01.war
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group ~/erase15/app02.war
[domain@localhost:9990 /] deployment deploy-file --server-groups=other-server-group,main-server-group ~/erase15/app03.war
[domain@localhost:9990 /] deployment disable --server-groups=main-server-group app01.war
[domain@localhost:9990 /] deployment info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war enabled
app03.war app03.war enabled
[domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
[domain@localhost:9990 /] deployment info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war enabled
app03.war app03.war enabled
[domain@localhost:9990 /]
{noformat}
*Legacy way:*
{noformat}
deploy ~/erase15/app01.war --server-groups=main-server-group
deploy ~/erase15/app02.war --server-groups=main-server-group
deploy ~/erase15/app03.war --server-groups=other-server-group,main-server-group
undeploy app01.war --keep-content --server-groups=main-server-group
deployment-info --server-group=main-server-group
undeploy * --keep-content --server-groups=main-server-group
deployment-info --server-group=main-server-group
{noformat}
EAP 7.1 results (error doesn't occurs):
{noformat}
[mkopecky@dhcp-10-40-5-4 bin]$ ./jboss-cli.sh -c
[domain@localhost:9990 /] deploy ~/erase15/app01.war --server-groups=main-server-group
[domain@localhost:9990 /] deploy ~/erase15/app02.war --server-groups=main-server-group
[domain@localhost:9990 /] deploy ~/erase15/app03.war --server-groups=other-server-group,main-server-group
[domain@localhost:9990 /] undeploy app01.war --keep-content --server-groups=main-server-group
[domain@localhost:9990 /] deployment-info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war enabled
app03.war app03.war enabled
[domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group
[domain@localhost:9990 /] deployment-info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war added
app03.war app03.war added
[domain@localhost:9990 /]
{noformat}
WF master results (error doesn't occurs):
{noformat}
[domain@localhost:9990 /] deploy ~/erase15/app01.war --server-groups=main-server-group
[domain@localhost:9990 /] deploy ~/erase15/app02.war --server-groups=main-server-group
[domain@localhost:9990 /] deploy ~/erase15/app03.war --server-groups=other-server-group,main-server-group
[domain@localhost:9990 /] undeploy app01.war --keep-content --server-groups=main-server-group
[domain@localhost:9990 /] deployment-info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war enabled
app03.war app03.war enabled
[domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group
[domain@localhost:9990 /] deployment-info --server-group=main-server-group
NAME RUNTIME-NAME STATE
app01.war app01.war added
app02.war app02.war added
app03.war app03.war added
[domain@localhost:9990 /]
{noformat}
> Deployment disable-all doesn't correct function at domain
> ---------------------------------------------------------
>
> Key: WFCORE-3562
> URL: https://issues.jboss.org/browse/WFCORE-3562
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
> Attachments: app01.war, app02.war, app03.war
>
>
> Domain
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3562) Deployment disable-all doesn't correct function at domain
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3562?page=com.atlassian.jira.plugi... ]
Marek Kopecký updated WFCORE-3562:
----------------------------------
Attachment: app01.war
app02.war
app03.war
> Deployment disable-all doesn't correct function at domain
> ---------------------------------------------------------
>
> Key: WFCORE-3562
> URL: https://issues.jboss.org/browse/WFCORE-3562
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
> Attachments: app01.war, app02.war, app03.war
>
>
> Domain
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3569?page=com.atlassian.jira.plugi... ]
David Lloyd commented on WFCORE-3569:
-------------------------------------
[~brian.stansberry] this looks like the same issue you were seeing, right?
> NPE is shown in server shutdown
> -------------------------------
>
> Key: WFCORE-3569
> URL: https://issues.jboss.org/browse/WFCORE-3569
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, IO, Server
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: David Lloyd
> Priority: Critical
>
> NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
> Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
> {noformat}
> 13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
> at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
> at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
> at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3562) Deployment disable-all doesn't correct function at domain
by Vratislav Marek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3562?page=com.atlassian.jira.plugi... ]
Vratislav Marek commented on WFCORE-3562:
-----------------------------------------
[~jdenise], I am sure with my steps, you miss two next deployments.
I tray it again...
With two it worked as expected:
{noformat}
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group /media/Data/Repos/Remote/Public/wildfly-core/testsuite/domain/target/cli-test-app1-deploy-all.war
[domain@localhost:9990 /] deployment deploy-file --server-groups=other-server-group,main-server-group /media/Data/Repos/Remote/Public/wildfly-core/testsuite/domain/target/cli-test-app3-deploy-all.war
[domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
[domain@localhost:9990 /] deployment info --server-group=
failure-test-group ignored-profile ignored-sockets main-server-group minimal other-server-group reload-test-group
[domain@localhost:9990 /] deployment info --server-group=main-server-group
NAME RUNTIME-NAME STATE
cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added
cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war added
[domain@localhost:9990 /] deployment info --server-group=other-server-group
NAME RUNTIME-NAME STATE
cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war not added
cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war added
[domain@localhost:9990 /] deployment undeploy * --all-relevant-server-groups
[domain@localhost:9990 /] deployment info --server-group=other-server-group
[domain@localhost:9990 /]
{noformat}
But with 3 deployments doesn't:
{noformat}
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group /media/Data/Repos/Remote/Public/wildfly-core/testsuite/domain/target/cli-test-app1-deploy-all.war
[domain@localhost:9990 /] deployment deploy-file --server-groups=main-server-group /media/Data/Repos/Remote/Public/wildfly-core/testsuite/domain/target/cli-test-another-deploy-all.war
[domain@localhost:9990 /] deployment deploy-file --server-groups=other-server-group,main-server-group /media/Data/Repos/Remote/Public/wildfly-core/testsuite/domain/target/cli-test-app3-deploy-all.war
[domain@localhost:9990 /]
[domain@localhost:9990 /] deployment disable --server-groups=main-server-group cli-test-app1-deploy-all.war
[domain@localhost:9990 /]
[domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
[domain@localhost:9990 /] deployment info --server-group=main-server-group
NAME RUNTIME-NAME STATE
cli-test-another-deploy-all.war cli-test-another-deploy-all.war enabled
cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war added
cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled
[domain@localhost:9990 /] deployment info --server-group=other-server-group
NAME RUNTIME-NAME STATE
cli-test-another-deploy-all.war cli-test-another-deploy-all.war not added
cli-test-app1-deploy-all.war cli-test-app1-deploy-all.war not added
cli-test-app3-deploy-all.war cli-test-app3-deploy-all.war enabled
[domain@localhost:9990 /]
{noformat}
If I tested it with less than 4 before some deployments must be remaining installed.
> Deployment disable-all doesn't correct function at domain
> ---------------------------------------------------------
>
> Key: WFCORE-3562
> URL: https://issues.jboss.org/browse/WFCORE-3562
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Vratislav Marek
> Assignee: Jean-Francois Denise
>
> Domain
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --all-relevant-server-groups
> org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment.
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] deployment disable-all --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
> {noformat}
> [domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[
> (\"server-group\" => \"main-server-group\"),
> (\"deployment\" => \"cli-test-app2-deploy-all.war\")
> ]' not found"}}
> [domain@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by Chao Wang (JIRA)
Chao Wang created WFCORE-3569:
---------------------------------
Summary: NPE is shown in server shutdown
Key: WFCORE-3569
URL: https://issues.jboss.org/browse/WFCORE-3569
Project: WildFly Core
Issue Type: Bug
Components: CLI, Domain Management, IO, Server
Affects Versions: 4.0.0.Alpha8
Reporter: Chao Wang
Assignee: David Lloyd
Priority: Critical
NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
{noformat}
13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
at java.lang.Thread.run(Thread.java:748)
{noformat}
I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3568) Allow CLI output scrolling
by Chao Wang (JIRA)
Chao Wang created WFCORE-3568:
---------------------------------
Summary: Allow CLI output scrolling
Key: WFCORE-3568
URL: https://issues.jboss.org/browse/WFCORE-3568
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Affects Versions: 4.0.0.Alpha8
Reporter: Chao Wang
Assignee: Jean-Francois Denise
Mouse scrolling is forbidden to large CLI out. User has to press {{Down}} or {{Enter}} to navigate.
It would be nice to allow fast scrolling or {{PgUp}} / {{PgDn}}. e.g.
{noformat}
[standalone@localhost:9990 /] /core-service=capability-registry:read-resource
{
"outcome" => "success",
"result" => {
"capabilities" => [
{
"name" => "org.wildfly.batch.configuration",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=batch-jberet"]
},
{
"name" => "org.wildfly.batch.job.repository.in-memory",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=batch-jberet/in-memory-job-repository=in-memory"]
},
{
"name" => "org.wildfly.batch.thread.pool.batch",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=batch-jberet/thread-pool=batch"]
},
{
"name" => "org.wildfly.clustering.cache.default-group.ejb",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
},
{
"name" => "org.wildfly.clustering.cache.default-group.server",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=infinispan/cache-container=server"]
},
{
"name" => "org.wildfly.clustering.cache.default-group.web",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=infinispan/cache-container=web"]
},
{
"name" => "org.wildfly.clustering.cache.default-node-factory.ejb",
"dynamic" => false,
"scope" => "global",
"registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
},
{
"name" => "org.wildfly.clustering.cache.default-node-factory.server",
"dynamic" => false,
--More(2%)--
{noformat}
Also, after pressing {{Down}} or {{Enter}} to display more output, user can not press {{up}} to go up. User has to inconveniently use scroll up.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database
by Gail Badner (JIRA)
[ https://issues.jboss.org/browse/WFLY-9739?page=com.atlassian.jira.plugin.... ]
Gail Badner commented on WFLY-9739:
-----------------------------------
[~smarlow], I see https://hibernate.atlassian.net/browse/HHH-12259. Can this issue be rejected now?
> JPA / Hibernate: There is already an object named 'x' in the database
> ---------------------------------------------------------------------
>
> Key: WFLY-9739
> URL: https://issues.jboss.org/browse/WFLY-9739
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits
> Java version: 1.8.0_151
> SQL Server 2014
> Reporter: Eric SantAnna
> Assignee: Scott Marlow
> Attachments: sqljdbc4.jar, wildfly11-migration.zip
>
>
> I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update".
> This doesn't happen in my tests with 10.1.0.Final.
> Appearently, despite these Exceptions, all my applications are running ok.
> I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11.
> This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month