May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on ISPN-9214: ------------------------------------ Thanks [~pruivo], the JNDI name still looks correct. For the direct reference to com.arjuna.ats.jta.TransactionManager, I'm not exactly sure of what that needs to change to (beyond changing to use org.wildfly.transaction.client.ContextTransactionManager#getInstance.) Does Infinispan need to manage its own TM instance when not running inside of WF? Do you have code to com.arjuna.ats.jta.TransactionManager setup code somewhere? I assume that you still need your com.arjuna.ats.jta.TransactionManager setup code, but will also now need to initialize org.wildfly.transaction.client.ContextTransactionManager to work with the started com.arjuna.ats.jta.TransactionManager. What do you recommend [~dmlloyd] + [~tomjenkinson] that Infinispan change in their code? > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+, JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}}, needs to instead use the WildFly Transaction Client, or it may see incorrect TX status. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] Scott Marlow updated ISPN-9214: ------------------------------- Description: Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+, JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}}, needs to instead use the WildFly Transaction Client, or it may see incorrect TX status. I assume the Infinispan standalone client will need to be updated as well. See: - https://hibernate.atlassian.net/browse/HHH-12640 - https://hibernate.atlassian.net/browse/HHH-12620 was: Scott has been changing classes such as {{JBossStandaloneJTAManagerLookup}} in other projects as apparently the JTA client code should no longer use {{com.arjuna.ats.jta.TransactionManager}}. I assume the Infinispan standalone client will need to be updated as well. See: - https://hibernate.atlassian.net/browse/HHH-12640 - https://hibernate.atlassian.net/browse/HHH-12620 > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+, JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}}, needs to instead use the WildFly Transaction Client, or it may see incorrect TX status. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-9214: ----------------------------------- here: https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... and JNDI name here: https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott has been changing classes such as {{JBossStandaloneJTAManagerLookup}} in other projects as apparently the JTA client code should no longer use {{com.arjuna.ats.jta.TransactionManager}}. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on ISPN-9214: ------------------------------------ [~dmlloyd] fyi [~sannegrinovero] do you have a web link showing where Infinispan references the Arjuna/Narayna TM directly? > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott has been changing classes such as {{JBossStandaloneJTAManagerLookup}} in other projects as apparently the JTA client code should no longer use {{com.arjuna.ats.jta.TransactionManager}}. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9149) Some TestNG tests do not have any group

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9149?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9149: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6018 > Some TestNG tests do not have any group > --------------------------------------- > > Key: ISPN-9149 > URL: https://issues.jboss.org/browse/ISPN-9149 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > The test suite only runs tests in groups {{functional,unit,xsite,arquillian}}, tests that don't have any group set with {{@Test groups=...}} are excluded. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9149) Some TestNG tests do not have any group

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9149?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9149: ------------------------------- Status: Open (was: New) > Some TestNG tests do not have any group > --------------------------------------- > > Key: ISPN-9149 > URL: https://issues.jboss.org/browse/ISPN-9149 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > The test suite only runs tests in groups {{functional,unit,xsite,arquillian}}, tests that don't have any group set with {{@Test groups=...}} are excluded. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-9214: ------------------------------------- Summary: JBossStandaloneJTAManagerLookup is using deprecated integration names Key: ISPN-9214 URL: https://issues.jboss.org/browse/ISPN-9214 Project: Infinispan Issue Type: Task Components: Core, Integration Reporter: Sanne Grinovero Assignee: Scott Marlow Priority: Minor Scott has been changing classes such as {{JBossStandaloneJTAManagerLookup}} in other projects as apparently the JTA client code should no longer use {{com.arjuna.ats.jta.TransactionManager}}. I assume the Infinispan standalone client will need to be updated as well. See: - https://hibernate.atlassian.net/browse/HHH-12640 - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9214: ---------------------------------- Status: Open (was: New) > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott has been changing classes such as {{JBossStandaloneJTAManagerLookup}} in other projects as apparently the JTA client code should no longer use {{com.arjuna.ats.jta.TransactionManager}}. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9205) LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-9205?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned ISPN-9205: ------------------------------------ Assignee: Gail Badner > LocalInvalidationSynchronization#afterCompletion calls PutFromLoadValidator#endInvalidatingKey with arguments in incorrect order > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9205 > URL: https://issues.jboss.org/browse/ISPN-9205 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.2.3.Final > Reporter: Gail Badner > Assignee: Gail Badner > Fix For: 9.2.4.Final > > > {{LocalInvalidationSynchronization#afterCompletion}} calls: > {{validator.endInvalidatingKey(key, lockOwner, ...) }} > Instead, it should call: > {{validator.endInvalidatingKey(lockOwner, key, ... }} > I'll create a PR shortly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9213) Update to Hibernate ORM 5.3.1 and Hibernate Search 5.10.1

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-9213?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-9213: ---------------------------------- Status: Open (was: New) > Update to Hibernate ORM 5.3.1 and Hibernate Search 5.10.1 > --------------------------------------------------------- > > Key: ISPN-9213 > URL: https://issues.jboss.org/browse/ISPN-9213 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Optional > Fix For: 9.3.0.CR1 > > > This is not particularly urgent or relevant to Infinispan directly, but it would align the dependencies with the versions included in WildFly 13. > Might reduce some overall efforts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018