January 2018 - jboss-jira - Jboss List Archives

[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)

7 years, 8 months

1
0
0 / 0

[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)

7 years, 8 months

1
0
0 / 0

[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)

7 years, 8 months

1
0
0 / 0

[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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2268) Add more fine-grained control on all assets

by Alexandre Porcelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2268?page=com.atlassian.jira.plugi... ] Alexandre Porcelli commented on DROOLS-2268: -------------------------------------------- I don't see permission per file happening any time soon. > Add more fine-grained control on all assets > ------------------------------------------- > > Key: DROOLS-2268 > URL: https://issues.jboss.org/browse/DROOLS-2268 > Project: Drools > Issue Type: Enhancement > Components: Artifact Repository > Affects Versions: 6.5.0.Final > Reporter: Richard Bourner > Assignee: Michael Anstis > Priority: Minor > > Currently, permissions within Business Central are only at projects level. > It would be interesting to be able to enable permissions at a more fine-grained level. > For instance, in a single project of one repository, having some people with read-only access on some assets, and other people have read/write access to the same assets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar resolved WFLY-9572. ---------------------------------- Fix Version/s: 12.0.0.Alpha1 Resolution: Done > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > Tracking issue for speeding up clustering testsuite. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9572: -------------------------------------- All incorporated issues are resolved, there is a couple of follow up Jiras that will follow to expand the testsuite. > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > Tracking issue for speeding up clustering testsuite. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Priority: Critical (was: Major) > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > The core of the problem is that since all cases run against 2-node cluster a remote get(..) is never being tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Fix Version/s: (was: 12.0.0.Alpha1) > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Description: The core of the problem is that since all cases run against 2-node cluster a remote get(..) is never being tested given that numOwners defaults to 2. (was: The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2.) > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The core of the problem is that since all cases run against 2-node cluster a remote get(..) is never being tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018