November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1748) Diagnostics: change size of printed views dynamically

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1748?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1748. ---------------------------- Resolution: Done Examples: probe.sh max-list-print-size=30 probe.sh max-list-print-size > Diagnostics: change size of printed views dynamically > ----------------------------------------------------- > > Key: JGRP-1748 > URL: https://issues.jboss.org/browse/JGRP-1748 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > Currently, when a view or digest is longer than Util.MAX_LIST_PRINT_SIZE (20 by default) elements, we don't print the entire list, but only the first 20 elements, followed by an ellipsis. Util.MAX_LIST_PRINT_SIZE is defined via system prop "max.list.print_size". > Use probe / JMX to dynamically change the value of Util.MAX_LIST_PRINT_SIZE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1748) Diagnostics: change size of printed views dynamically

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1748?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1748: --------------------------- Summary: Diagnostics: change size of printed views dynamically (was: Change size of printed views dynamically) > Diagnostics: change size of printed views dynamically > ----------------------------------------------------- > > Key: JGRP-1748 > URL: https://issues.jboss.org/browse/JGRP-1748 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > Currently, when a view or digest is longer than Util.MAX_LIST_PRINT_SIZE (20 by default) elements, we don't print the entire list, but only the first 20 elements, followed by an ellipsis. Util.MAX_LIST_PRINT_SIZE is defined via system prop "max.list.print_size". > Use probe / JMX to dynamically change the value of Util.MAX_LIST_PRINT_SIZE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2588) HC Main.getHostSystemProperties() does not handle additional equals in system properties properly

by Kabir Khan (JIRA)

Kabir Khan created WFLY-2588: -------------------------------- Summary: HC Main.getHostSystemProperties() does not handle additional equals in system properties properly Key: WFLY-2588 URL: https://issues.jboss.org/browse/WFLY-2588 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Beta1 Reporter: Kabir Khan Assignee: Brian Stansberry Fix For: 8.0.0.CR1 -Djava.security.policy==/Users/kabir/tmp/permit.policy (note the extra '=') is a valid setting to just use that policy file (unlike -Djava.security.policy=/Users/kabir/tmp/permit.policy which adds it to the system wide and user policies) Main.getHostSystemProperties() currently handles this in a way that the value becomes null, while it should be '=/Users/kabir/tmp/permit.policy' which causes this problem when starting up the servers {code} [Server:server-one] Exception in thread "main" java.security.AccessControlException: access denied (java.util.PropertyPermission module.path write) [Server:server-one] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:376) [Server:server-one] at java.security.AccessController.checkPermission(AccessController.java:549) [Server:server-one] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) [Server:server-one] at java.lang.System.setProperty(System.java:741) [Server:server-one] at org.jboss.modules.Main.main(Main.java:148) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-356?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-356: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1035685|https://bugzilla.redhat.com/show_bug.cgi?id=1035685] from NEW to ASSIGNED > KieScanner doesn't work on a KieContainer using a maven version range > --------------------------------------------------------------------- > > Key: DROOLS-356 > URL: https://issues.jboss.org/browse/DROOLS-356 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > > It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-356?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-356. -------------------------------- Fix Version/s: 6.0.1.Final Resolution: Done > KieScanner doesn't work on a KieContainer using a maven version range > --------------------------------------------------------------------- > > Key: DROOLS-356 > URL: https://issues.jboss.org/browse/DROOLS-356 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-356?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-356: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1035685 > KieScanner doesn't work on a KieContainer using a maven version range > --------------------------------------------------------------------- > > Key: DROOLS-356 > URL: https://issues.jboss.org/browse/DROOLS-356 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > > It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-356: ---------------------------------- Summary: KieScanner doesn't work on a KieContainer using a maven version range Key: DROOLS-356 URL: https://issues.jboss.org/browse/DROOLS-356 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1747) Diagnostics: provide managed operation to start/stop diagnostics

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1747?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1747. ---------------------------- Resolution: Done > Diagnostics: provide managed operation to start/stop diagnostics > ---------------------------------------------------------------- > > Key: JGRP-1747 > URL: https://issues.jboss.org/browse/JGRP-1747 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > Provide methods to start and stop the DiagnosticsHandler in TP, e.g. via JMX or byteman. This allows for delivery of a system with diagnostics disabled, and to dynamically enable it at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1746) Diagnostics: reset stats in all protocols

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1746?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1746. ---------------------------- Resolution: Done > Diagnostics: reset stats in all protocols > ----------------------------------------- > > Key: JGRP-1746 > URL: https://issues.jboss.org/browse/JGRP-1746 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Trivial > Fix For: 3.5 > > > Add a key to probe.sh (e.g. reset-all-stats) which calls resetStats() in all protocols, plus the channel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1749) Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port

by Bela Ban (JIRA)

Bela Ban created JGRP-1749: ------------------------------ Summary: Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port Key: JGRP-1749 URL: https://issues.jboss.org/browse/JGRP-1749 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.5 Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013