March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3097) Allow user configuration of log files for JDR to omit

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/WFLY-3097?page=com.atlassian.jira.plugin.... ] James Livingston updated WFLY-3097: ----------------------------------- Summary: Allow user configuration of log files for JDR to omit (was: Allow user configuration of omitted log files) > Allow user configuration of log files for JDR to omit > ----------------------------------------------------- > > Key: WFLY-3097 > URL: https://issues.jboss.org/browse/WFLY-3097 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JDR > Affects Versions: 8.0.0.Final > Reporter: James Livingston > Assignee: Jesse Jaggars > > AS7Plugin gathers all *.log files and does not currently provide a way of omitting them. It would be useful to be able to provide a list that were skipped, if they contain sensitive application information. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-448) Traiting non-declared POJOS prevents the execution of WM actions from outside the WM

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-448: ------------------------------------- Summary: Traiting non-declared POJOS prevents the execution of WM actions from outside the WM Key: DROOLS-448 URL: https://issues.jboss.org/browse/DROOLS-448 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.1.0.Beta1, 6.0.1.Final, 6.0.0.Final, 5.6.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Fix For: 6.1.0.Final When a trait is applied to non-declared bean, a transparent proxy is created and the handle is updated accordingly. However, this prevents the lookup of the handle using the original object as a key. The proxy creation should be avoided. See also PLANNER-229 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-448) Traiting non-declared POJOS prevents the execution of WM actions from outside the WM

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-448?page=com.atlassian.jira.plugin... ] Davide Sottara reassigned DROOLS-448: ------------------------------------- Assignee: Davide Sottara (was: Mark Proctor) > Traiting non-declared POJOS prevents the execution of WM actions from outside the WM > ------------------------------------------------------------------------------------ > > Key: DROOLS-448 > URL: https://issues.jboss.org/browse/DROOLS-448 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > Fix For: 6.1.0.Final > > > When a trait is applied to non-declared bean, a transparent proxy is created and the handle is updated accordingly. However, this prevents the lookup of the handle using the original object as a key. > The proxy creation should be avoided. > See also PLANNER-229 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2899) Help and error messages in Main classes should be printed raw

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2899?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2899: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1072224|https://bugzilla.redhat.com/show_bug.cgi?id=1072224] from NEW to POST > Help and error messages in Main classes should be printed raw > ------------------------------------------------------------- > > Key: WFLY-2899 > URL: https://issues.jboss.org/browse/WFLY-2899 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.1.Final > > > The help in standalone and host-controller main methods gets printed after {{System.out}} and {{System.err}} have been captured by jboss-stdio. This leads the help and errors being printed in a log manager format rather than just the raw text. > Example output: > {code} > [jperkins@jperkins-rh wildfly]$ ./build/target/wildfly-8.0.0.Final-SNAPSHOT/bin/standalone.sh -help > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jperkins/projects/jboss/as/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT > JAVA: java > JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > 15:31:43,895 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final > 15:31:44,918 INFO [stdout] (main) > 15:31:44,918 INFO [stdout] (main) Usage: standalone.sh [args...] > 15:31:44,918 INFO [stdout] (main) where args include: > 15:31:44,918 INFO [stdout] (main) --admin-only Set the server's running type to > 15:31:44,919 INFO [stdout] (main) ADMIN_ONLY causing it to open > 15:31:44,919 INFO [stdout] (main) administrative interfaces and accept > 15:31:44,919 INFO [stdout] (main) management requests but not start other > 15:31:44,920 INFO [stdout] (main) runtime services or accept end user > 15:31:44,920 INFO [stdout] (main) requests. > 15:31:44,920 INFO [stdout] (main) > 15:31:44,920 INFO [stdout] (main) > 15:31:44,921 INFO [stdout] (main) -b <value>, -b=<value> Set system property jboss.bind.address > 15:31:44,921 INFO [stdout] (main) to the given value > 15:31:44,921 INFO [stdout] (main) > 15:31:44,921 INFO [stdout] (main) > 15:31:44,922 INFO [stdout] (main) -b<interface>=<value> Set system property > 15:31:44,922 INFO [stdout] (main) jboss.bind.address.<interface> to the > 15:31:44,922 INFO [stdout] (main) given value > 15:31:44,922 INFO [stdout] (main) > 15:31:44,923 INFO [stdout] (main) > 15:31:44,923 INFO [stdout] (main) -c <config>, -c=<config> Name of the server configuration file > 15:31:44,923 INFO [stdout] (main) to use (default is "standalone.xml") > 15:31:44,923 INFO [stdout] (main) (Same as --server-config) > 15:31:44,924 INFO [stdout] (main) > 15:31:44,924 INFO [stdout] (main) > 15:31:44,924 INFO [stdout] (main) --debug [<port>] Activate debug mode with an optional > 15:31:44,924 INFO [stdout] (main) argument to specify the port. Only > 15:31:44,925 INFO [stdout] (main) works if the launch script supports it. > 15:31:44,925 INFO [stdout] (main) > 15:31:44,925 INFO [stdout] (main) > 15:31:44,925 INFO [stdout] (main) -D<name>[=<value>] Set a system property > 15:31:44,926 INFO [stdout] (main) > 15:31:44,926 INFO [stdout] (main) > 15:31:44,926 INFO [stdout] (main) -h, --help Display this message and exit > 15:31:44,927 INFO [stdout] (main) > 15:31:44,927 INFO [stdout] (main) > 15:31:44,927 INFO [stdout] (main) --read-only-server-config=<config> Name of the server configuration file > 15:31:44,927 INFO [stdout] (main) to use. This differs from > 15:31:44,928 INFO [stdout] (main) '--server-config' and '-c' in that the > 15:31:44,928 INFO [stdout] (main) original file is never overwritten. > 15:31:44,928 INFO [stdout] (main) > 15:31:44,928 INFO [stdout] (main) > 15:31:44,929 INFO [stdout] (main) -P <url>, -P=<url>, Load system properties from the given > 15:31:44,929 INFO [stdout] (main) --properties=<url> url > 15:31:44,929 INFO [stdout] (main) > 15:31:44,929 INFO [stdout] (main) > 15:31:44,930 INFO [stdout] (main) -S<name>[=<value>] Set a security property > 15:31:44,930 INFO [stdout] (main) > 15:31:44,930 INFO [stdout] (main) > 15:31:44,930 INFO [stdout] (main) --server-config=<config> Name of the server configuration file > 15:31:44,931 INFO [stdout] (main) to use (default is "standalone.xml") > 15:31:44,931 INFO [stdout] (main) (Same as -c) > 15:31:44,931 INFO [stdout] (main) > 15:31:44,931 INFO [stdout] (main) > 15:31:44,932 INFO [stdout] (main) -u <value>, -u=<value> Set system property > 15:31:44,932 INFO [stdout] (main) jboss.default.multicast.address to the > 15:31:44,932 INFO [stdout] (main) given value > 15:31:44,933 INFO [stdout] (main) > 15:31:44,933 INFO [stdout] (main) > 15:31:44,933 INFO [stdout] (main) -v, -V, --version Print version and exit > 15:31:44,934 INFO [stdout] (main) > 15:31:44,934 INFO [stdout] (main) > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2533) Add ability to set default character encoding on a subsystem level

