June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1612) Allow applying the same configuration changes to multiple Standalone nodes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1612?page=com.atlassian.jira.plugi... ] Sebastian Łaskawiec updated WFCORE-1612: ---------------------------------------- Summary: Allow applying the same configuration changes to multiple Standalone nodes (was: Add DMR support for Stanalone mode) > Allow applying the same configuration changes to multiple Standalone nodes > -------------------------------------------------------------------------- > > Key: WFCORE-1612 > URL: https://issues.jboss.org/browse/WFCORE-1612 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Sebastian Łaskawiec > Assignee: Brian Stansberry > > I would like to request a support for DMR commands in standalone mode. > The main motivation behind that is using WF based Projects (like Infinispan HotRod Server) in the Cloud. By using DMR we can ensure changing configuration on the fly, which is very important in our case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-106) Resources leak when an exception is thrown in "connect"

by Vasco Veloso (JIRA)

[ https://issues.jboss.org/browse/REMJMX-106?page=com.atlassian.jira.plugin... ] Vasco Veloso commented on REMJMX-106: ------------------------------------- Also note that is a regression error from the fix introduced by REMJMX-37 . > Resources leak when an exception is thrown in "connect" > ------------------------------------------------------- > > Key: REMJMX-106 > URL: https://issues.jboss.org/browse/REMJMX-106 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.1.Final > Environment: Wildfly 10.0.0.Final > Reporter: Dominique Toupin > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1612) Add DMR support for Stanalone mode

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1612?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1612: ------------------------------------- what exactly do you mean? Can you elaborate? DMR is backbone of all our management. Standalone and otherwise. You can already manage everything via cli / mgmt interface / http interface That is why I am not sure what you are really asking for. > Add DMR support for Stanalone mode > ---------------------------------- > > Key: WFCORE-1612 > URL: https://issues.jboss.org/browse/WFCORE-1612 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Sebastian Łaskawiec > Assignee: Brian Stansberry > > I would like to request a support for DMR commands in standalone mode. > The main motivation behind that is using WF based Projects (like Infinispan HotRod Server) in the Cloud. By using DMR we can ensure changing configuration on the fly, which is very important in our case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1066) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/WFLY-1066?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated WFLY-1066: -------------------------------------- Priority: Major (was: Minor) > Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING) > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1066 > URL: https://issues.jboss.org/browse/WFLY-1066 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: Server running in Domain mode > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > Labels: clustering, domain, jgroups > > It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode. > All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration. > The domain server will receive the information if a host-controller enrol and register server to a clustered server-group. > So the configuration of the initial_hosts can be done automatically to avoid old entries which cause unnecessary checks and ensure that all active servers are known. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1612) Add DMR support for Stanalone mode

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created WFCORE-1612: ------------------------------------------- Summary: Add DMR support for Stanalone mode Key: WFCORE-1612 URL: https://issues.jboss.org/browse/WFCORE-1612 Project: WildFly Core Issue Type: Feature Request Reporter: Sebastian Łaskawiec Assignee: Brian Stansberry I would like to request a support for DMR commands in standalone mode. The main motivation behind that is using WF based Projects (like Infinispan HotRod Server) in the Cloud. By using DMR we can ensure changing configuration on the fly, which is very important in our case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1611) CLI could stuck if SIGINT is send during authentication dialogue

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1611?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-5100 to WFCORE-1611: ------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1611 (was: JBEAP-5100) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.backlog.GA) Affects Version/s: 3.0.0.Alpha2 (was: 7.0.0.GA) > CLI could stuck if SIGINT is send during authentication dialogue > ---------------------------------------------------------------- > > Key: WFCORE-1611 > URL: https://issues.jboss.org/browse/WFCORE-1611 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha2 > Reporter: Chao Wang > Assignee: Chao Wang > > Interruption a CLI session with Ctrl+C during authentication dialogue could get CLI into unresponsive state. > *reproduce* > Either use a remote server, --no-local-auth cli script arg or remove a local element from ManagementRealm configuration > {code:diff} > <security-realms> > <security-realm name="ManagementRealm"> > <authentication> > - <local default-user="$local" skip-group-loading="true"/> > {code} > start a standalone server and launch a CLI > {noformat} > [pkremens@localhost] $ ./standalone.sh & > [pkremens@localhost] $ ./jboss-cli.sh > [disconnected /] connect > Authenticating against security realm: ManagementRealm > Username: <Press Ctrl+C here> > {noformat} > Could not connect message is printed, but process is not terminated and stuck at this point. > {noformat} > The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to http-remoting://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to http-remoting://localhost:9990. The connection timed out > {noformat} > Only way to recover the terminal is to SIGKILL the CLI process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6752) add trace logging to the SSO code in wildfly/undertow

