October 2017 - jboss-jira - Jboss List Archives

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

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1748: ------------------------------------- Assignee: Petr Široký (was: Edson Tirelli) > 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, 7 months

1
0
0 / 0

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

by M C (JIRA)

M C created DROOLS-1748: --------------------------- Summary: 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.3.0.Final, 7.0.0.Final Environment: Drools workbench on Wildfly domain cluster Reporter: M C Assignee: Edson Tirelli 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1747) Fix Declaring Enumerative Types Code Snippets 8.7.1.1

by Luca Molteni (JIRA)

Luca Molteni created DROOLS-1747: ------------------------------------ Summary: Fix Declaring Enumerative Types Code Snippets 8.7.1.1 Key: DROOLS-1747 URL: https://issues.jboss.org/browse/DROOLS-1747 Project: Drools Issue Type: Task Components: docs Reporter: Luca Molteni Assignee: Mario Fusco The code snipper in the section 8.7.1.1 on the enum is wrong, it has been copy and pasted from the previous one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

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

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9406: ------------------------------------ https://github.com/wildfly/wildfly/pull/10557 is now for separate jira [WFLY-9413]. > [WildFly 11] 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9413) Update EclipseLink module to remove unused asm/javassist dependencies

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9413?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-9413: ------------------------------- Description: The EclipseLink module doesn't depend on asm/javassist modules. (was: The EclipseLink doesn't depend on asm/javassist modules.) > Update EclipseLink module to remove unused asm/javassist dependencies > --------------------------------------------------------------------- > > Key: WFLY-9413 > URL: https://issues.jboss.org/browse/WFLY-9413 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > > The EclipseLink module doesn't depend on asm/javassist modules. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9413) Update EclipseLink module to remove unused asm/javassist dependencies

by Scott Marlow (JIRA)

Scott Marlow created WFLY-9413: ---------------------------------- Summary: Update EclipseLink module to remove unused asm/javassist dependencies Key: WFLY-9413 URL: https://issues.jboss.org/browse/WFLY-9413 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 12.0.0.Alpha1 The EclipseLink doesn't depend on asm/javassist modules. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3180) ElytronSubsystemMessages uses double quotes to surround string literals

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3180?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3180: ------------------------------------------ Hi [~yersan] -- sure that would be fine. > ElytronSubsystemMessages uses double quotes to surround string literals > ----------------------------------------------------------------------- > > Key: WFCORE-3180 > URL: https://issues.jboss.org/browse/WFCORE-3180 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Priority: Minor > > Lots of things like this: > @Message(id = 910, value = "Password cannot be resolved for key-store \"%s\"") > Use ' instead of \". If the string ends up in a DMR ModelNode, which it often does, the output looks bad when double quotes are present. > For this ModelNode > ModelNode node = new ModelNode("Password cannot be resolved for key-store \"%s\""); > > A call to node.toString() produces > "Password cannot be resolved for key-store \"%s\"" > node.asString() is better, but that requires a special call vs the standard Object.toString > Password cannot be resolved for key-store "%s" > This is minor since we can try to ensure asString is used or perhaps even consider changing how toString works. But I think single quotes are a better practice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3180) ElytronSubsystemMessages uses double quotes to surround string literals

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3180?page=com.atlassian.jira.plugi... ] Yeray Borges commented on WFCORE-3180: -------------------------------------- [~brian.stansberry] just a random thought, would you be interested in a solution that works with LocalDescription.properties as well? There are text descriptions using double quotes there. Those descriptions are "badly" scaped when they are displayed by read-resource-description for example, maybe it could be useful a general solution that takes those cases into account. > ElytronSubsystemMessages uses double quotes to surround string literals > ----------------------------------------------------------------------- > > Key: WFCORE-3180 > URL: https://issues.jboss.org/browse/WFCORE-3180 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Priority: Minor > > Lots of things like this: > @Message(id = 910, value = "Password cannot be resolved for key-store \"%s\"") > Use ' instead of \". If the string ends up in a DMR ModelNode, which it often does, the output looks bad when double quotes are present. > For this ModelNode > ModelNode node = new ModelNode("Password cannot be resolved for key-store \"%s\""); > > A call to node.toString() produces > "Password cannot be resolved for key-store \"%s\"" > node.asString() is better, but that requires a special call vs the standard Object.toString > Password cannot be resolved for key-store "%s" > This is minor since we can try to ensure asString is used or perhaps even consider changing how toString works. But I think single quotes are a better practice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9130) RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9130?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9130: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10552 (was: https://github.com/wildfly/wildfly/pull/10548) > RemoteStatefulEJBConcurrentFailoverTestCase fails intermittently > ---------------------------------------------------------------- > > Key: WFLY-9130 > URL: https://issues.jboss.org/browse/WFLY-9130 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Final > > > This is looks like an issue with EJB client failing to retry the EJB lookup on EJBComponentUnavailableException. > e.g. > https://ci.wildfly.org/viewLog.html?buildId=67940&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9363) Fix failing clustering EJB2 tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9363?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9363: --------------------------------- Component/s: Test Suite > Fix failing clustering EJB2 tests > ---------------------------------- > > Key: WFLY-9363 > URL: https://issues.jboss.org/browse/WFLY-9363 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {{org.jboss.as.test.clustering.extended.ejb2}} package. > These tests have been consistently failing with the EJB client upgrade. Having them not executed within CI runs deems these tests to be consistently broken. > https://ci.wildfly.org/viewLog.html?buildId=74894&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 October 2017