November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1135) Enable FIPS support in Domain Mode

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Ryan Emerson updated WFCORE-1135: --------------------------------- Summary: Enable FIPS support in Domain Mode (was: Unable to start Wildfly when FIPS is enabled in domain mode) > Enable FIPS support in Domain Mode > ---------------------------------- > > Key: WFCORE-1135 > URL: https://issues.jboss.org/browse/WFCORE-1135 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Affects Versions: 2.0.1.Final > Reporter: Ryan Emerson > Assignee: Brian Stansberry > Attachments: domain.xml, host.xml > > > Resulting stacktrace below: > 15:47:39,410 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:133) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-one] at java.lang.Thread.run(Thread.java:745) > [Server:server-one] Caused by: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.getAcceptingSSLContext(HostControllerConnectionService.java:212) > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:108) > [Server:server-one] ... 5 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1135) Unable to start Wildfly when FIPS is enabled in domain mode

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Ryan Emerson reassigned WFCORE-1135: ------------------------------------ Assignee: Brian Stansberry (was: Ryan Emerson) > Unable to start Wildfly when FIPS is enabled in domain mode > ----------------------------------------------------------- > > Key: WFCORE-1135 > URL: https://issues.jboss.org/browse/WFCORE-1135 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.1.Final > Reporter: Ryan Emerson > Assignee: Brian Stansberry > Attachments: domain.xml, host.xml > > > Resulting stacktrace below: > 15:47:39,410 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:133) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-one] at java.lang.Thread.run(Thread.java:745) > [Server:server-one] Caused by: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.getAcceptingSSLContext(HostControllerConnectionService.java:212) > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:108) > [Server:server-one] ... 5 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5713) Remove duplicate keys from clustering LocalDescriptions.properties

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5713: ------------------------------------ Summary: Remove duplicate keys from clustering LocalDescriptions.properties Key: WFLY-5713 URL: https://issues.jboss.org/browse/WFLY-5713 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Optional Violates properties file structure, adds unnecessar translations, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5711) FormAuthenticationWebFailoverTestCase fails against Undertow 1.3.6.Final

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5711?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5711: ------------------------------- Summary: FormAuthenticationWebFailoverTestCase fails against Undertow 1.3.6.Final (was: FormAuthenticationWebFailoverTestCase fails against 1.3.6.Final) > FormAuthenticationWebFailoverTestCase fails against Undertow 1.3.6.Final > ------------------------------------------------------------------------ > > Key: WFLY-5711 > URL: https://issues.jboss.org/browse/WFLY-5711 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5712) FormAuthenticationWebFailoverTestCase fails against 1.3.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5712: ---------------------------------- Summary: FormAuthenticationWebFailoverTestCase fails against 1.3.6.Final Key: WFLY-5712 URL: https://issues.jboss.org/browse/WFLY-5712 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 10.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5711) FormAuthenticationWebFailoverTestCase fails against 1.3.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-5711: ---------------------------------- Summary: FormAuthenticationWebFailoverTestCase fails against 1.3.6.Final Key: WFLY-5711 URL: https://issues.jboss.org/browse/WFLY-5711 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 10.0.0.CR4 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 10.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5180) Creating cache from user code needs to execute in a privileged block

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5180?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5180: --------------------------------- Summary: Creating cache from user code needs to execute in a privileged block (was: InfinispanResourceRefTestCase causes NameNotFoundException with security manager) > Creating cache from user code needs to execute in a privileged block > -------------------------------------------------------------------- > > Key: WFLY-5180 > URL: https://issues.jboss.org/browse/WFLY-5180 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security Manager > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Radoslav Husar > > *Description of problem:* > InfinispanResourceRefTestCase causes NameNotFoundException with security manager. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./build.sh -DskipTests -DallTests -Dts.noSmoke > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=InfinispanResourceRefTestCase > *Actual results:* > {noformat} > javax.naming.NameNotFoundException: infinispan > at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58) > at org.jboss.as.naming.ServiceBasedNamingStore$1.run(ServiceBasedNamingStore.java:138) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase.test(InfinispanResourceRefTestCase.java:64) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5180) InfinispanResourceRefTestCase causes NameNotFoundException with security manager

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5180?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5180: --------------------------------- Component/s: Security Manager (was: Test Suite) > InfinispanResourceRefTestCase causes NameNotFoundException with security manager > -------------------------------------------------------------------------------- > > Key: WFLY-5180 > URL: https://issues.jboss.org/browse/WFLY-5180 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Radoslav Husar > > *Description of problem:* > InfinispanResourceRefTestCase causes NameNotFoundException with security manager. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./build.sh -DskipTests -DallTests -Dts.noSmoke > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=InfinispanResourceRefTestCase > *Actual results:* > {noformat} > javax.naming.NameNotFoundException: infinispan > at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58) > at org.jboss.as.naming.ServiceBasedNamingStore$1.run(ServiceBasedNamingStore.java:138) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase.test(InfinispanResourceRefTestCase.java:64) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5180) InfinispanResourceRefTestCase causes NameNotFoundException with security manager

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5180?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5180: --------------------------------- Component/s: Clustering > InfinispanResourceRefTestCase causes NameNotFoundException with security manager > -------------------------------------------------------------------------------- > > Key: WFLY-5180 > URL: https://issues.jboss.org/browse/WFLY-5180 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security Manager > Affects Versions: 10.0.0.CR4 > Reporter: Marek Kopecký > Assignee: Radoslav Husar > > *Description of problem:* > InfinispanResourceRefTestCase causes NameNotFoundException with security manager. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./build.sh -DskipTests -DallTests -Dts.noSmoke > # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=InfinispanResourceRefTestCase > *Actual results:* > {noformat} > javax.naming.NameNotFoundException: infinispan > at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58) > at org.jboss.as.naming.ServiceBasedNamingStore$1.run(ServiceBasedNamingStore.java:138) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase.test(InfinispanResourceRefTestCase.java:64) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1982) RequestCorrelator: use IntHashMap / LongHashmap for request correlation

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1982?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1982: -------------------------------- These classes can possibly also be used for logging, when retrieving error messages based on a key > RequestCorrelator: use IntHashMap / LongHashmap for request correlation > ----------------------------------------------------------------------- > > Key: JGRP-1982 > URL: https://issues.jboss.org/browse/JGRP-1982 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.7 > > > In RequestCorrelator (and possibly other classes), use an IntHashMap or LongHashmap for the request table. Goal: use less space when we have a lot of requests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 2015