by Ingo Weiss (JIRA)

Ingo Weiss created WFLY-6752: -------------------------------- Summary: add trace logging to the SSO code in wildfly/undertow Key: WFLY-6752 URL: https://issues.jboss.org/browse/WFLY-6752 Project: WildFly Issue Type: Enhancement Components: Security, Web (Undertow) Reporter: Ingo Weiss Assignee: Ingo Weiss Priority: Critical Fix For: 10.1.0.Final Please add trace logging to the SSO code in wildfly/undertow. For example, it would be helpful if the sso code logged that it was getting triggered, if re-authentication was happening, etc. This is going to be very difficult to support if we do not have this type of information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6741) Missing validation for messaging-activemq (journal-buffer-size)

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6741?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-6741: ----------------------------------- [~treblereel] What have you in mind? The only additional validation I can think of is to check that the size of the buffer for AIO journal must be a multiple of 512. > Missing validation for messaging-activemq (journal-buffer-size) > --------------------------------------------------------------- > > Key: WFLY-6741 > URL: https://issues.jboss.org/browse/WFLY-6741 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Dmitrii Tikhomirov > > There is no validation for journal-buffer-size attribute. > The following request shouldn't be successful: > {noformat} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:write-attribute(name=journal-buffer-size, value=-8L > { > "outcome" => "success", > } > [standalone@localhost:9990 /] reload > {noformat} > server.log > {noformat} > 15:11:57,787 ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ224000: Failure in initialisation: java.lang.IllegalArgumentException: initialCapacity: -8 (expectd: 0+) > at io.netty.buffer.AbstractByteBufAllocator.validate(AbstractByteBufAllocator.java:196) > at io.netty.buffer.AbstractByteBufAllocator.heapBuffer(AbstractByteBufAllocator.java:135) > at io.netty.buffer.Unpooled.buffer(Unpooled.java:135) > at org.apache.activemq.artemis.api.core.ActiveMQBuffers.fixedBuffer(ActiveMQBuffers.java:86) > at org.apache.activemq.artemis.core.io.buffer.TimedBuffer.<init>(TimedBuffer.java:108) > at org.apache.activemq.artemis.core.io.AbstractSequentialFileFactory.<init>(AbstractSequentialFileFactory.java:74) > at org.apache.activemq.artemis.core.io.aio.AIOSequentialFileFactory.<init>(AIOSequentialFileFactory.java:77) > at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.<init>(JournalStorageManager.java:251) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createStorageManager(ActiveMQServerImpl.java:1421) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:1540) > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:61) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:396) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:381) > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:199) > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:63) > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:97) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} > This issue can occur on other subsystem resources as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6751) add trace logging to the SSO code in wildfly/undertow

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-6751?page=com.atlassian.jira.plugin.... ] Ingo Weiss moved UNDERTOW-751 to WFLY-6751: ------------------------------------------- Project: WildFly (was: Undertow) Key: WFLY-6751 (was: UNDERTOW-751) Component/s: Security Web (Undertow) (was: Security) Fix Version/s: (was: 1.4.0.Beta1) (was: 2.0.0.Alpha2) (was: 1.3.23.Final) > add trace logging to the SSO code in wildfly/undertow > ----------------------------------------------------- > > Key: WFLY-6751 > URL: https://issues.jboss.org/browse/WFLY-6751 > Project: WildFly > Issue Type: Enhancement > Components: Security, Web (Undertow) > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Critical > > Please add trace logging to the SSO code in wildfly/undertow. > For example, it would be helpful if the sso code logged that it was getting triggered, if re-authentication was happening, etc. > This is going to be very difficult to support if we do not have this type of information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6751) add trace logging to the SSO code in wildfly/undertow

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-6751?page=com.atlassian.jira.plugin.... ] Ingo Weiss updated WFLY-6751: ----------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8926 (was: https://github.com/undertow-io/undertow/pull/395, https://github.com/wildfly/wildfly/pull/8926) > add trace logging to the SSO code in wildfly/undertow > ----------------------------------------------------- > > Key: WFLY-6751 > URL: https://issues.jboss.org/browse/WFLY-6751 > Project: WildFly > Issue Type: Enhancement > Components: Security, Web (Undertow) > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Critical > > Please add trace logging to the SSO code in wildfly/undertow. > For example, it would be helpful if the sso code logged that it was getting triggered, if re-authentication was happening, etc. > This is going to be very difficult to support if we do not have this type of information. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016