May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1470) There are unknown project codes in wildfly core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1470?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1470: ------------------------------------- Fix Version/s: 2.2.0.CR1 > There are unknown project codes in wildfly core > ----------------------------------------------- > > Key: WFCORE-1470 > URL: https://issues.jboss.org/browse/WFCORE-1470 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 2.1.0.Final > Reporter: Ivan Straka > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > we see unknown project codes in wildfly-core: > {code:java} > '<<none>>' - 'version/src/main/java/org/jboss/as/version/UsageMessages.java' > 'N/A' - 'core-security/implementation/src/main/java/org/jboss/as/core/security/CoreSecurityMessages.java' > {code} > They should be changed to empty string. > https://issues.jboss.org/browse/EAP7-44?focusedCommentId=13170957&page=co... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1466?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1466: ------------------------------------- Fix Version/s: 2.2.0.CR1 > 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 > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1315) Double prompt when connecting to a new HC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1315?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1315: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Double prompt when connecting to a new HC > ----------------------------------------- > > Key: WFCORE-1315 > URL: https://issues.jboss.org/browse/WFCORE-1315 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.8.Final > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Priority: Optional > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > I observed this with 0.66.3 in a kind of franken-build of EAP 7. The logical equivalent would be 2.0.8.Final once WFCORE-1277 is fixed. > {code} > [domain@localhost:9990 core-service=discovery-options] connect 127.0.0.1:29990 > [disconnected core-service=discovery-options] [domain@127.0.0.1:29990 core-service=discovery-options] cd / > [domain@127.0.0.1:29990 /] > {code} > Before the first line I had killed the HC at localhost:9990, so then I wanted to connect to another HC. Got a double prompt. > Not a big deal, but I wanted to record it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1462) ssl element not usable in xml cli config

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1462?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1462: ------------------------------------- Fix Version/s: 2.2.0.CR1 > ssl element not usable in xml cli config > ---------------------------------------- > > Key: WFCORE-1462 > URL: https://issues.jboss.org/browse/WFCORE-1462 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > Setting a trust store in the cli-config.xml (ssl XML element) has the side effect to load classes from picketBox that is not present in the core feature pack. This makes ssl element not usable in a core configuration. This works well in a fully featured wildly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-263) Cancelling management op on slave HC tree is broken

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-263?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-263: ------------------------------------ Fix Version/s: 2.2.0.CR1 > Cancelling management op on slave HC tree is broken > --------------------------------------------------- > > Key: WFCORE-263 > URL: https://issues.jboss.org/browse/WFCORE-263 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha9 > Reporter: James Livingston > Assignee: Brian Stansberry > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Attachments: unundeployable.zip > > > If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via: > /host=master/core-service=management/service=management-operations:find-non-progressing-operation > /host=slave/core-service=management/service=management-operations:find-non-progressing-operation > Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again. > If however you attempt to cancel the operation under /host=slave, it goes bad. { "outcome" => "success", "result" => undefined } is reported in the CLI, but the controllers are still unresponsive. > Running :find-non-progressing-operation against the slave will report the {outcome=success,result=undefined} rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled. > Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1464?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1464: ------------------------------------- Fix Version/s: 2.2.0.CR1 > 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: 2.2.0.CR1, 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1413) Web console doesn't accept passwords with non-ascii characters

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1413?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1413: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Web console doesn't accept passwords with non-ascii characters > -------------------------------------------------------------- > > Key: WFCORE-1413 > URL: https://issues.jboss.org/browse/WFCORE-1413 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > Firefox, Safari and IE use ISO-8859_1 character encoding when generating authentication header. If the credentials contain umlauts (eg. ü), the decoded string on the server is incorrect and authentication fails. > This affects web console authentication when LDAP is used as credentials store. > Web console can solve this by using https://issues.jboss.org/browse/UNDERTOW-595 which adds ability for Undertow to use user-agent patterns to choose correct charset during BASIC authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1230) Drop OperationContextImpl.DescriptionCaching(Immutable)ResourceRegistration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1230?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1230: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Drop OperationContextImpl.DescriptionCaching(Immutable)ResourceRegistration > --------------------------------------------------------------------------- > > Key: WFCORE-1230 > URL: https://issues.jboss.org/browse/WFCORE-1230 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > The OperationContextImpl.DescriptionCaching(Immutable)ResourceRegistration classes and the usage thereof are no longer needed. They were used for RBAC checks in cases where an MRR had attributes without an AttributeDefinition. But those are no longer possible so this code is unnecessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1453) module patched in a one-off not included in the next cp is not port-forwarded from the prev cp

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1453?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1453: ------------------------------------- Fix Version/s: 2.2.0.CR1 > module patched in a one-off not included in the next cp is not port-forwarded from the prev cp > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1453 > URL: https://issues.jboss.org/browse/WFCORE-1453 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 2.1.0.Final > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > If CP1 patches module M, a one-off patch later patches the same module M and the following CP2 does not include M at all, module M will not be port-forwarded from CP1. M will be loaded from the original base instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1245) Improve readability of missing dependency logs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1245?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1245: ------------------------------------- Fix Version/s: 2.2.0.CR1 > Improve readability of missing dependency logs > ---------------------------------------------- > > Key: WFCORE-1245 > URL: https://issues.jboss.org/browse/WFCORE-1245 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Attachments: after_1.log, after_2.log, before.log, bz1283294-reproducer.zip > > > When deploying an ear using initialize-in-order option, if one of the subdeployments contains an EJB that depends on an EJB from another subdeployment and the dependency subdeployment fails log output makes it hard to understand the root cause. > Structure of deployment is as follows: > {noformat} > reproducer.ear > |- service-locator.jar > | |- ServiceLocator (Stateless EJB) > | |- TestQueue (JNDI Resource) > |- client.jar > |- TestEjb (Stateless EJB) > |- ServiceLocator > {noformat} > If the TestQueue JNDI resource cannot be injected in the ServiceLocator, the deployment failure output lists a number of missing services per each EJB in the dependant subdeployment (.ORB, .HandleDelegate, .ValidatorFactory, etc). > When the dependant subdeployment has a larger number of EJBs the log output very quickly becomes hard to read. > Example with a single dependant EJB: > {noformat} > 14:27:43,092 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "reproducer-1.0-SNAPSHOT.ear"}) - failure description: { > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".batch.environment is missing [jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".beanmanager]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.ValidatorFactory is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.ORB is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.HandleDelegate is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".beanmanager]", > "jboss.deployment.unit.\"reproducer-1.0-SNAPSHOT.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.InstanceName is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.Validator is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]", > "jboss.naming.context.java.comp.testEar.service-locator.test_ServiceLocator.env.queue.TestQueue is missing [jboss.naming.context.java.jboss.resources.queue.TestQueue]", > "jboss.naming.context.java.comp.testEar.client.TestEjb.InAppClientContainer is missing [jboss.naming.context.java.comp.testEar.client.TestEjb]" > ], > "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => [ > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"client.jar\".INSTALL", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".CLEANUP", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".component.test_ServiceLocator.JndiBindingsService", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".component.test_ServiceLocator.START", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".deploymentCompleteService", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".jndiDependencyService", > "jboss.deployment.subunit.\"reproducer-1.0-SNAPSHOT.ear\".\"service-locator.jar\".moduleDeploymentRuntimeInformationStart", > "jboss.deployment.unit.\"reproducer-1.0-SNAPSHOT.ear\".CLEANUP" > ] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016