April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1467) Servers are suspended two times using timeout parameter in domain mode

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1467?page=com.atlassian.jira.plugi... ] Yeray Santana Borges commented on WFCORE-1467: ---------------------------------------------- Ohh, correct, I didn't see it before, sadly it is being multiplied two times; once in DomainServerLifecycleHandlers#SuspendServersLifecycleHandler and the other in ServerSuspendHandler#execute Is it necesary a new issue to resolve it? > Servers are suspended two times using timeout parameter in domain mode > ---------------------------------------------------------------------- > > Key: WFCORE-1467 > URL: https://issues.jboss.org/browse/WFCORE-1467 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Yeray Santana Borges > Assignee: Yeray Santana Borges > > In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified. > How to reproduce it: > {code} > [domain@localhost:9990 /] :suspend-servers(timeout=10) > {code} > Server log traces show: > {code} > [Server:server-one] 20:14:40,126 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout. > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} > Expected traces are: > {code} > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1467) Servers are suspended two times using timeout parameter in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1467?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1467: ------------------------------------------ This isn't correct either: [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. It should say "10000 ms" not "10000000ms". Hopefully it's just getting multiplied by 1K a second time for the log message and not for the actual timeout calculation! > Servers are suspended two times using timeout parameter in domain mode > ---------------------------------------------------------------------- > > Key: WFCORE-1467 > URL: https://issues.jboss.org/browse/WFCORE-1467 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Yeray Santana Borges > Assignee: Yeray Santana Borges > > In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified. > How to reproduce it: > {code} > [domain@localhost:9990 /] :suspend-servers(timeout=10) > {code} > Server log traces show: > {code} > [Server:server-one] 20:14:40,126 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout. > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} > Expected traces are: > {code} > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-129) Create a better error message if the time zone argument is missing from the %z format pattern

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-129?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-129: --------------------------------- Description: Using the {{%z}} format pattern and not including a time zone argument results in an NPE. A better error message should be thrown indicating an argument is required. {code:title=Example pattern} %z{GMT} {code} A bonus would be to possibly add a warning, once only though, if the time {{%d}} was processed before the time zone {{%z}}. was: Using the {{%z}} format pattern and not including a time zone argument results in an NPE. A better error message should be thrown indicating an argument is required. {code:title=Example pattern} %z{GMT} {code} > Create a better error message if the time zone argument is missing from the %z format pattern > --------------------------------------------------------------------------------------------- > > Key: LOGMGR-129 > URL: https://issues.jboss.org/browse/LOGMGR-129 > Project: JBoss Log Manager > Issue Type: Task > Reporter: James Perkins > > Using the {{%z}} format pattern and not including a time zone argument results in an NPE. A better error message should be thrown indicating an argument is required. > {code:title=Example pattern} > %z{GMT} > {code} > A bonus would be to possibly add a warning, once only though, if the time {{%d}} was processed before the time zone {{%z}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-129) Create a better error message if the time zone argument is missing from the %z format pattern

by James Perkins (JIRA)

James Perkins created LOGMGR-129: ------------------------------------ Summary: Create a better error message if the time zone argument is missing from the %z format pattern Key: LOGMGR-129 URL: https://issues.jboss.org/browse/LOGMGR-129 Project: JBoss Log Manager Issue Type: Task Reporter: James Perkins Using the {{%z}} format pattern and not including a time zone argument results in an NPE. A better error message should be thrown indicating an argument is required. {code:title=Example pattern} %z{GMT} {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1467) Servers are suspended two times using timeout parameter in domain mode

by Yeray Santana Borges (JIRA)

Yeray Santana Borges created WFCORE-1467: -------------------------------------------- Summary: Servers are suspended two times using timeout parameter in domain mode Key: WFCORE-1467 URL: https://issues.jboss.org/browse/WFCORE-1467 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Yeray Santana Borges Assignee: Brian Stansberry In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified. How to reproduce it: {code} [domain@localhost:9990 /] :suspend-servers(timeout=10) {code} Server log traces show: {code} [Server:server-one] 20:14:40,126 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout. [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. {code} Expected traces are: {code} [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1467) Servers are suspended two times using timeout parameter in domain mode

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1467?page=com.atlassian.jira.plugi... ] Yeray Santana Borges reassigned WFCORE-1467: -------------------------------------------- Assignee: Yeray Santana Borges (was: Brian Stansberry) > Servers are suspended two times using timeout parameter in domain mode > ---------------------------------------------------------------------- > > Key: WFCORE-1467 > URL: https://issues.jboss.org/browse/WFCORE-1467 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Yeray Santana Borges > Assignee: Yeray Santana Borges > > In a domain mode :suspend-servers command with a timeout parameter different than 0 executes two suspend operations for each server in the domain. It first executes a suspend with 0ms and later a suspend with the timeout specified. > How to reproduce it: > {code} > [domain@localhost:9990 /] :suspend-servers(timeout=10) > {code} > Server log traces show: > {code} > [Server:server-one] 20:14:40,126 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 0ms timeout. > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} > Expected traces are: > {code} > [Server:server-one] 20:14:40,135 INFO [org.jboss.as.server] (ServerService Thread Pool -- 8) WFLYSRV0211: Suspending server with 10000000ms timeout. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6500) wildfly-10.0.0.Final deployment crash

