October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1378) KeyStore resource does not support specifying the module

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1378: ------------------------------------- Summary: KeyStore resource does not support specifying the module Key: ELY-1378 URL: https://issues.jboss.org/browse/ELY-1378 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 In other areas of the authentication configuration where the ClassLoader is used we allow an optional module to be specified, we don't do this for <keyStore><resource/><keyStore> which only accepts a name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.

by Walter Medvedeo (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ] Walter Medvedeo edited comment on DROOLS-1748 at 10/4/17 8:54 AM: ------------------------------------------------------------------ For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to which the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name to use can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties must be added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties was (Author: wmedvede): For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to with the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties should added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties > Drools workbench datasource on Wildfly domain. > ---------------------------------------------- > > Key: DROOLS-1748 > URL: https://issues.jboss.org/browse/DROOLS-1748 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final, 7.3.0.Final > Environment: Drools workbench on Wildfly domain cluster > Reporter: M C > Assignee: Petr Široký > Priority: Critical > > After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source. > [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")] > Problem does not affect Wildfly standalone configuration, only domain configuration using profiles. > WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/... > In standalone syntax is: /subsystem=datasource/. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.

by Walter Medvedeo (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ] Walter Medvedeo commented on DROOLS-1748: ----------------------------------------- For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to with the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties should added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties > Drools workbench datasource on Wildfly domain. > ---------------------------------------------- > > Key: DROOLS-1748 > URL: https://issues.jboss.org/browse/DROOLS-1748 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final, 7.3.0.Final > Environment: Drools workbench on Wildfly domain cluster > Reporter: M C > Assignee: Petr Široký > Priority: Critical > > After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source. > [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")] > Problem does not affect Wildfly standalone configuration, only domain configuration using profiles. > WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/... > In standalone syntax is: /subsystem=datasource/. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent

by Nero M (JIRA)

Nero M created WFLY-9417: ---------------------------- Summary: No default-response-code during deployment sent Key: WFLY-9417 URL: https://issues.jboss.org/browse/WFLY-9417 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 11.0.0.CR1 Reporter: Nero M Assignee: Stuart Douglas Fix For: 11.0.0.Final Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10. When a *.dodeploy file exists during server-start. The Default response code e.g. <host name="default-host" alias="localhost" default-response-code="503"> Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout. If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete. (After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms I think the server should not "hang" during the deployment-time, just like it was on WF10. Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9375) META-INF/services are always accessible from dependencies

by Alexander Kudrevatykh (JIRA)

[ https://issues.jboss.org/browse/WFLY-9375?page=com.atlassian.jira.plugin.... ] Alexander Kudrevatykh commented on WFLY-9375: --------------------------------------------- Can I guess that It will be added in something like 11.1.0 or in 10.2.0 releases? > META-INF/services are always accessible from dependencies > --------------------------------------------------------- > > Key: WFLY-9375 > URL: https://issues.jboss.org/browse/WFLY-9375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.CR1 > Reporter: Alexander Kudrevatykh > Assignee: Stuart Douglas > > I found regression in Wildfly 10.1 (10.0 and 11 CR1 also affected) - META-INF/services entries are accesible from war dependencies, even if not marked as "import" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-9406: --------------------------------------- [~tibor17], yes, not doable. The upgrade to CXF 3.2 requires also upgrading to JBossWS 5.2, which is not ready for release. And if it was ready, it would already be too late for such a change in WFLY 11, which is close to being released. > Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian Extension dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9375) META-INF/services are always accessible from dependencies

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9375?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-9375: -------------------------------------- The changes look good, however as we are about to release and we are in 'blockers only' mode they will probably not make it in till the next release. > META-INF/services are always accessible from dependencies > --------------------------------------------------------- > > Key: WFLY-9375 > URL: https://issues.jboss.org/browse/WFLY-9375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.CR1 > Reporter: Alexander Kudrevatykh > Assignee: Stuart Douglas > > I found regression in Wildfly 10.1 (10.0 and 11 CR1 also affected) - META-INF/services entries are accesible from war dependencies, even if not marked as "import" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3318) User is unable to use WildflySasl.REALM_LIST property together with DIGEST-MD5

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3318?page=com.atlassian.jira.plugi... ] Hynek Švábek commented on WFCORE-3318: -------------------------------------- Hi [~dmlloyd], Thank you, it works as you described. > User is unable to use WildflySasl.REALM_LIST property together with DIGEST-MD5 > ------------------------------------------------------------------------------ > > Key: WFCORE-3318 > URL: https://issues.jboss.org/browse/WFCORE-3318 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > User is unable to use WildflySasl.REALM_LIST property together with DIGEST-MD5. > When I look to org.wildfly.security.sasl.digest.DigestServerFactory [1] I see there callback handler and I expect that this callback handle org.wildfly.security.sasl.util.AvailableRealmsSaslServerFactory too. When you look into this factory [2] you can see that there is processed property REALM_LIST. > I added there break point but nothing happened. > If I understand correctly I found out that in SaslServerDefinitions [3] is not added AvailableRealmsSaslServerFactory when property (or some another condition) is set. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.2.0.Beta3/src/... > [2] https://github.com/wildfly-security/wildfly-elytron/blob/1.2.0.Beta3/src/... > [3] https://github.com/wildfly/wildfly-core/blob/3.0.3.Final/elytron/src/main... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Description: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian Extension dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml was: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml > Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian Extension dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Summary: Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) (was: [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)) > Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017