December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11332) Docs for MP Health and MP OpenTracing are not properly included

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11332?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11332: --------------------------------- Fix Version/s: 15.0.0.Final > Docs for MP Health and MP OpenTracing are not properly included > --------------------------------------------------------------- > > Key: WFLY-11332 > URL: https://issues.jboss.org/browse/WFLY-11332 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Docs for MP Health and MP OpenTracing are not properly included -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11330) Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.CR1

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11330?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11330: --------------------------------- Fix Version/s: 15.0.0.Final > Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.CR1 > -------------------------------------------------------- > > Key: WFLY-11330 > URL: https://issues.jboss.org/browse/WFLY-11330 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Upgrade to the latest Galleon 3.x release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11166) Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11166: --------------------------------- Fix Version/s: 15.0.0.Final > Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11166 > URL: https://issues.jboss.org/browse/WFLY-11166 > Project: WildFly > Issue Type: Sub-task > Components: Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > See https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&page=... in the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11266) JAXWS Client BOM

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11266?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11266: --------------------------------- Fix Version/s: 15.0.0.Final > JAXWS Client BOM > ---------------- > > Key: WFLY-11266 > URL: https://issues.jboss.org/browse/WFLY-11266 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > The dependency management defined on WildFly, for JAXWS/CXF client, is over 1000 SLoC due to exclusions applied, which is a nightmare to manage on client apps projects, such as the jaxws-* quickstarts. > To hide the dependency management complexity on apps a new client BOM should be added wrt JAXWS, which apps can just depend on it, and should includes all dependencies excluded on WildFly dependency management. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11117) Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11117?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11117: --------------------------------- Fix Version/s: 15.0.0.Final > Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-11117 > URL: https://issues.jboss.org/browse/WFLY-11117 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 14.0.0.Final > Reporter: Jan Kašík > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Running legacy operation ends up with an error: > {code} > [standalone@localhost:9990 /] /subsystem=modcluster/:disable > { > "outcome" => "failed", > "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.", > "rolled-back" => true > } > {code} > mod_cluster configuration: > {code} > [standalone@localhost:9990 /] /subsystem=modcluster/:read-resource > { > "outcome" => "success", > "result" => { > "mod-cluster-config" => {"configuration" => undefined}, > "proxy" => {"default" => undefined} > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10796: --------------------------------- Fix Version/s: 15.0.0.Final > Warning about JSF version 'NONE' is shown in logs > -------------------------------------------------- > > Key: WFLY-10796 > URL: https://issues.jboss.org/browse/WFLY-10796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: clusterbench-ee7.ear > > > Following warning is shown in log upon server start: > {code} > 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. > {code} > Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ] James Perkins reopened WFLY-10638: ---------------------------------- > Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments > ------------------------------------------------------------------------------------------ > > Key: WFLY-10638 > URL: https://issues.jboss.org/browse/WFLY-10638 > Project: WildFly > Issue Type: Task > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all. > {quote} > HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset. > {quote} > The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10638: --------------------------------- Fix Version/s: 15.0.0.Final > Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments > ------------------------------------------------------------------------------------------ > > Key: WFLY-10638 > URL: https://issues.jboss.org/browse/WFLY-10638 > Project: WildFly > Issue Type: Task > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all. > {quote} > HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset. > {quote} > The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10638) Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10638?page=com.atlassian.jira.plugin... ] James Perkins resolved WFLY-10638. ---------------------------------- Resolution: Done > Eliminate "Transactional caches are not supported." log warning from ORM 5.3.* deployments > ------------------------------------------------------------------------------------------ > > Key: WFLY-10638 > URL: https://issues.jboss.org/browse/WFLY-10638 > Project: WildFly > Issue Type: Task > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 15.0.0.Final, 15.0.0.Beta1 > > > Currently, during deployment of ORM 5.3.* applications, the following warning is logged in the server console, four times per persistence unit. It should not appear at all. > {quote} > HHH025030: Transactional caches are not supported. The configuration option will be ignored; please unset. > {quote} > The warning comes from ORM 5.3 integration code org.infinispan.hibernate.cache.v53.InfinispanRegionFactory#unsetTransactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10580) WildFly should use Artemis' SQLProvider implementation

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10580?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10580: --------------------------------- Fix Version/s: 15.0.0.Final > WildFly should use Artemis' SQLProvider implementation > ------------------------------------------------------ > > Key: WFLY-10580 > URL: https://issues.jboss.org/browse/WFLY-10580 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > During development and integration of JDBC persistence store into WildFly, the custom implementation of SQLProvider interface \[1\] was developed for WildFly use case. The reason was that WildFly used Artemis 1.x which was at that time maintenance branch and thus development of new features was focused on 2.x branch. > In the meantime, the code has been donated to Artemis and backported in Artemis 1.5.5.jbossorg-012. > We can now remove the implementation in WildFly code base and use the Artemis one instead. > \[1\] https://github.com/apache/activemq-artemis/blob/f2b5114af8dd505e3c5c3efc1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 December 2018