November 2013 - jboss-jira - Jboss List Archives

[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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1748) Change size of printed views dynamically

by Bela Ban (JIRA)

Bela Ban created JGRP-1748: ------------------------------ Summary: 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

12 years, 7 months

1
0
0 / 0

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

by Bela Ban (JIRA)

Bela Ban created JGRP-1747: ------------------------------ Summary: 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

12 years, 7 months

1
0
0 / 0

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

by Bela Ban (JIRA)

Bela Ban created JGRP-1746: ------------------------------ Summary: 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2587) ManagedServerBootCmdFactory alters system property values

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2587: -------------------------------------- Summary: ManagedServerBootCmdFactory alters system property values Key: WFLY-2587 URL: https://issues.jboss.org/browse/WFLY-2587 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 8.0.0.CR1 When ManagedServerBootCmdFactory iterates through system properties to use in the server launch command it adds a value of "true" for any properties that have no value. This is incorrect. In particular it breaks SecurityManager usage as -Djava.security.manager is a valid setting while -Djava.security.manager=true will result in [Host Controller] 15:09:01,758 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-one 15:10:55,691 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-one' [Server:server-one] Error occurred during initialization of VM [Server:server-one] java.lang.InternalError: Could not create SecurityManager: true [Server:server-one] at sun.misc.Launcher.<init>(Launcher.java:106) [Server:server-one] at sun.misc.Launcher.<clinit>(Launcher.java:57) [Server:server-one] at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1486) [Server:server-one] at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1468) [Server:server-one] -- 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

12 years, 7 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 2013