June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1614) Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1614?page=com.atlassian.jira.plugi... ] Petr Kremensky commented on WFCORE-1614: ---------------------------------------- Nice, that should do the job. > Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts) > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-1614 > URL: https://issues.jboss.org/browse/WFCORE-1614 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha3 > > Attachments: test.cli > > > We are proposing here to add a Cli option (command line option and an XML element) to make the CLI to echo the command and its options in non interactive mode. This will help to match a given command and its output. > For example, the "ls -l" command output would be: > [standalone@localhost:9990 /] ls -l > ATTRIBUTE VALUE TYPE > launch-type STANDALONE STRING > management-major-version 5 INT > management-micro-version 0 INT > management-minor-version 0 INT > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1617) Tab completion is doesn't work for cli variables and properties

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1617?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-1617: ------------------------------ Labels: (was: downstream_dependency) > Tab completion is doesn't work for cli variables and properties > --------------------------------------------------------------- > > Key: WFCORE-1617 > URL: https://issues.jboss.org/browse/WFCORE-1617 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha2 > Reporter: Chao Wang > Assignee: Chao Wang > > CLI tab completion doesn't work for CLI variables. > Add a CLI variable: > {noformat} > set myvar=/subsystem=datasources/data-source=ExampleDS > [standalone@embedded /] $myvar:read-resource > { > "outcome" => "success", > "result" => { > ... > {noformat} > Now try to use tab completion > *actual* > {noformat} > [standalone@embedded /] $myvar:read<TAB> > [standalone@embedded /] $myvar:readread-<TAB> > [standalone@embedded /] $myvar:readread- > 'readread-' is not a valid operation name. > {noformat} > *expected* > {noformat} > [standalone@embedded /] $myvar:read<TAB> > [standalone@embedded /] $myvar:read-resource > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1614) Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1614?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1614: ---------------------------------------------- By deferring the output of the command at execution time (and not declaration time), I am getting the following output that should match what you are expecting: [disconnected /] embed-server [standalone@embedded /] ls system-property [standalone@embedded /] try [standalone@embedded /] :read-attribute(name=foo) [standalone@embedded /] /system-property=catch:add(value=bar) {"outcome" => "success"} [standalone@embedded /] /system-property=finally:add(value=bar) {"outcome" => "success"} [standalone@embedded /] /system-property=*:read-resource { "outcome" => "success", "result" => [ { "address" => [("system-property" => "catch")], "outcome" => "success", "result" => {"value" => "bar"} }, { "address" => [("system-property" => "finally")], "outcome" => "success", "result" => {"value" => "bar"} } ] } [standalone@embedded /] if (outcome == success) of /system-property=catch:read-attribute(name=value) [standalone@embedded /] set prop=Catch\ block\ was\ executed [standalone@embedded /] /system-property=finally:write-attribute(name=value, value=if) {"outcome" => "success"} [standalone@embedded /] reload > Requesting CLI Equivalent of Remote Echo / set -x in non-interactive mode (from within scripts) > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-1614 > URL: https://issues.jboss.org/browse/WFCORE-1614 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha3 > > Attachments: test.cli > > > We are proposing here to add a Cli option (command line option and an XML element) to make the CLI to echo the command and its options in non interactive mode. This will help to match a given command and its output. > For example, the "ls -l" command output would be: > [standalone@localhost:9990 /] ls -l > ATTRIBUTE VALUE TYPE > launch-type STANDALONE STRING > management-major-version 5 INT > management-micro-version 0 INT > management-minor-version 0 INT > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2083) Specifying prefix in S3_PING or GOOGLE_PING causes property validation failures

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2083?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2083. ---------------------------- Resolution: Done Removed the check: people have to know what they're doing > Specifying prefix in S3_PING or GOOGLE_PING causes property validation failures > ------------------------------------------------------------------------------- > > Key: JGRP-2083 > URL: https://issues.jboss.org/browse/JGRP-2083 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.9 > Reporter: Alan Field > Assignee: Bela Ban > Fix For: 3.6.10, 4.0 > > > S3_PING.validateProperties() has a check to verify that both location and prefix are not set, but the superclass FILE_PING sets the value for location. In order to use prefix, the location property has to be set to null which is not possible in all cases. See ISPN-5097 for details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook)

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2063: --------------------------- Fix Version/s: 3.6.11 (was: 3.6.10) > JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) > ------------------------------------------------------------------------------------ > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Bela Ban > Fix For: 3.6.11, 4.0 > > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook)

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2063: -------------------------------- [~rhusar] I want to release 3.6.10 today, is this a quick change? > JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) > ------------------------------------------------------------------------------------ > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Bela Ban > Fix For: 3.6.10, 4.0 > > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2029) SEQUENCER locks itself from receiving messages

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2029?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2029: --------------------------- Fix Version/s: 3.6.11 (was: 3.6.10) > SEQUENCER locks itself from receiving messages > ---------------------------------------------- > > Key: JGRP-2029 > URL: https://issues.jboss.org/browse/JGRP-2029 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: two nodes cluster environment, we are using infinispan 7.1.1 with JGroups 3.6.1-FINAL inside. > Reporter: Sean Guo > Assignee: Bela Ban > Fix For: 3.6.11, 4.0 > > Attachments: filtered_threads.txt, jgroups-tcp.xml > > > I attached the filtered thread dump and the jgroups-tcp.xml from one node. > If I read the code correctly, all the threads reading message from Socket are blocked(INT-1...INT-4) and they are waiting the lock owned by #489 thread. > Please check whether this is a bug or configuration problem. Currently we have to remove the SEQUENCER from JGroups' protocol stack. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2029) SEQUENCER locks itself from receiving messages

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2029?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2029: -------------------------------- You have a somewhat unusual configuration, e.g. * SEQUENCER is now where it is supposed to be (below FRAG2) * FLUSH is in the config; this combo has never been tested. I suggest remove FLUSH * PEER_LOCK: not recommened, CENTRAL_LOCK is the recommended lock protocol > SEQUENCER locks itself from receiving messages > ---------------------------------------------- > > Key: JGRP-2029 > URL: https://issues.jboss.org/browse/JGRP-2029 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: two nodes cluster environment, we are using infinispan 7.1.1 with JGroups 3.6.1-FINAL inside. > Reporter: Sean Guo > Assignee: Bela Ban > Fix For: 3.6.11, 4.0 > > Attachments: filtered_threads.txt, jgroups-tcp.xml > > > I attached the filtered thread dump and the jgroups-tcp.xml from one node. > If I read the code correctly, all the threads reading message from Socket are blocked(INT-1...INT-4) and they are waiting the lock owned by #489 thread. > Please check whether this is a bug or configuration problem. Currently we have to remove the SEQUENCER from JGroups' protocol stack. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2069) UNICAST3: bypass or remove when running over TCP

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2069?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2069: --------------------------- Fix Version/s: 3.6.11 (was: 3.6.10) > UNICAST3: bypass or remove when running over TCP > ------------------------------------------------ > > Key: JGRP-2069 > URL: https://issues.jboss.org/browse/JGRP-2069 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.11, 4.0 > > > When running over TCP as transport, UNICAST3 is still required: while TCP/IP retransmits messages reliably and also provides sender-FIFO ordering, the receiver's thread pool might be exhausted and thus the message might get rejected. > However, *if* the regular and OOB thread pools are disabled, we could actually bypass (or completely remove) UNICAST3. If messages get dropped by a protocol further up the stack, however, there will be no retransmission in this case. > SOLUTION: > * Document this behavior > * Emit an INFO message (or automatically bypass UNICAST3) when run over a TCP transport and both OOB and regular pools are disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2066) Probe: sort attributes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2066?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2066. ---------------------------- Resolution: Done > Probe: sort attributes > ---------------------- > > Key: JGRP-2066 > URL: https://issues.jboss.org/browse/JGRP-2066 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.10, 4.0 > > > The output of probe is easier to read if all attributes are sorted by name -- 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