by TedGoddard (JIRA)

[ https://issues.jboss.org/browse/WFLY-2533?page=com.atlassian.jira.plugin.... ] TedGoddard commented on WFLY-2533: ---------------------------------- Should this setting affect decoding of unicode characters in HTTP multipart uploads (such as localized filenames obtained from javax.servlet.http.Part.getHeader("content-disposition") ? > Add ability to set default character encoding on a subsystem level > ------------------------------------------------------------------ > > Key: WFLY-2533 > URL: https://issues.jboss.org/browse/WFLY-2533 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Stuart: the charset one should be pretty simple, just an attribute on <servlet-container? > Stuart: ideally we would also have it in jboss-web.xml as well > Stuart: I should also add an option to use the connector encoding > Stuart: as connectors have their own encoding set > Stuart: that is used to decode the URL > Stuart: we should have an option to use the connector encoding as the default encoding -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3096) Upgrade JGroups to 3.4.3.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-3096: ---------------------------------- Summary: Upgrade JGroups to 3.4.3.Final Key: WFLY-3096 URL: https://issues.jboss.org/browse/WFLY-3096 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 8.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.1.Final -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-440) Add JMX management beans for the Kie Scanner

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-440?page=com.atlassian.jira.plugin... ] Edson Tirelli resolved DROOLS-440. ---------------------------------- Resolution: Done This is done to the extent of the functionality that the underlying scanner exposes. To enable scanner mbeans, for now, we are using a system property: kie.scanner.mbeans = enabled . We need to improve this in the future when we add support to a configuration framework. > Add JMX management beans for the Kie Scanner > -------------------------------------------- > > Key: DROOLS-440 > URL: https://issues.jboss.org/browse/DROOLS-440 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta1 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 6.1.0.Beta2 > > > ==== from Mario ==== > Edson, > I added some of the requested features with this commit: https://github.com/droolsjbpm/drools/commit/d90c02ee3 > In particular: > > 1) list all deployed KieScanners > I added a KieScannersRegistry so you can obtain this list by invoking KieScannersRegistry.getAllKieScanners() > > 2) Display the GAV (ReleaseID) the KieScanner was created from. The V should be editable. Changing forces the KieScanner to update to the resulting effective version. > InternalKieScanner.getScannerReleaseId() > I don't think that allowing to change the ReleaseId would be a good idea. Actually that RelaseId doesn't belong to the KieScanner but to the KieContainer for which the KieScanner has been created. This implies that I should change it on the KieContainer and I am not sure this is correct. Moreover what happens if you set a version that actually doesn't exist on the maven repo? > > 3) Display the effective GAV. i.e. if they say 1.0-SNAPSHOT for 2) this one would show which snapshot was used. Same for version ranges. > InternalKieScanner.getCurrentReleaseId() > > 4) allow “scanNow” to be invoked. > KieScanner.scanNow() > > 5) allow the interval to be edited, including turning off. > KieScanner.stop() > KieScanner.start(long pollingInterval) > Note that if you want to change the pollingInterval you have to first invoke stop and then do a restart with the new pollingInterval. > > 6) Display the status, such as “starting, updating, running” (not quite sure we can do this now) > InternalKieScanner.getStatus() > > I am using the following Status defined in InternalKieScanner (I hope they makes sense but in case you want to change something about them let me know) > public enum Status { > STARTING, SCANNING, UPDATING, RUNNING, STOPPED; > } -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-440) Add JMX management beans for the Kie Scanner

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-440?page=com.atlassian.jira.plugin... ] Edson Tirelli closed DROOLS-440. -------------------------------- > Add JMX management beans for the Kie Scanner > -------------------------------------------- > > Key: DROOLS-440 > URL: https://issues.jboss.org/browse/DROOLS-440 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.Beta1 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 6.1.0.Beta2 > > > ==== from Mario ==== > Edson, > I added some of the requested features with this commit: https://github.com/droolsjbpm/drools/commit/d90c02ee3 > In particular: > > 1) list all deployed KieScanners > I added a KieScannersRegistry so you can obtain this list by invoking KieScannersRegistry.getAllKieScanners() > > 2) Display the GAV (ReleaseID) the KieScanner was created from. The V should be editable. Changing forces the KieScanner to update to the resulting effective version. > InternalKieScanner.getScannerReleaseId() > I don't think that allowing to change the ReleaseId would be a good idea. Actually that RelaseId doesn't belong to the KieScanner but to the KieContainer for which the KieScanner has been created. This implies that I should change it on the KieContainer and I am not sure this is correct. Moreover what happens if you set a version that actually doesn't exist on the maven repo? > > 3) Display the effective GAV. i.e. if they say 1.0-SNAPSHOT for 2) this one would show which snapshot was used. Same for version ranges. > InternalKieScanner.getCurrentReleaseId() > > 4) allow “scanNow” to be invoked. > KieScanner.scanNow() > > 5) allow the interval to be edited, including turning off. > KieScanner.stop() > KieScanner.start(long pollingInterval) > Note that if you want to change the pollingInterval you have to first invoke stop and then do a restart with the new pollingInterval. > > 6) Display the status, such as “starting, updating, running” (not quite sure we can do this now) > InternalKieScanner.getStatus() > > I am using the following Status defined in InternalKieScanner (I hope they makes sense but in case you want to change something about them let me know) > public enum Status { > STARTING, SCANNING, UPDATING, RUNNING, STOPPED; > } -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5768) Support resource adapter deployments via modules

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5768?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5768: ---------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 868964|https://bugzilla.redhat.com/show_bug.cgi?id=868964] from VERIFIED to CLOSED > Support resource adapter deployments via modules > ------------------------------------------------ > > Key: AS7-5768 > URL: https://issues.jboss.org/browse/AS7-5768 > Project: Application Server 7 > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > Attachments: AS7-5768-example.tgz > > > Add a new minor revision of the :resource-adapters: subsystem where the user has a choice of using > {code} > <archive>foo.rar</archive> > {code} > or > {code} > <module id="com.eis" slot="main"/> > {code} > where the latter contains the resource adapter in its unpacked form. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3094) Warn if there is no resource bound for address-settings expiry and dead-letter addresses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3094: ----------------------------------------------- Clebert Suconic <csuconic(a)redhat.com> changed the Status of [bug 1014099|https://bugzilla.redhat.com/show_bug.cgi?id=1014099] from POST to NEW > Warn if there is no resource bound for address-settings expiry and dead-letter addresses > ---------------------------------------------------------------------------------------- > > Key: WFLY-3094 > URL: https://issues.jboss.org/browse/WFLY-3094 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > > Warns the user if a address-setting has defined an expiry-address or a dead-letter-address with no queue bound for them as this will result in unintended message loss. > WildFly default full configuration specifies an expiry address (jms.queue.ExpiryQueue) and dead-letter-addres (jms.queue.DLQ) for the # address settings (i.e. matching all addresses). > To have a consistent configuration, we must also define 2 queues that will be bound to these settings. -- 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, 3 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 March 2014