February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3434) ERROR in logs while using vault in system properties

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3434?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3434: -------------------------------- Fix Version/s: 3.1.0.Final > ERROR in logs while using vault in system properties > ---------------------------------------------------- > > Key: WFCORE-3434 > URL: https://issues.jboss.org/browse/WFCORE-3434 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 4.0.0.Alpha3 > Environment: JBoss EAP 7.1 Beta > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 4.0.0.Alpha4, 3.1.0.Final > > > Getting below ERROR message in server.log when *Picketbox Vault expressions* used in *system properties*.: > {code:java} > ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0230: Vault is not initialized; resolution of vault expressions is not possible > {code} > Below expressions are resolving fine but due to race condition this ERROR message got printed in the logs. > {code:java} > <system-properties> > <property name="javax.net.ssl.trustStore" value="/home/jboss-eap-7.1/vault/vault.keystore"/> > <property name="javax.net.ssl.trustStorePassword" value="${VAULT::datasource::password::1}"/> > </system-properties> > <vault> > <vault-option name="KEYSTORE_URL" value="/home/jboss-eap-7.1/vault/vault.keystore"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-2GAtdnlXL8H"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="44"/> > <vault-option name="ENC_FILE_DIR" value="/home/jboss-eap-7.1/vault/"/> > </vault> > {code} > Expression is actually resolving to the correct value and that can be check using below CLI command : > {code:java} > /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties). > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3448) Unable to set multiple ssl protocols and ciphers on security-realms using system properties

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3448?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3448: -------------------------------- Fix Version/s: 3.1.0.Final > Unable to set multiple ssl protocols and ciphers on security-realms using system properties > ------------------------------------------------------------------------------------------- > > Key: WFCORE-3448 > URL: https://issues.jboss.org/browse/WFCORE-3448 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Derek Horton > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha6, 3.1.0.Final > > > It is not possible to set the ssl protocol and ciphers on a security-realm using system property if multiple protocols and/or ciphers are needed. > Setting the "enabled-cipher-suites" and "enabled-protocols" using a system property works if the system property value resolves to a single value ("TLSv1.2" for example). > An error is thrown if the system property has multiple values (-Dtlsversion="TLSv1.1 TLSv1.2"). Here is the error that is generated: > 13:20:43,315 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ManagementRealm.ssl-context: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ManagementRealm.ssl-context: WFLYDM0096: No protocols in common, supported=([SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2]), requested=([TLSv1.1 TLSv1.2]) > at org.jboss.as.domain.management.security.SSLContextService.wrapSslContext(SSLContextService.java:137) > at org.jboss.as.domain.management.security.SSLContextService.start(SSLContextService.java:102) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3338) Management returning success for read-attribute on non-existent domain server path

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3338?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3338: -------------------------------- Fix Version/s: 3.1.0.Final > Management returning success for read-attribute on non-existent domain server path > ---------------------------------------------------------------------------------- > > Key: WFCORE-3338 > URL: https://issues.jboss.org/browse/WFCORE-3338 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.4.Final > Reporter: Brad Maxwell > Assignee: Chao Wang > Fix For: 4.0.0.Alpha1, 3.1.0.Final > > > In Wildfly, a command such as this with a non-existent path returns success instead of failed: > {code} > /host=master/server=nonExistant:read-attribute(name=runtime-configuration-state) > { > "outcome" => "success", > "result" => "stopped" > } > {code} > Where as in EAP 6.4: > {code} > [domain@localhost:9999 /] /host=master/server=server-NOT-EXIST:read-attribute(name=server-state) > Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [ > ("host" => "master"), > ("server" => "server-NOT-EXIST") > ]" > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3336) Not able to separate application(EAR) logging with the use of logging profile

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3336?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3336: -------------------------------- Fix Version/s: 3.1.0.Final > Not able to separate application(EAR) logging with the use of logging profile > ----------------------------------------------------------------------------- > > Key: WFCORE-3336 > URL: https://issues.jboss.org/browse/WFCORE-3336 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 4.0.0.Alpha1, 3.1.0.Final > > Attachments: 01933631-new.tar.gz, logging-profile.zip > > > Two ear files are deployed on EAP instance and both are configured to use different logging profile through EAR/META-INF/MANIFEST.MF file. > WAR file from EAR uses some libraries those are present in the "lib" folder of each ear file. Application1.ear which logs in app1.log and Application2.ear which logs in app2.log. > when we access application we can see logging from EAR1 into EAR2 log file . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3416) User redirected with HTTP 301 instead of 302 in admin-only mode

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3416?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3416: -------------------------------- Fix Version/s: 3.1.0.Final > User redirected with HTTP 301 instead of 302 in admin-only mode > --------------------------------------------------------------- > > Key: WFCORE-3416 > URL: https://issues.jboss.org/browse/WFCORE-3416 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 4.0.0.Alpha2 > Environment: JBoss EAP 7.1.0.Alpha and 7.0.5 > OS : RHEL 7 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 4.0.0.Alpha5, 3.1.0.Final > > > The issue isn't that the console isn't working in admin-only mode. It's that a permanent redirect is issued for a temporary condition. The redirect from the console root URL should use a 302, not a 301, since the appropriate target depends on whether the server was started in admin-only mode. > The root URL of the admin console ( / ) does a permanent redirect (301) to the final target. Normally it's a redirect to /console/index.html. But if the server is started in admin-only mode then /console/index.html doesn't return a sensible error (Chrome reports that the connection to the server was lost). If a browser has cached the permanent redirect, it won't be clear why the console isn't working. > On the other hand if the server is started in domain-only mode and the browser caches the permanent redirect to /consoleerror/noConsoleForAdminModeError.html, then the browser will continue to load /consoleerror/noConsoleForAdminModeError.html even after the server is started without --admin-only. > A 301 redirect is inappropriate since "admin-only" isn't a permanent state. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3268) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3268?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3268: -------------------------------- Fix Version/s: 3.1.0.Final > module defined in jboss-deployment-structure.xml with fails to parse when annotations=true > ------------------------------------------------------------------------------------------ > > Key: WFCORE-3268 > URL: https://issues.jboss.org/browse/WFCORE-3268 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 3.0.2.CR1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 4.0.0.Alpha1, 3.1.0.Final > > Attachments: application-exception-using-dynamic-module.ear > > > {code} > 21:15:06,004 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]", > "jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]" > ]} > 21:15:06,027 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "application-exception-using-dynamic-module.ear" (runtime-name : "application-exception-using-dynamic-module.ear") > 21:15:06,028 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.module.service."deployment.application-exception-api".main (missing) dependents: [service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-ejb.jar".PARSE, service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-client-singleton.jar".PARSE] > {code} > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <module name="deployment.application-exception-api"> > <resources> > <resource-root path="application-exception-api.jar"/> > </resources> > <dependencies> > <module name="javaee.api" export="true"/> > <module name="javax.api" export="true"/> > </dependencies> > </module> > <sub-deployment name="application-exception-ejb.jar"> > <dependencies> > <module name="deployment.application-exception-api" annotations="true" meta-inf="export"/> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3290) Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3290?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3290: -------------------------------- Fix Version/s: 3.1.0.Final > Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6 > ------------------------------------------------------------------------------- > > Key: WFCORE-3290 > URL: https://issues.jboss.org/browse/WFCORE-3290 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Remoting > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: 4.0.0.Alpha1, 3.1.0.Final > > > When a slave running EAP 6 connects to a current DC, the following appears in the DC log even though the endpoint resource should be discarded: > {code}2017-08-07 14:35:09,000 WARN [org.jboss.as.controller.transformer.slave] (Host Controller Service Threads - 55) WFLYCTL0032: There were problems during the transformation process for target host: 'slave' > Problems found: > [ WFLYCTL0303: Resource [ > ("profile" => "full-ha"), > ("subsystem" => "remoting"), > ("configuration" => "endpoint") > ] is rejected on the target host, and will need to be ignored on the host > ] > {code} > This is because the remoting endpoint transformation was overly simplified in https://github.com/wildfly/wildfly-core/pull/2577 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9773) Construction/initialization of custom filter instance, configured in undertow subsystem uses incorrect/undefined TCCL

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9773?page=com.atlassian.jira.plugin.... ] jaikiran pai reassigned WFLY-9773: ---------------------------------- Assignee: Stuart Douglas (was: David Lloyd) > Construction/initialization of custom filter instance, configured in undertow subsystem uses incorrect/undefined TCCL > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9773 > URL: https://issues.jboss.org/browse/WFLY-9773 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final, 11.0.0.Final > Environment: Windows 10 > Java 1.8.0_112 > WildFly 10.1.Final > Reporter: Thomas Isaksen > Assignee: Stuart Douglas > Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip > > > Custom module class loading fails with ClassNotFoundException > I have attached a reproducible example here but it is also available on the forum thread mentioned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3522) Module dependency order for a deployment is wrong

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3522?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3522: -------------------------------- Fix Version/s: 3.1.0.Final > Module dependency order for a deployment is wrong > ------------------------------------------------- > > Key: WFCORE-3522 > URL: https://issues.jboss.org/browse/WFCORE-3522 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.8.Final > Reporter: Ken Finnigan > Assignee: David Lloyd > Priority: Blocker > Fix For: 4.0.0.Beta1, 3.1.0.Final > > > Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile. > With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... > After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead. > He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9773) Construction/initialization of custom filter instance, configured in undertow subsystem uses incorrect/undefined TCCL

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9773?page=com.atlassian.jira.plugin.... ] jaikiran pai updated WFLY-9773: ------------------------------- Summary: Construction/initialization of custom filter instance, configured in undertow subsystem uses incorrect/undefined TCCL (was: Bug in Module Classloading) > Construction/initialization of custom filter instance, configured in undertow subsystem uses incorrect/undefined TCCL > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9773 > URL: https://issues.jboss.org/browse/WFLY-9773 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final, 11.0.0.Final > Environment: Windows 10 > Java 1.8.0_112 > WildFly 10.1.Final > Reporter: Thomas Isaksen > Assignee: David Lloyd > Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip > > > Custom module class loading fails with ClassNotFoundException > I have attached a reproducible example here but it is also available on the forum thread mentioned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018