November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11374: ------------------------------------ Hi [~jason.greene], attached few more logs for your analysis. [^slave-server-linux.log] [^slave-server-windows.log] [^master-server-linux.log] [^master-server-windows.log] > Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Critical > Attachments: master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11374: ------------------------------- Priority: Blocker (was: Critical) > Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Blocker > Attachments: master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11383) [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars

by Tomas Hofman (Jira)

Tomas Hofman created WFLY-11383: ----------------------------------- Summary: [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars Key: WFLY-11383 URL: https://issues.jboss.org/browse/WFLY-11383 Project: WildFly Issue Type: Bug Components: Security Reporter: Tomas Hofman Assignee: Tomas Hofman Currently if you have jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar on your module path, jvm complains as both jars export package org.jboss.security.negotiation.spnego which violates the modules contract where only one module (jar) can provide single package. example error that jvm prints {noformat} Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package org.jboss.security.negotiation.spnego to module wildfly.clustering.common {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9855) [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-9855?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-9855: ------------------------------------ I'm checking this out. --list-modules works for me, but --validate-modules gives an error. > [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars > ----------------------------------------------------------------------------- > > Key: WFLY-9855 > URL: https://issues.jboss.org/browse/WFLY-9855 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > Priority: Critical > > Currently if you have > jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar > on your module path, jvm complains as both jars export package org.jboss.security.negotiation.spnego > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package org.jboss.security.negotiation.spnego to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9855) [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-9855?page=com.atlassian.jira.plugin.... ] Tomas Hofman reassigned WFLY-9855: ---------------------------------- Assignee: Tomas Hofman > [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars > ----------------------------------------------------------------------------- > > Key: WFLY-9855 > URL: https://issues.jboss.org/browse/WFLY-9855 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > Assignee: Tomas Hofman > Priority: Critical > > Currently if you have > jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar > on your module path, jvm complains as both jars export package org.jboss.security.negotiation.spnego > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package org.jboss.security.negotiation.spnego to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11142) Regression in SOAP over JMS when WF13 and WF14 are communicating

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11142?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11142: ------------------------------------ [~kabirkhan] Only one direction si fixed with artemis upgrade: WF13.0.0.Final client(artemis 1.5.5.jbossorg-012) against WF14.0.1.Final server (artemis 2.6.3.jbossorg-001) is broken, as reported in this jira WF13.0.0.Final client(artemis 1.5.5.jbossorg-012) against WF15.0.0.CR1-SNAPSHOT server (artemis 2.6.3.jbossorg-013) is working now, fixed by WFLY-11143 WF14.0.1.Final client(artemis 2.6.3.jbossorg-001) against WF13.0.0.Final server(artemis 1.5.5.jbossorg-012) is broken, as reported in this jira WF15.0.0.CR1-SNAPSHOT client (artemis 2.6.3.jbossorg-013) against WF13.0.0.Final server(artemis 1.5.5.jbossorg-012) *is still broken* > Regression in SOAP over JMS when WF13 and WF14 are communicating > ---------------------------------------------------------------- > > Key: WFLY-11142 > URL: https://issues.jboss.org/browse/WFLY-11142 > Project: WildFly > Issue Type: Bug > Components: JMS, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Jeff Mesnil > Priority: Major > > There is a regression visible in JBossWS testsuite in SOAP over JMS test when client side and server side are WF13 and WF14 or vice-versa, in other words it is affecting backward and forward compatibility. > The cause was identified as Artemis upgrade from 1.5.5 to 2.6.3, there is ongoing investigation for gathering more details. > Exception in case of new client and old server: > {code:java} > Exception while processing jms message in cxf. Rolling back: javax.jms.JMSRuntimeException: Invalid address queue://jms.queue.testQueue > at org.apache.activemq.artemis.jms.client.ActiveMQDestination.fromAddress(ActiveMQDestination.java:119) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getJMSReplyTo(ActiveMQMessage.java:356) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.cxf.transport.jms.JMSMessageHeadersType.getDestName(JMSMessageHeadersType.java:363) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at org.apache.cxf.transport.jms.JMSMessageHeadersType.read(JMSMessageHeadersType.java:358) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at org.apache.cxf.transport.jms.JMSMessageHeadersType.from(JMSMessageHeadersType.java:335) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at org.apache.cxf.transport.jms.JMSMessageUtils.asCXFMessage(JMSMessageUtils.java:64) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:237) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at org.apache.cxf.transport.jms.util.PollingMessageListenerContainer$Poller.run(PollingMessageListenerContainer.java:84) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_181] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_181] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3074) Implement placeholder mechanism in core-grids

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3074?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3074. ------------------------------------ > Implement placeholder mechanism in core-grids > --------------------------------------------- > > Key: DROOLS-3074 > URL: https://issues.jboss.org/browse/DROOLS-3074 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > > Refactor custom placeholder mechanism done into Test Scenario (Preview) asset ( https://github.com/kiegroup/drools-wb/pull/951 ) and move it to core-grids -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11382) MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-11382?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-11382: ------------------------------------- Description: MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants Constants introduced in https://issues.jboss.org/browse/WFCORE-4204 was:MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants > MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants > ------------------------------------------------------------------------------ > > Key: WFLY-11382 > URL: https://issues.jboss.org/browse/WFLY-11382 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > > MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants > Constants introduced in https://issues.jboss.org/browse/WFCORE-4204 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11382) MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFLY-11382: ---------------------------------------- Summary: MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants Key: WFLY-11382 URL: https://issues.jboss.org/browse/WFLY-11382 Project: WildFly Issue Type: Bug Components: MP Metrics Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda MP Metrics subsystem should use org.jboss.as.server.deployment.Phase constants -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4232) Upgrade JBoss Modules to 1.8.7.Final

by David Lloyd (Jira)

David Lloyd created WFCORE-4232: ----------------------------------- Summary: Upgrade JBoss Modules to 1.8.7.Final Key: WFCORE-4232 URL: https://issues.jboss.org/browse/WFCORE-4232 Project: WildFly Core Issue Type: Component Upgrade Components: Modules Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018