October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7384) Removal of messaging-activemq's server stops Infinispan services

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7384?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-7384: ------------------------------------ [~jmesnil] Sure - I'll have a look. > Removal of messaging-activemq's server stops Infinispan services > ---------------------------------------------------------------- > > Key: WFLY-7384 > URL: https://issues.jboss.org/browse/WFLY-7384 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Attachments: WFLY-7384.diff > > > This issue occurs after I fixed the issue for WFLY-7333 which ensures that all services related to a messaging-activemq server are stopped when the server is removed. > When I run the command to remove the server: > /subsystem=messaging-activemq/server=default:remove > I see logs in the app server about Infinispan services being stopped: > {noformat} > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel server > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000080: Disconnecting JGroups channel hibernate > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel web > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel server > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher for channel web > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000082: Stopping the RpcDispatcher for channel hibernate > 09:28:46,381 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.4.0 [c96316a7-9b4d-11e6-ab8c-b8f6b112daf7] stopped, uptime 18.904 seconds > {noformat} > There should be no reason than stopping the messaging server should stop such Infinispan services. The messaging-activemq subsystem has *no* dependency to Infinispan resources. > However both messaging-activemq and infinispan resources depends on JGroups resources. > I did a diff of the services dump before and after removing the messaging-activemq server (see attached file). > The Infinispan services are stopped as a consequence of stopping the jboss.messaging-activemq.default service. Before removing the server, this service is in this state: > {noformat} > Service \"jboss.messaging-activemq.default\" (class org.wildfly.extension.messaging.activemq.ActiveMQServerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.management.jmx, org.wildfly.clustering.jgroups.default-channel-factory, jboss.outbound-socket-binding.http, jboss.binding.http, jboss.http-upgrade-registry.default, jboss.path.manager, jboss.security.security-domain.other) > {noformat} > The only relation between this messaging server and the Infinispan resources is that they depend on the org.wildfly.clustering.jgroups.default-channel-factory service. Before removing the messaging server, this service is in the state: > {noformat} > Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) > {noformat} > After removing the messaging server, this service is in the state: > {noformat} > > Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) > {noformat} > I am not sure to understand why and when removing the jboss.messaging-activemq.default implies to remove the org.wildfly.clustering.jgroups.default-channel-factory service but there is no reason that removing any messaging-activemq resources should impact the state of Infinispan services -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7388) NullPointerException Adding FileSystemRealm with identities in a batch.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7388?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-7388: ---------------------------------------- This may be irrelevant but that "--commands" string looks odd as it has a "run-batch" with no preceding "batch". > NullPointerException Adding FileSystemRealm with identities in a batch. > ----------------------------------------------------------------------- > > Key: WFLY-7388 > URL: https://issues.jboss.org/browse/WFLY-7388 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > {{/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)}} > {noformat} > Step 21 : RUN /opt/jboss/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/bin/jboss-cli.sh --commands=embed-server\ --server-config=standalone-elytron.xml,run-batch\ --file=/opt/jboss/commands.txt,stop-embedded-server > ---> Running in fb3e83746136 > The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} > {noformat} > NullPointerException experienced randomly, initially this sounds like the service is not fully up by the time the first command completes. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7389) Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7389?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7389: --------------------------------- Summary: Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2 (was: Improve statistics-enabled="false" testing in infinispan subsystem for EAP 6.2) > Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2 > ----------------------------------------------------------------------------------------- > > Key: WFLY-7389 > URL: https://issues.jboss.org/browse/WFLY-7389 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7389) Improve statistics-enabled="false" testing in infinispan subsystem for EAP 6.2

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-7389: ------------------------------------ Summary: Improve statistics-enabled="false" testing in infinispan subsystem for EAP 6.2 Key: WFLY-7389 URL: https://issues.jboss.org/browse/WFLY-7389 Project: WildFly Issue Type: Task Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1883) Post-boot transition to/from acting as a master or slave HC must be done with management op execution locked out

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1883?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1883: ---------------------------------------- Assignee: Brian Stansberry > Post-boot transition to/from acting as a master or slave HC must be done with management op execution locked out > ---------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1883 > URL: https://issues.jboss.org/browse/WFCORE-1883 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > As part of WFCORE-338, a Candidate Domain Controller can shift between acting a master or acting as slave without requiring a reload or reboot. > However, after initial boot, a DCC can be handling management requests. Any transition between acting as a master or slave to the other role must ensure that in-process management requests are not disrupted and that no new management requests are able to access the management model or runtime services until the transition is complete. As a practical matter this likely means that the transition task(s) must acquire the exclusive management lock and hold it until the transition is complete. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7388) NullPointerException Adding FileSystemRealm with identities in a batch.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-7388: -------------------------------------- Summary: NullPointerException Adding FileSystemRealm with identities in a batch. Key: WFLY-7388 URL: https://issues.jboss.org/browse/WFLY-7388 Project: WildFly Issue Type: Bug Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 11.0.0.Alpha1 {{/subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add() /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add-attribute(name=Roles, value=["Admin","Guest"]) /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper)}} {noformat} Step 21 : RUN /opt/jboss/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/bin/jboss-cli.sh --commands=embed-server\ --server-config=standalone-elytron.xml,run-batch\ --file=/opt/jboss/commands.txt,stop-embedded-server ---> Running in fb3e83746136 The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} {noformat} NullPointerException experienced randomly, initially this sounds like the service is not fully up by the time the first command completes. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1606) Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1606: ---------------------------------------- Assignee: ehsavoie Hugonnet Emmanuel, please have a look at this, starting off with discussing a bit with [~dlofthouse]. I'm quite fine with fixing this by simply correcting the metadata, and not actual supporting allow-resource-service-restart=true. We should only go beyond that if: 1) The elytron replacements for these legacy security-realm resources will support allow-resource-service-restart=true *in core 3.0.0 / WF 11*. 2) Darran is up for reviewing a patch to add the support. Otherwise let's just fix the metadata. > Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1606 > URL: https://issues.jboss.org/browse/WFCORE-1606 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.10.Final > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Beta1 > > > When security-realm, which is set as http-interface security-realm in management-interfaces, is modified and operation used {allow-resource-service-restart=true} header then server is NOT in reload-required state but modified security realm does not work correctly until server is manually reloaded. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1552) Slaves should report the master's version in the domain model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1552?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1552: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Kabir Khan) > Slaves should report the master's version in the domain model > ------------------------------------------------------------- > > Key: WFCORE-1552 > URL: https://issues.jboss.org/browse/WFCORE-1552 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.2.0.CR2 > Reporter: Kabir Khan > Assignee: ehsavoie Hugonnet > > Setting up the mixed domain tests for an EAP7 slave, I get the following error : > {code} > SimpleMixedDomain700TestCase>SimpleMixedDomainTest.test00002_Versioning:139 expected:<{ > "management-major-version" => 4, > "management-micro-version" => 0, > "management-minor-version" => 1, > "name" => "Unnamed Domain", > "namespaces" => [], > "product-name" => "WildFly Full", > "product-version" => "10.1.0.Final-SNAPSHOT", > "release-codename" => "Kenny", > "release-version" => "2.2.0.CR2", > "schema-locations" => [] > }> but was:<{ > "management-major-version" => 4, > "management-micro-version" => 0, > "management-minor-version" => 1, > "name" => "Unnamed Domain", > "namespaces" => [], > "product-name" => "JBoss EAP", > "product-version" => "7.0.0.GA", > "release-codename" => "Kenny", > "release-version" => "2.1.2.Final-redhat-1", > "schema-locations" => [] > }> > {code} > The 'expected' is the WildFly master values, while the 'actual' are the slave values. product-name, product-version, release-codename and release-version on the slave should be the same as the master values. Once we upgrade to Wildfly Core 3.0.0 we should also check that the management-[major/minor/micro]-version attributes on the slave are the same as the DC's values as well (i.e 5.0.0 rather than 4.0.1) This is similar to WFLY-3228 back in the day. > This is probably caused by the SyncXXX handlers for pushing the domain config as operations (WFCORE-401) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-694) CLIENT-CERT mechanism is incorrectly called CLIENT_CERT

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-694?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-694: -------------------------------------- [~zrhoads] FYI > CLIENT-CERT mechanism is incorrectly called CLIENT_CERT > ------------------------------------------------------- > > Key: ELY-694 > URL: https://issues.jboss.org/browse/ELY-694 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta12 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-694) CLIENT-CERT mechanism is incorrectly called CLIENT_CERT

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-694: ------------------------------------ Summary: CLIENT-CERT mechanism is incorrectly called CLIENT_CERT Key: ELY-694 URL: https://issues.jboss.org/browse/ELY-694 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta12 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016