by Jason Morgan (JIRA)

Jason Morgan created WFLY-6500: ---------------------------------- Summary: wildfly-10.0.0.Final deployment crash Key: WFLY-6500 URL: https://issues.jboss.org/browse/WFLY-6500 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Jason Morgan Assignee: Jason Greene Having a war in the deployment directory and then "replacing" a deployment through the web console causes the server to crash without any logging on restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1466) Wildfly SSL Setup Fails on HSM-Backed Keystore

by Gregory Ramsperger (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1466?page=com.atlassian.jira.plugi... ] Gregory Ramsperger commented on WFCORE-1466: -------------------------------------------- Great. I'm happy to test the other solution if needed. > Wildfly SSL Setup Fails on HSM-Backed Keystore > ---------------------------------------------- > > Key: WFCORE-1466 > URL: https://issues.jboss.org/browse/WFCORE-1466 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: Any host environment with an HSM for key management > Reporter: Gregory Ramsperger > Assignee: Darran Lofthouse > > Using a keystore type that does not allow or returns empty from getEncoded() on private keys causes a KeyStoreException at startup. This is common in HSM-backed key operations. > Storing SSL keys and certs in an HSM is a common method of securing keys and offloading SSL overhead. > FileKeyStore.java copies a KeyStore.Entry value into a JKS KeyStore but JKS and PKCS12 KeyStore implementations maintain a copy of the encoded PKCS#8 data for private keys. When applying a KeyStore.Entry from a source that does not return the data for security reasons, the import fails. > While it's still not guaranteed to work with all KeyStore providers, switching {{KeyStore.getInstance("JKS")}} to {{KeyStore.getInstance(provider)}} fixes the issue for SafeNet "Luna" and SunPKCS11 "PKCS11" KeyStore implementations while not breaking the "PKCS12" and "JKS" cases. > See [https://github.com/wildfly/wildfly-core/blob/master/domain-management/src...] > Log output: > {noformat} > 2016-04-04 18:53:51,100 i-4b6f79d1 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.server.controller.management.security_realm.test.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.test.key-manager: JBAS015229: Unable to start service > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:148) > at org.jboss.as.domain.management.security.FileKeyManagerService.start(FileKeyManagerService.java:119) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60] > Caused by: java.security.KeyStoreException: Cannot get key bytes, not PKCS#8 encoded > at sun.security.provider.KeyProtector.protect(KeyProtector.java:174) [rt.jar:1.8.0_60] > at sun.security.provider.JavaKeyStore.engineSetKeyEntry(JavaKeyStore.java:267) [rt.jar:1.8.0_60] > at sun.security.provider.JavaKeyStore$JKS.engineSetKeyEntry(JavaKeyStore.java:56) [rt.jar:1.8.0_60] > at java.security.KeyStoreSpi.engineSetEntry(KeyStoreSpi.java:537) [rt.jar:1.8.0_60] > at sun.security.provider.KeyStoreDelegator.engineSetEntry(KeyStoreDelegator.java:179) [rt.jar:1.8.0_60] > at sun.security.provider.JavaKeyStore$DualFormatJKS.engineSetEntry(JavaKeyStore.java:70) [rt.jar:1.8.0_60] > at java.security.KeyStore.setEntry(KeyStore.java:1557) [rt.jar:1.8.0_60] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:136) > ... 6 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1464) LogContexts are not removed for ear subdeployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1464?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1464: ------------------------------------------------- Aaron Ogburn <aogburn(a)redhat.com> changed the Status of [bug 1324572|https://bugzilla.redhat.com/show_bug.cgi?id=1324572] from ASSIGNED to POST > LogContexts are not removed for ear subdeployments > -------------------------------------------------- > > Key: WFCORE-1464 > URL: https://issues.jboss.org/browse/WFCORE-1464 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 2.1.0.Final > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > Fix For: 3.0.0.Alpha1 > > Attachments: app.ear > > > If an ear does not have its own LogContext created, but a subdeployment in it does, the subdeployment never has its LogContext cleaned up upon undeploy, leading to PermGen leaks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-491) General SSLContext matching facility

by David Lloyd (JIRA)

David Lloyd created ELY-491: ------------------------------- Summary: General SSLContext matching facility Key: ELY-491 URL: https://issues.jboss.org/browse/ELY-491 Project: WildFly Elytron Issue Type: Task Components: SSL Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.0.Beta6 Add a facility to match SSL handshake attributes to a corresponding SSL context. Start with converting the existing SNI code over. Later (Java 9), ALPN matching can be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 April 2016