March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-241) Specify and expose mod_cluster runtime information the should be shown within the console

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-241?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-241: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Specify and expose mod_cluster runtime information the should be shown within the console > ----------------------------------------------------------------------------------------- > > Key: WFLY-241 > URL: https://issues.jboss.org/browse/WFLY-241 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Heiko Braun > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-224) Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*"

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-224?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-224: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*" > ---------------------------------------------------------------------------------------- > > Key: WFLY-224 > URL: https://issues.jboss.org/browse/WFLY-224 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Affects Versions: 8.0.0.Alpha1 > Reporter: Harald Pehl > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 9.0.0.CR1 > > > The attribute "cache-type" in "/subsystem=security/security-domain=*" can either be "default" or "infinispan". Please add the allowed value to the resource description. > In order to generate the UI based on the management model, it is essential that information like this is present. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-279) Add deployment-scanner for singleton deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-279?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-279: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Add deployment-scanner for singleton deployments > ------------------------------------------------ > > Key: WFLY-279 > URL: https://issues.jboss.org/browse/WFLY-279 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > To simplify the use of singleton deployments in standalone mode, it would be nice to have a mechanism analogous to the hasingleton-deploy directory in AS6 and earlier. To do this, we can enhance the existing deployment-scanner to accept an additional policy attribute. Something like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="standard"/> > <deployment-scanner path="singleton-deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="singleton"/> > </subsystem> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-277) TS: Integrate JUnitDiff

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-277?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-277: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > TS: Integrate JUnitDiff > ----------------------- > > Key: WFLY-277 > URL: https://issues.jboss.org/browse/WFLY-277 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 9.0.0.CR1 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Running with > {code} > -DjunitDiff='<path1>:<path2>:<path3>' > {code} > would create a comparison to given testsuite result sets (JUnit .xml and txt files). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-276) Clustering/multi-node tests cannot be run with -Djpda debugger

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-276?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-276: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Clustering/multi-node tests cannot be run with -Djpda debugger > -------------------------------------------------------------- > > Key: WFLY-276 > URL: https://issues.jboss.org/browse/WFLY-276 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation, Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 9.0.0.CR1 > > > The doc now says whats pasted below, but I am not sure if both servers are listening on 8787 because (that would fail the startup), if I have to connect to both or where do I configure that, etc. > {code} > Running JBoss AS instances with debugger > Adding -Djpda (May be changed to -Ddebug in the future) will make JBoss AS run with JPDA JVM arguments for debugging. > It will suspend and wait for the debugger to connect at port 8787. > JBoss AS is started by Arquillian, when the first test which requires given instance is run. There's (currently) no challenge text in the console, it will look like the first test is stuck. This is being solved in http://jira.codehaus.org/browse/SUREFIRE-781. > Depending on which test group(s) you run, multiple instances may be started. In that case, you need to attach the debugger multiple times. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-273) Document how to configure firewall when using different JGroups stacks

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-273?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-273: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Document how to configure firewall when using different JGroups stacks > ---------------------------------------------------------------------- > > Key: WFLY-273 > URL: https://issues.jboss.org/browse/WFLY-273 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > Document how to configure firewall for using different clustering stacks > https://docs.jboss.org/author/display/AS71/High+Availability+Guide > Needed by OpenShift team (especially TCP stacks). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-319) OpenSSL SSL certificate support for domain management security realms (http and native interface)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-319?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-319: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > OpenSSL SSL certificate support for domain management security realms (http and native interface) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-319 > URL: https://issues.jboss.org/browse/WFLY-319 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security, Server > Reporter: Franck LEDAY > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > related to https://community.jboss.org/message/728665#728665 : > Request the feature to use SSL certificate issued from OpenSSL directly from SSL attribute of management interface instead of available use of JKS . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-316) Javadoc - exclude _private.* packages

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-316?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-316: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Javadoc - exclude _private.* packages > ------------------------------------- > > Key: WFLY-316 > URL: https://issues.jboss.org/browse/WFLY-316 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-288) SecurityDomainJndiInjectable should allow "java:/jaas" prefixed security domain on demand

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-288?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-288: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > SecurityDomainJndiInjectable should allow "java:/jaas" prefixed security domain on demand > ----------------------------------------------------------------------------------------- > > Key: WFLY-288 > URL: https://issues.jboss.org/browse/WFLY-288 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Anil Saldhana > Assignee: Stefan Guilhen > Fix For: 9.0.0.CR1 > > > Currently, security domain strings of the form "java:/jaas/sd" are not resolving properly. IMO we should allow users to deploy applications on AS4,5,6,7 if they need to. > So have a flag inside the SecurityDomainJndiInjectable class that is turned off by default. If you turn it on, then "java:/jaas" is unprefixed if present. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-334) HA Singleton deployer for applications

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-334?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-334: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > HA Singleton deployer for applications > -------------------------------------- > > Key: WFLY-334 > URL: https://issues.jboss.org/browse/WFLY-334 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Labels: deployers, hasingleton > Fix For: 9.0.0.CR1 > > > A HASingleton deployer should be provided in standalone and domain mode. > To be able to migrate such singleton applications from former AS versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015