March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AG-56) deprecate AgroalDataSourceConfiguration.isXA()

by Luis Barreiro (JIRA)

Luis Barreiro created AG-56: ------------------------------- Summary: deprecate AgroalDataSourceConfiguration.isXA() Key: AG-56 URL: https://issues.jboss.org/browse/AG-56 Project: Agroal Issue Type: Bug Components: api Affects Versions: 0.4 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.5 It should be up to the ConnectionFactory to determine if the Datasource is in XA mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-55) Support for XAResource in the transaction API and Narayana implementation

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-55?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-55. ----------------------------- Resolution: Done > Support for XAResource in the transaction API and Narayana implementation > ------------------------------------------------------------------------- > > Key: AG-55 > URL: https://issues.jboss.org/browse/AG-55 > Project: Agroal > Issue Type: Bug > Components: api, narayana > Affects Versions: 0.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.5 > > > Building on AG-54 add support for XAResource in the transaction integration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9938) Fix iiop testsuite for JDK 10

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-9938: --------------------------------- Summary: Fix iiop testsuite for JDK 10 Key: WFLY-9938 URL: https://issues.jboss.org/browse/WFLY-9938 Project: WildFly Issue Type: Task Reporter: Tomaz Cerar Assignee: Tomaz Cerar currently on JDK10 and 11 iiop testsuite fails with jvm crash. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5271) jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime library list of WildFly 8.2.0

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-5271?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-5271: --------------------------------- Assignee: (was: David Lloyd) > jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime library list of WildFly 8.2.0 > ------------------------------------------------------------------------------------- > > Key: WFLY-5271 > URL: https://issues.jboss.org/browse/WFLY-5271 > Project: WildFly > Issue Type: Feature Request > Components: Class Loading > Affects Versions: 8.2.0.Final > Reporter: carl zhang > Priority: Minor > > In Eclipse, I chose WildFly 8.2.0 server as my local web server. Then I created Dynamic Web Project. After done, I check the project Libraries-->WildFly 8.x Runtime libraries. I can see jboss-jsf-api_2.2_spec-2.2.8.jar in the list, but cannot see jsf-impl-2.2.8-jbossorg-1.jar > So my Java codes related to jsf-impl classes cannot pass the compile. And I cannot manually add jsf-impl.jar into the project WEB_INF/lib because it cause deployment conflict. > Please add the jsf-impl jar file into default Runtime library list. I don't check 9.0.0 and 10.0.0, if it is not in their default list. Please add it in -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4333) Transaction must be sticky to ensure consistency for EJB remote invocation with JPA

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4333?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-4333. ------------------------------- Fix Version/s: 11.0.0.Final Resolution: Done > Transaction must be sticky to ensure consistency for EJB remote invocation with JPA > ----------------------------------------------------------------------------------- > > Key: WFLY-4333 > URL: https://issues.jboss.org/browse/WFLY-4333 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Tomasz Adamski > Priority: Critical > Labels: ejb, transaction > Fix For: 11.0.0.Final > > > If an application inside of a server uses standard JavaEE persistence JPA, the current implementation include a local 1. level cache which might end in inconsistent reads within the same (uncommited) transaction. > There are two reasons > - JPA must not flush changes to an entity until commit > - The 1. level cache might not read from the persistence if the entity is already loaded in a transaction > Therefore the server to server invocations of EJB's need to be sticky to one node during a transaction. The granularity must be the application. > It might be worth to use already known nodes for other applications as well. > The stickyness should be enabled automatically if a transaction is active and distributed, which is the default within the current implementation, and use the loadbalancing policy if no transaction is active. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2423) Elytron resources runtime updates without reload

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2423?page=com.atlassian.jira.plugi... ] Jan Kalina commented on WFCORE-2423: ------------------------------------ Just note, it is expected that write-attribute operations will take effect only after server reload. Admin can rely that until server reload old settings will be used. Only when {{\{allow-resource-service-restart=true\}}} is used, changes should take effect immediately - but this is not supported by elytron resources now - this is WFCORE-1953. > Elytron resources runtime updates without reload > ------------------------------------------------ > > Key: WFCORE-2423 > URL: https://issues.jboss.org/browse/WFCORE-2423 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Martin Choma > Assignee: Dmitrii Tikhomirov > > When updating elytron resources, server ends up in {{reload-required}} state. For example > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=krbSF:write-attribute(name=debug, value=true) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Make it possible for all (most - some may be impossible) resources to support runtime updates. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4522) Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-4522?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-4522: --------------------------------------- I'm a bit out-of-context here, sorry. Perhaps the reporter can explain a little bit the problem that led to creating this jira? > Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module > -------------------------------------------------------------------- > > Key: WFLY-4522 > URL: https://issues.jboss.org/browse/WFLY-4522 > Project: WildFly > Issue Type: Task > Components: Class Loading, Web Services > Affects Versions: 9.0.0.Beta2 > Reporter: Edvin Syse > Assignee: David Lloyd > > The following paths are needed for xws-security: > com/sun/org/apache/xml/internal/security > com/sun/org/apache/xml/internal/security/exceptions > com/sun/org/apache/xerces/internal/jaxp -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-47) Create a Confluence Test Plan Format

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-47?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo reassigned SWSQE-47: -------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Create a Confluence Test Plan Format > ------------------------------------ > > Key: SWSQE-47 > URL: https://issues.jboss.org/browse/SWSQE-47 > Project: Swift Sunshine QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > It is possible to create a Confluence Test Plan Format and reuse it for our needs. It suit better than using Product Requirements -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3863) META-INF/services/org.jboss.ejb.client.EJBClientInterceptor has no effect in ejb.jar

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3863?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-3863. ------------------------------- Fix Version/s: 11.0.0.Final Resolution: Done Should be fixed in 11 but I think it will only work if a per-deployment EJB client context is somehow configured. > META-INF/services/org.jboss.ejb.client.EJBClientInterceptor has no effect in ejb.jar > ------------------------------------------------------------------------------------ > > Key: WFLY-3863 > URL: https://issues.jboss.org/browse/WFLY-3863 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.1.0.Final, 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Fix For: 11.0.0.Final > > > If ejb.jar has META-INF/services/org.jboss.ejb.client.EJBClientInterceptor it has no effect on deployment/runtime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2323) Interoperability testing between current and previous versions

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-2323?page=com.atlassian.jira.plugin.... ] David Lloyd resolved WFLY-2323. ------------------------------- Assignee: (was: David Lloyd) Resolution: Won't Do This is not something I will have time for, now or maybe ever. Anyone else is free to take this on though. > Interoperability testing between current and previous versions > -------------------------------------------------------------- > > Key: WFLY-2323 > URL: https://issues.jboss.org/browse/WFLY-2323 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > > We need a complete way to verify forward and backward compatibility between all supported network protocols in all WildFly releases. This includes (but is not limited to) the following areas: > * Remoting itself > * EJB > * Remote Naming > * Remote JTA > * HornetQ > * IIOP > * Management > * Transactions > * Web Services -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 March 2018