April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11935) Remove unused commons-cli, commons-lang and commons-lang3 modules

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11935: --------------------------------------- Summary: Remove unused commons-cli, commons-lang and commons-lang3 modules Key: WFLY-11935 URL: https://issues.jboss.org/browse/WFLY-11935 Project: WildFly Issue Type: Task Components: JSF, Server Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 17.0.0.Beta1 Currently WildFly includes 3 JBoss Modules modules that are not used in our runtime. I would like to remove these in WildFly 17: org.apache.commons.cli org.apache.commons.lang[1] org.apache.commons.lang3 All three have the "jboss.api" = "private" property set in their module.xml, meaning they are marked for internal use only and we are free to remove them. End user applications should not have referenced these modules, and if they do we log a WARN on boot advising not to do that. However, other projects that extend WildFly (i.e. write their own subsystems) may be using these modules, so I sent out a notification that these may be going away: http://lists.jboss.org/pipermail/wildfly-dev/2019-April/006829.html -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1778) Enhanced Audit Logging - Feature parity with legacy audit logging

by Justin Cook (Jira)

Justin Cook created ELY-1778: -------------------------------- Summary: Enhanced Audit Logging - Feature parity with legacy audit logging Key: ELY-1778 URL: https://issues.jboss.org/browse/ELY-1778 Project: WildFly Elytron Issue Type: Feature Request Components: Audit Reporter: Justin Cook Assignee: Justin Cook This RFE for Enhanced Audit Logging in WildFly Elytron is for feature parity with legacy audit logging via: * Additional audit events * An "Audit" annotation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11934) Upgrade wildfly-arquillian from 2.1.1.Final to 2.2.0.Final

by James Perkins (Jira)

James Perkins created WFLY-11934: ------------------------------------ Summary: Upgrade wildfly-arquillian from 2.1.1.Final to 2.2.0.Final Key: WFLY-11934 URL: https://issues.jboss.org/browse/WFLY-11934 Project: WildFly Issue Type: Component Upgrade Components: Test Suite Reporter: James Perkins Assignee: James Perkins This will also require an upgrade to Arquillian Core and the Shrinkwrap Descriptors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

Claudio Weiler created WFLY-11933: ------------------------------------- Summary: Error when accessing metrics with RBAC enabled Key: WFLY-11933 URL: https://issues.jboss.org/browse/WFLY-11933 Project: WildFly Issue Type: Bug Components: MP Metrics Affects Versions: 16.0.0.Final Reporter: Claudio Weiler Assignee: Jeff Mesnil When RBAC is enabled for management in Wildfly 16, metrics throws exception: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ ("subsystem" => "datasources"), ("data-source" => "ExampleDS"), ("statistics" => "pool") ]: "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"datasources\"), (\"data-source\" => \"ExampleDS\"), (\"statistics\" => \"pool\") ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3841) [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3841?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3841: ------------------------------------ Description: An error is raised when a DMN file with imports is saved *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The following error will appear in the server log. *Error:* {code} 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' {code} was: An error is raised when a DMN file with imports is saved *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The error [1] will appear in the server log. *Error:* {code} 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' {code} > [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3841 > URL: https://issues.jboss.org/browse/DROOLS-3841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > An error is raised when a DMN file with imports is saved > *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The following error will appear in the server log. > *Error:* > {code} > 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3841) [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-3841: --------------------------------------- Summary: [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved Key: DROOLS-3841 URL: https://issues.jboss.org/browse/DROOLS-3841 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes An error is raised when a DMN file with imports is saved *Steps to reproduce: *Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The error [1] will appear in the server log. *Error: * {code} 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3841) [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3841?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3841: ------------------------------------ Description: An error is raised when a DMN file with imports is saved *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The error [1] will appear in the server log. *Error:* {code} 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' {code} was: An error is raised when a DMN file with imports is saved *Steps to reproduce: *Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The error [1] will appear in the server log. *Error: * {code} 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' {code} > [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3841 > URL: https://issues.jboss.org/browse/DROOLS-3841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > An error is raised when a DMN file with imports is saved > *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The error [1] will appear in the server log. > *Error:* > {code} > 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3840) Extend Rule runner to support additional parameters

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3840?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3840: ---------------------------------- Story Points: 3 > Extend Rule runner to support additional parameters > --------------------------------------------------- > > Key: DROOLS-3840 > URL: https://issues.jboss.org/browse/DROOLS-3840 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use these rule parameters > https://issues.jboss.org/browse/DROOLS-3572 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3840) Extend Rule runner to support additional parameters

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3840: ------------------------------------- Summary: Extend Rule runner to support additional parameters Key: DROOLS-3840 URL: https://issues.jboss.org/browse/DROOLS-3840 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Use these rule parameters https://issues.jboss.org/browse/DROOLS-3572 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AG-114) Connection failure stack traces are confusing

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-114?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-114. ---------------------------- Resolution: Done Thanks! > Connection failure stack traces are confusing > --------------------------------------------- > > Key: AG-114 > URL: https://issues.jboss.org/browse/AG-114 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.4 > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 1.5 > > > The stack traces for failed connections are not correct due to incorrect handling of exceptions thrown from {{Future.get()}}. They include intermediate causes that are not relevant to the problem or any debugging effort. > Here's an example too-long stack trace: > {noformat} > java.sql.SQLException: Exception while creating new connection > at io.agroal.pool.ConnectionPool.handlerFromSharedCache(ConnectionPool.java:225) > at io.agroal.pool.ConnectionPool.getConnection(ConnectionPool.java:146) > at io.agroal.pool.DataSource.getConnection(DataSource.java:61) > at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) > at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180) > at org.hibernate.resource.transaction.backend.jta.internal.DdlTransactionIsolatorJtaImpl.<init>(DdlTransactionIsolatorJtaImpl.java:59) > ... 20 more > Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Exception while creating new connection > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at io.agroal.pool.ConnectionPool.handlerFromSharedCache(ConnectionPool.java:193) > ... 25 more > Caused by: java.lang.RuntimeException: Exception while creating new connection > at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:357) > at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:337) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:63) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:481) > at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193) > Caused by: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: localhost" [90067-197] > at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:451) > at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:332) > at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:124) > at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:103) > at org.h2.Driver.connect(Driver.java:69) > at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:178) > at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:348) > ... 8 more > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:5193) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at org.h2.util.NetUtils.createSocket(NetUtils.java:103) > at org.h2.util.NetUtils.createSocket(NetUtils.java:83) > at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:114) > at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:447) > ... 14 more > {noformat} > Here's the preferred output: > {noformat} > org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: localhost" [90067-197] > at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:451) > at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:332) > at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:124) > at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:103) > at org.h2.Driver.connect(Driver.java:69) > at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:178) > at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:355) > at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:344) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:63) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:481) > at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193) > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:5193) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at org.h2.util.NetUtils.createSocket(NetUtils.java:103) > at org.h2.util.NetUtils.createSocket(NetUtils.java:83) > at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:114) > at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:447) > ... 14 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

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