December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4250) CLI, terminal can be corrupted during Ctrl-C

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFCORE-4250: -------------------------------------------- Summary: CLI, terminal can be corrupted during Ctrl-C Key: WFCORE-4250 URL: https://issues.jboss.org/browse/WFCORE-4250 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise We still have a window where the terminal can be set in rawMode at exit time. This is a race between the main thread and the aesh thread that sets back the attributes before the process exit. This is related to the fix made for WFCORE-3748. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11483) Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11483?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11483: --------------------------------------- Looks this one is similar to https://issues.jboss.org/browse/JBEAP-12126. > Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11483 > URL: https://issues.jboss.org/browse/WFLY-11483 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final, 14.0.0.Final > Reporter: Srinivas ev > Assignee: Martyn Taylor > Priority: Major > > Issue - Master should announce backup even when data and tmp folders are deleted during restart of master during failback. > Scenario - > 1. Master and LIVEQ are started. > 2. LIVEQ announces backup. > 3. Master is shutdown. > 4. LIVEQ acts as master. > 5. Master is started. Start script will have delete commands for tmp and data folder under standalone directory. > 6. Fails to announce backup and starts as independent servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11483) Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11483?page=com.atlassian.jira.plugin... ] Miroslav Novak reassigned WFLY-11483: ------------------------------------- Assignee: Martyn Taylor (was: Jason Greene) > Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11483 > URL: https://issues.jboss.org/browse/WFLY-11483 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Martyn Taylor > Priority: Major > > Issue - Master should announce backup even when data and tmp folders are deleted during restart of master during failback. > Scenario - > 1. Master and LIVEQ are started. > 2. LIVEQ announces backup. > 3. Master is shutdown. > 4. LIVEQ acts as master. > 5. Master is started. Start script will have delete commands for tmp and data folder under standalone directory. > 6. Fails to announce backup and starts as independent servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.1.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: ------------------------------------ Created - https://issues.jboss.org/browse/WFLY-11483 > Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: active standalone full ha.xml, master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, rotateserver_active.log, rotateserver_active.log, rotateserver_backup.log, rotateserver_slave.log, slave standalone full ha.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 > Few logs I found which may be impacting and I am not clear - > 1.2018-11-21 14:28:07,238 TRACE [org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@38e819b6-2112524495)) Setting up bridge between TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-30 and ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-41], discoveryGroupConfiguration=null]: java.lang.Exception: trace > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.<init>(ClusterConnectionBridge.java:129) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.createNewRecord(ClusterConnectionImpl.java:778) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:698) > at org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:264) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11483) Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11483?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11483: ------------------------------- Component/s: JMS > Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11483 > URL: https://issues.jboss.org/browse/WFLY-11483 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Major > > Issue - Master should announce backup even when data and tmp folders are deleted during restart of master during failback. > Scenario - > 1. Master and LIVEQ are started. > 2. LIVEQ announces backup. > 3. Master is shutdown. > 4. LIVEQ acts as master. > 5. Master is started. Start script will have delete commands for tmp and data folder under standalone directory. > 6. Fails to announce backup and starts as independent servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11483) Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11483?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11483: ------------------------------- Affects Version/s: 10.1.0.Final > Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11483 > URL: https://issues.jboss.org/browse/WFLY-11483 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Major > > Issue - Master should announce backup even when data and tmp folders are deleted during restart of master during failback. > Scenario - > 1. Master and LIVEQ are started. > 2. LIVEQ announces backup. > 3. Master is shutdown. > 4. LIVEQ acts as master. > 5. Master is started. Start script will have delete commands for tmp and data folder under standalone directory. > 6. Fails to announce backup and starts as independent servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11483) Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability

by Srinivas ev (Jira)

Srinivas ev created WFLY-11483: ---------------------------------- Summary: Master Artemis in Wildfly 10.1.0.Final fails to announce backup if tmp and data folders are deleted during master restart - High Availability Key: WFLY-11483 URL: https://issues.jboss.org/browse/WFLY-11483 Project: WildFly Issue Type: Bug Reporter: Srinivas ev Assignee: Jason Greene Issue - Master should announce backup even when data and tmp folders are deleted during restart of master during failback. Scenario - 1. Master and LIVEQ are started. 2. LIVEQ announces backup. 3. Master is shutdown. 4. LIVEQ acts as master. 5. Master is started. Start script will have delete commands for tmp and data folder under standalone directory. 6. Fails to announce backup and starts as independent servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4249) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4249?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4249: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3612 > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-4249 > URL: https://issues.jboss.org/browse/WFCORE-4249 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Fix For: 8.0.0.Beta1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10997) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-10997?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10997: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3612) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-10997 > URL: https://issues.jboss.org/browse/WFLY-10997 > Project: WildFly > Issue Type: Bug > Components: Remoting > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4249) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4249?page=com.atlassian.jira.plugi... ] Jeff Mesnil moved WFLY-11482 to WFCORE-4249: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4249 (was: WFLY-11482) Component/s: Remoting (was: Remoting) > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-4249 > URL: https://issues.jboss.org/browse/WFCORE-4249 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Lin Gao > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Fix For: 8.0.0.Beta1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups > Using WildFlyInitialContextFactory and calling a remote EJB server. > Observations: > 1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties. > Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected > 2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first). > If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 December 2018