October 2016 - jboss-jira - Jboss List Archives

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

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7384?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-7384: ------------------------------ Attachment: WFLY-7384.diff > 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-7384) Removal of messaging-activemq's server stops Infinispan services

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-7384: --------------------------------- Summary: 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 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] (JBJCA-1335) Add protection in RaXmlDeployer to prevent from loading xml resource

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1335?page=com.atlassian.jira.plugin... ] Chao Wang updated JBJCA-1335: ----------------------------- Fix Version/s: WildFly/IronJacamar 1.3.5.Final > Add protection in RaXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1335 > URL: https://issues.jboss.org/browse/JBJCA-1335 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Priority: Minor > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > If we place a -ra.xml in jar file, the class RaXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in RaXmlDeployer . > The second goal is to provide ability of overring RaXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.3

by Emmanuel Bernard (JIRA)

[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ] Emmanuel Bernard commented on WFLY-6854: ---------------------------------------- Do we have a go? BTW these requirement documents are nice when you start thinking about the feature but here Hibernate works differently, we do things much more iteratively and retro explaining everything would be a waste of energy. EAP7-582 explains very well our main reasons I think. > Upgrade Hibernate ORM to 5.1.3 > ------------------------------- > > Key: WFLY-6854 > URL: https://issues.jboss.org/browse/WFLY-6854 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Emmanuel Bernard > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > > This is a follow up on WFLY-6682. > After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users. > We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it. > PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-688) Elytron Properties realm parses password with "=" incorrectly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-688?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-688: ----------------------------- Affects Version/s: 1.1.0.Beta11 > Elytron Properties realm parses password with "=" incorrectly > ------------------------------------------------------------- > > Key: ELY-688 > URL: https://issues.jboss.org/browse/ELY-688 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta11 > Reporter: Ondrej Lukas > Assignee: Dmitrii Tikhomirov > > In case when Elytron properties-realm uses plain-text properties file and password includes {{=}} sign then username/password is parsing incorrectly. In case when properties file contains line as {{A=B=C}} then Elytron parses it as user {{A=B}} with password {{C}}. Correct behavior should be user {{A}} with password {{B=C}}. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-688) Elytron Properties realm parses password with "=" incorrectly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-688?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas moved WFLY-7369 to ELY-688: ---------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-688 (was: WFLY-7369) Component/s: Realms (was: Security) > Elytron Properties realm parses password with "=" incorrectly > ------------------------------------------------------------- > > Key: ELY-688 > URL: https://issues.jboss.org/browse/ELY-688 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Ondrej Lukas > Assignee: Dmitrii Tikhomirov > > In case when Elytron properties-realm uses plain-text properties file and password includes {{=}} sign then username/password is parsing incorrectly. In case when properties file contains line as {{A=B=C}} then Elytron parses it as user {{A=B}} with password {{C}}. Correct behavior should be user {{A}} with password {{B=C}}. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1335) Add protection in RaXmlDeployer to prevent from loading xml resource

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1335?page=com.atlassian.jira.plugin... ] Chao Wang updated JBJCA-1335: ----------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/584, https://github.com/ironjacamar/ironjacamar/pull/583 (was: https://github.com/ironjacamar/ironjacamar/pull/584) > Add protection in RaXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1335 > URL: https://issues.jboss.org/browse/JBJCA-1335 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Priority: Minor > Fix For: 1.2.8.Final > > > If we place a -ra.xml in jar file, the class RaXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in RaXmlDeployer . > The second goal is to provide ability of overring RaXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1333) Add protection in DsXmlDeployer to prevent from loading xml resource

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1333?page=com.atlassian.jira.plugin... ] Chao Wang updated JBJCA-1333: ----------------------------- Fix Version/s: WildFly/IronJacamar 1.3.5.Final > Add protection in DsXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1333 > URL: https://issues.jboss.org/browse/JBJCA-1333 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Assignee: Stefano Maestri > Priority: Minor > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > If we place a datasource.xml in a jar file, the class DsXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in DsXmlDeployer. > The second goal is to provide ability of overring DsXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1333) Add protection in DsXmlDeployer to prevent from loading xml resource

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1333?page=com.atlassian.jira.plugin... ] Chao Wang updated JBJCA-1333: ----------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/576, https://github.com/ironjacamar/ironjacamar/pull/580 (was: https://github.com/ironjacamar/ironjacamar/pull/576) > Add protection in DsXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1333 > URL: https://issues.jboss.org/browse/JBJCA-1333 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Assignee: Stefano Maestri > Priority: Minor > Fix For: 1.2.8.Final > > > If we place a datasource.xml in a jar file, the class DsXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in DsXmlDeployer. > The second goal is to provide ability of overring DsXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1895) Undertow 1.4.4.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-1895: -------------------------------------- Summary: Undertow 1.4.4.Final Key: WFCORE-1895 URL: https://issues.jboss.org/browse/WFCORE-1895 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas -- 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