June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1228) Follow up on WFCORE-1202 and make the configuration available in the management model.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1228?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1228: ------------------------------------------ If the following PR is merged we will have a new management schema version so maybe a good time to get this out the way: - https://github.com/wildfly/wildfly-core/pull/1596 > Follow up on WFCORE-1202 and make the configuration available in the management model. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1228 > URL: https://issues.jboss.org/browse/WFCORE-1228 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 2.2.0.CR3 > > > WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model. > The system property should remain supported for backwards compatibility for those migrating from servers that relied on it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1228) Follow up on WFCORE-1202 and make the configuration available in the management model.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1228?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1228: ------------------------------------- Fix Version/s: 2.2.0.CR3 (was: 3.0.0.Alpha2) > Follow up on WFCORE-1202 and make the configuration available in the management model. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1228 > URL: https://issues.jboss.org/browse/WFCORE-1228 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 2.2.0.CR3 > > > WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model. > The system property should remain supported for backwards compatibility for those migrating from servers that relied on it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6705) Namespaces / schema versions of module.xml are out of sync

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-6705: --------------------------------------- Summary: Namespaces / schema versions of module.xml are out of sync Key: WFLY-6705 URL: https://issues.jboss.org/browse/WFLY-6705 Project: WildFly Issue Type: Bug Components: Server Reporter: Rostislav Svoboda Assignee: Jason Greene Namespaces / schema versions of module.xml are out of sync: {code} grep "urn:jboss:module" jboss-eap-7.0/modules/ -R | cut -d: -f 5 | cut -d\" -f1 | sort | uniq -c 5 1.1 352 1.3 1 1.5 {code} 1.5 is used by: ./modules/system/layers/base/javax/transaction/api/main/module.xml 1.1 is used by: ./modules/system/layers/base/org/jboss/as/domain-http-error-context/eap/module.xml ./modules/system/layers/base/org/jboss/as/product/eap/module.xml ./modules/system/layers/base/org/hibernate/search/backend-jgroups/main/module.xml ./modules/system/layers/base/org/hibernate/search/serialization-avro/main/module.xml ./modules/system/layers/base/org/hibernate/search/backend-jms/main/module.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6705) Namespaces / schema versions of module.xml are out of sync

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-6705?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda reassigned WFLY-6705: --------------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > Namespaces / schema versions of module.xml are out of sync > ---------------------------------------------------------- > > Key: WFLY-6705 > URL: https://issues.jboss.org/browse/WFLY-6705 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Rostislav Svoboda > Assignee: Tomaz Cerar > > Namespaces / schema versions of module.xml are out of sync: > {code} > grep "urn:jboss:module" jboss-eap-7.0/modules/ -R | cut -d: -f 5 | cut -d\" -f1 | sort | uniq -c > 5 1.1 > 352 1.3 > 1 1.5 > {code} > 1.5 is used by: > ./modules/system/layers/base/javax/transaction/api/main/module.xml > 1.1 is used by: > ./modules/system/layers/base/org/jboss/as/domain-http-error-context/eap/module.xml > ./modules/system/layers/base/org/jboss/as/product/eap/module.xml > ./modules/system/layers/base/org/hibernate/search/backend-jgroups/main/module.xml > ./modules/system/layers/base/org/hibernate/search/serialization-avro/main/module.xml > ./modules/system/layers/base/org/hibernate/search/backend-jms/main/module.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6704) Duplicated javax.api in javax/xml/rpc/api/main/module.xml

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-6704?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda reassigned WFLY-6704: --------------------------------------- Assignee: Rostislav Svoboda (was: Alessio Soldano) > Duplicated javax.api in javax/xml/rpc/api/main/module.xml > --------------------------------------------------------- > > Key: WFLY-6704 > URL: https://issues.jboss.org/browse/WFLY-6704 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Minor > > https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > javax.api is duplicated, see line 27 and 30. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6704) Duplicated javax.api in javax/xml/rpc/api/main/module.xml

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-6704: --------------------------------------- Summary: Duplicated javax.api in javax/xml/rpc/api/main/module.xml Key: WFLY-6704 URL: https://issues.jboss.org/browse/WFLY-6704 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Rostislav Svoboda Assignee: Alessio Soldano Priority: Minor https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... javax.api is duplicated, see line 27 and 30. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1591) jboss-cli help message lacks --properties argument

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1591?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-1591: ------------------------------ Labels: downstream_dependency (was: ) > jboss-cli help message lacks --properties argument > -------------------------------------------------- > > Key: WFCORE-1591 > URL: https://issues.jboss.org/browse/WFCORE-1591 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Labels: downstream_dependency > > --properties is not listed among valid jboss-cli arguments. Properties are used for CLI property substitution - https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > {noformat} > [pkremens@localhost bin] $ ./jboss-cli.sh --help > help > [pkremens@localhost bin] $ grep -c properties help > 0 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1321) Statement.cancel() is not invoked until the statement is completed

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1321?page=com.atlassian.jira.plugin... ] Lin Gao resolved JBJCA-1321. ---------------------------- Resolution: Done > Statement.cancel() is not invoked until the statement is completed > ------------------------------------------------------------------ > > Key: JBJCA-1321 > URL: https://issues.jboss.org/browse/JBJCA-1321 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final > Reporter: lorenzo benvenuti > Assignee: Lin Gao > Priority: Critical > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > Hi, > in our application we are using the {{Statement.cancel()}} method to stop long-running queries; in Wildfly 9.0.2 this is not working because the {{cancel()}} method is synchronized using a lock which is not released until the query is executed. In {{WrappedStatement}}: > {code:java} > public void cancel() throws SQLException > { > if (doLocking) > lock(); > try > { > /* ... */ > {code} > It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final {{WrappedStatement.cancel}} doesn't try to obtain the lock. > Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion. > Thank you, > lorenzo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1321) Statement.cancel() is not invoked until the statement is completed

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1321?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1321: --------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/526, https://github.com/ironjacamar/ironjacamar/pull/527 > Statement.cancel() is not invoked until the statement is completed > ------------------------------------------------------------------ > > Key: JBJCA-1321 > URL: https://issues.jboss.org/browse/JBJCA-1321 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final > Reporter: lorenzo benvenuti > Assignee: Lin Gao > Priority: Critical > Fix For: WildFly/IronJacamar 1.3.5.Final, 1.2.8.Final > > > Hi, > in our application we are using the {{Statement.cancel()}} method to stop long-running queries; in Wildfly 9.0.2 this is not working because the {{cancel()}} method is synchronized using a lock which is not released until the query is executed. In {{WrappedStatement}}: > {code:java} > public void cancel() throws SQLException > { > if (doLocking) > lock(); > try > { > /* ... */ > {code} > It seems this behaviour has changed from version 1.2.5.Final of ironjacamar-jdbc; in version 1.2.4.Final {{WrappedStatement.cancel}} doesn't try to obtain the lock. > Probably I'm missing something, but to me it's strange that in order to cancel a statement you have to wait for its completion. > Thank you, > lorenzo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1591) jboss-cli help message lacks --properties argument

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1591?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-4979 to WFCORE-1591: ------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1591 (was: JBEAP-4979) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) Target Release: (was: 7.backlog.GA) Affects Version/s: 3.0.0.Alpha1 (was: 7.0.0.GA) > jboss-cli help message lacks --properties argument > -------------------------------------------------- > > Key: WFCORE-1591 > URL: https://issues.jboss.org/browse/WFCORE-1591 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > > --properties is not listed among valid jboss-cli arguments. Properties are used for CLI property substitution - https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > {noformat} > [pkremens@localhost bin] $ ./jboss-cli.sh --help > help > [pkremens@localhost bin] $ grep -c properties help > 0 > {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 June 2016