November 2015 - jboss-jira - Jboss List Archives

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-5694 to WFCORE-1135: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1135 (was: WFLY-5694) Affects Version/s: 2.0.1.Final (was: 10.0.0.CR4) > 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 > Affects Versions: 2.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Attachments: domain.xml, host.xml > > -- 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 Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1135: ------------------------------------- Component/s: Domain Management Security > 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: Ryan Emerson > Attachments: domain.xml, host.xml > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

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

by Ryan Emerson (JIRA)

Ryan Emerson created WFLY-5695: ---------------------------------- Summary: Unable to start Wildfly when FIPS is enabled in domain mode Key: WFLY-5695 URL: https://issues.jboss.org/browse/WFLY-5695 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.CR4 Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

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

by Ryan Emerson (JIRA)

Ryan Emerson created WFLY-5694: ---------------------------------- Summary: Unable to start Wildfly when FIPS is enabled in domain mode Key: WFLY-5694 URL: https://issues.jboss.org/browse/WFLY-5694 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.CR4 Reporter: Ryan Emerson Assignee: Ryan Emerson Attachments: domain.xml, host.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-372) Add runAs* variants that are lambda-friendly

by David Lloyd (JIRA)

David Lloyd created ELY-372: ------------------------------- Summary: Add runAs* variants that are lambda-friendly Key: ELY-372 URL: https://issues.jboss.org/browse/ELY-372 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 1.1.0.Beta2 The runAs* methods are overloaded and thus are hostile to lambdas. Add variations that do not have ambiguous overloads and which accept (Bi)Function, (Bi)Consumer, and Supplier arguments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-917) "Could not initialize class java.lang.StringCoding" on HP-UX

by Gene Bradley (JIRA)

[ https://issues.jboss.org/browse/WFCORE-917?page=com.atlassian.jira.plugin... ] Gene Bradley commented on WFCORE-917: ------------------------------------- hi Marek, are you using a LANG setting when running this? > "Could not initialize class java.lang.StringCoding" on HP-UX > ------------------------------------------------------------ > > Key: WFCORE-917 > URL: https://issues.jboss.org/browse/WFCORE-917 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Marek Kopecký > Assignee: Jason Greene > > *Description of problem:* > "NoClassDefFoundError: Could not initialize class java.lang.StringCoding" occurs on HP-UX in a non-interactive mode of CLI > This is intermittent issue. > This exception occurs even without running domain server. > *How reproducible:* > 2% on HP-UX > *Steps to Reproduce: (this reproducer always hits this issue)* > # ./domain.sh \# optional step > # {noformat}for (( i = 1; i <= 200 ; i++ )) ; do > ./jboss-cli.sh -c command="/profile=test:add" > ./jboss-cli.sh -c command="/profile=test:remove" > done{noformat} > *Actual results:* > {noformat} > Exception: java.lang.NullPointerException thrown from the UncaughtExceptionHandler in thread "Finalizer" > Error occurred during initialization of VM > java.lang.NoClassDefFoundError: Could not initialize class java.lang.StringCoding > at java.lang.String.<init>(String.java:534) > at java.lang.String.<init>(String.java:554) > at java.lang.System.initProperties(Native Method) > at java.lang.System.initializeSystemClass(System.java:1164) > {noformat} > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBADMCON-176) JBOSS AS 7.0.1 , how to get Admin Console

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBADMCON-176?page=com.atlassian.jira.plug... ] Tomaz Cerar closed JBADMCON-176. -------------------------------- Resolution: Rejected User help questions belong to forums https://developer.jboss.org/en/jbossas7 > JBOSS AS 7.0.1 , how to get Admin Console > ----------------------------------------- > > Key: JBADMCON-176 > URL: https://issues.jboss.org/browse/JBADMCON-176 > Project: JBoss Admin Console > Issue Type: Feature Request > Reporter: jitendra parihar > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5693) Improve clustering thread pool validation

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5693?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5693: --------------------------------- Issue Type: Task (was: Feature Request) > Improve clustering thread pool validation > ----------------------------------------- > > Key: WFLY-5693 > URL: https://issues.jboss.org/browse/WFLY-5693 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > Currently, configuration where e.g. max threads is smaller than min threads is accepted in the model, is not validated by jgroups either and then fails at runtime > {noformat} > 15:17:50,221 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.jgroups.channel.ee: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee: java.lang.IllegalArgumentException > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:80) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307) > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195) > at org.jgroups.protocols.TP.createThreadPool(TP.java:2358) > at org.jgroups.protocols.TP.init(TP.java:1152) > at org.jgroups.protocols.BasicTCP.init(BasicTCP.java:87) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) > at org.jgroups.JChannel.init(JChannel.java:853) > at org.jgroups.JChannel.<init>(JChannel.java:159) > at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:95) > at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:92) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:98) > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:78) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5693) Improve clustering thread pool validation

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-5693: ------------------------------------ Summary: Improve clustering thread pool validation Key: WFLY-5693 URL: https://issues.jboss.org/browse/WFLY-5693 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 10.0.0.CR4 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Optional Currently, configuration where e.g. max threads is smaller than min threads is accepted in the model, is not validated by jgroups either and then fails at runtime {noformat} 15:17:50,221 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.jgroups.channel.ee: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee: java.lang.IllegalArgumentException at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:80) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307) at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195) at org.jgroups.protocols.TP.createThreadPool(TP.java:2358) at org.jgroups.protocols.TP.init(TP.java:1152) at org.jgroups.protocols.BasicTCP.init(BasicTCP.java:87) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481) at org.jgroups.JChannel.init(JChannel.java:853) at org.jgroups.JChannel.<init>(JChannel.java:159) at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:95) at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:92) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:98) at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:78) ... 5 more {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5494) Fix Infinispan subsystem cache store properties transformations and improve testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5494?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5494: --------------------------------- Fix Version/s: (was: 10.0.0.Final) > Fix Infinispan subsystem cache store properties transformations and improve testing > ----------------------------------------------------------------------------------- > > Key: WFLY-5494 > URL: https://issues.jboss.org/browse/WFLY-5494 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Similar to what is done in jgroups, related fixes and move code to common module, etc. -- 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