December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4180) Allow for more control over the creation of the SSLContext

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-4180: ------------------------------------ Summary: Allow for more control over the creation of the SSLContext Key: WFLY-4180 URL: https://issues.jboss.org/browse/WFLY-4180 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4179) Three web integration test failures with security manager enabled

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4179?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4179: ----------------------------------- This is all caused by WFLY-84 > Three web integration test failures with security manager enabled > ----------------------------------------------------------------- > > Key: WFLY-4179 > URL: https://issues.jboss.org/browse/WFLY-4179 > Project: WildFly > Issue Type: Bug > Components: Security Manager, Test Suite > Reporter: James Perkins > Assignee: Stefan Guilhen > Attachments: org.jboss.as.test.integration.jsp.JspTagTestCase-output.txt, org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase-output.txt, org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase.txt > > > The following 3 tests fail when the security manager is enabled for the {{testsuite/integration/web}} tests. > * org.jboss.as.test.integration.jsp.JspTagTestCase > * org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase > * org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase > The tests are set to be ignored if the {{-Dsecurity.manager}} property is enabled. Once resolved the profile in the pom.xml for the web integration tests should be removed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1905: -------------------------------- Alternatively we could send a special message back to the sender, informing it that the fork-stack or -channel is not available. The Rsp would then be marked specially, let's see... > FORK: RPCs might block if fork channel or fork stack is not available > --------------------------------------------------------------------- > > Key: JGRP-1905 > URL: https://issues.jboss.org/browse/JGRP-1905 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.2 > > > When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out. > h5. Solution > * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available"). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

by Bela Ban (JIRA)

Bela Ban created JGRP-1905: ------------------------------ Summary: FORK: RPCs might block if fork channel or fork stack is not available Key: JGRP-1905 URL: https://issues.jboss.org/browse/JGRP-1905 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.2 When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out. h5. Solution * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available"). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4043) Cannot load custom login module

by Rostyslav Smirnov (JIRA)

[ https://issues.jboss.org/browse/WFLY-4043?page=com.atlassian.jira.plugin.... ] Rostyslav Smirnov commented on WFLY-4043: ----------------------------------------- Thank you! It would help if "module" attribute was mentioned somewhere in the [documentation|https://docs.jboss.org/author/display/WFLY8/Security+subsys...]. > Cannot load custom login module > ------------------------------- > > Key: WFLY-4043 > URL: https://issues.jboss.org/browse/WFLY-4043 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.1.0.Final > Environment: Java 1.8.0_25 > Reporter: Rostyslav Smirnov > Assignee: Jason Greene > > When security realm authentication is configured to use JAAS domain, it is not possible to use custom login module, because there is no loader present for deployed classes. LoginContext attempts to load the login module class and fails with ClassNotFoundException. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-463) Add consistent shutdown hook log message

by Kyle Lape (JIRA)

Kyle Lape created WFCORE-463: -------------------------------- Summary: Add consistent shutdown hook log message Key: WFCORE-463 URL: https://issues.jboss.org/browse/WFCORE-463 Project: WildFly Core Issue Type: Enhancement Components: Logging Reporter: Kyle Lape Assignee: James Perkins It would be nice to have a consistent log message to see when a shutdown began that is independent of any particular subsystem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-462) Deployment info should not accept wildcard as server-group parameter

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-462?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-4177 to WFCORE-462: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-462 (was: WFLY-4177) Affects Version/s: 1.0.0.Alpha14 (was: 9.0.0.Alpha1) Component/s: CLI (was: CLI) Fix Version/s: (was: No Release) > Deployment info should not accept wildcard as server-group parameter > -------------------------------------------------------------------- > > Key: WFCORE-462 > URL: https://issues.jboss.org/browse/WFCORE-462 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 1.0.0.Alpha14 > Environment: All environments. > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Priority: Optional > Labels: core > Original Estimate: 2 days > Remaining Estimate: 2 days > > Actually the deployment-info in a domain mode accepts the wildcard *, but when the * is given the CLI lists only the last server-group in the list, not all. The help says: > - single server group with a state report about each deployment in the > domain with regard to the selected server group. > In this case, the --server-group argument is required and its value > must be a specific server group name, not a wildcard expression. > The output of the command is a table with headers NAME, RUNTIME-NAME and STATE. > Ex: > [domain@localhost:9990 /] deployment-info --name=test.war --server-group=* > NAME RUNTIME-NAME STATE > test.war test.war not added > After the change: > [domain@localhost:9990 /] deployment-info --name=test.war --server-group=* > Wildcards are note permited here, please give a valid server-group name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1749) Switch from commons-beanutils to commons-beanutils-core

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1749?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-1749: --------------------------------- Assignee: Tomaz Cerar (was: Paul Gier) > Switch from commons-beanutils to commons-beanutils-core > ------------------------------------------------------- > > Key: WFLY-1749 > URL: https://issues.jboss.org/browse/WFLY-1749 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 8.0.0.Alpha3 > Reporter: David Walluck > Assignee: Tomaz Cerar > Priority: Minor > > The commons-beanutils jar includes classes from commons-collections which are not shaded, and should not be used, in any case. > The dependency can be switched from commons-beanutils:commons-beanutils to commons-beanutils:commons-beanutils-core which does not contain the classes. > Any module that actually needs the commons-collections classes should ensure that org.apache.commons.collections is also included as an import. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4179) Three web integration test failures with security manager enabled

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4179?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4179: -------------------------------- Attachment: org.jboss.as.test.integration.jsp.JspTagTestCase-output.txt org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase-output.txt org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase.txt Output from the 3 failed tests attached. > Three web integration test failures with security manager enabled > ----------------------------------------------------------------- > > Key: WFLY-4179 > URL: https://issues.jboss.org/browse/WFLY-4179 > Project: WildFly > Issue Type: Bug > Components: Security Manager, Test Suite > Reporter: James Perkins > Assignee: Stefan Guilhen > Attachments: org.jboss.as.test.integration.jsp.JspTagTestCase-output.txt, org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase-output.txt, org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase.txt > > > The following 3 tests fail when the security manager is enabled for the {{testsuite/integration/web}} tests. > * org.jboss.as.test.integration.jsp.JspTagTestCase > * org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase > * org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase > The tests are set to be ignored if the {{-Dsecurity.manager}} property is enabled. Once resolved the profile in the pom.xml for the web integration tests should be removed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4179) Three web integration test failures with security manager enabled

by James Perkins (JIRA)

James Perkins created WFLY-4179: ----------------------------------- Summary: Three web integration test failures with security manager enabled Key: WFLY-4179 URL: https://issues.jboss.org/browse/WFLY-4179 Project: WildFly Issue Type: Bug Components: Security Manager, Test Suite Reporter: James Perkins Assignee: Stefan Guilhen The following 3 tests fail when the security manager is enabled for the {{testsuite/integration/web}} tests. * org.jboss.as.test.integration.jsp.JspTagTestCase * org.jboss.as.test.integration.web.servlet.lifecycle.ServletLifecycleMethodDescriptorTestCase * org.jboss.as.test.integration.web.customerrors.CustomErrorsUnitTestCase The tests are set to be ignored if the {{-Dsecurity.manager}} property is enabled. Once resolved the profile in the pom.xml for the web integration tests should be removed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

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 December 2014