March 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2345: ----------------------------------- BTW whilst the base docker image is immutable, if you make changes to a running instance then they will be saved but under a new image id (unless you run with the -rm option). So it's not quite as bad as we may have thought, i.e., as long as we tell the developer/user that they need to rerun with the new image id, they will see transaction logs between instantiations. https://gist.github.com/goldmann/b547c230e402d702a140 > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Labels: docker > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2351: --------------------------------------- Looks like this depends on the environment. Does not fail on my machine, but fails on Jaime quite regularly. However, failure appears on different tests, thus have to execute all XTS crash recovery test suite. > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2350) CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability)

by Tomasz Krakowiak (JIRA)

[ https://issues.jboss.org/browse/JBTM-2350?page=com.atlassian.jira.plugin.... ] Tomasz Krakowiak resolved JBTM-2350. ------------------------------------ Resolution: Done > CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) > ----------------------------------------------------------------------------------------- > > Key: JBTM-2350 > URL: https://issues.jboss.org/browse/JBTM-2350 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 > Environment: Wildfly 8.1.0, Wildfly 8.2.0, linux, OS X > Reporter: Tomasz Krakowiak > Assignee: Tomasz Krakowiak > Fix For: 5.0.5 > > > The problem is with availability of `UserTransaction`. > Availability of UserTransaction is stored in `ServerVMClientUserTransaction.isAvailables` which is `ThreadLocal<Boolean>`. > `TransactionalInterceptorRequired` when intercepting call, stores thread local value of `isAvailables` in `TransactionalInterceptorBase.previousUserTransactionAvailability` field of interceptor - which is of type boolean(not thread local). > Here's a story: > We have a bean - `beanA` - with single method annotated transactional - `beanA.transactional()`. > This method is being called from two threads, where: > - Thread 1 is participating in BMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is true. > - Thread 2 is participating in CMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is false. > Both threads call `beanA.transactional()` at the same time. > What may happen: > 1. Thread 1 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to true. > 2. Thread 2 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to false. > 3. Thread 1 - exits method `beanA.transactional()` > Interceptor restores thread local value of `isAvailables` to false (leaked value from thread 2!) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2350) CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability)

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2350?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned JBTM-2350: -------------------------------------- Assignee: Tomasz Krakowiak (was: Tom Jenkinson) > CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) > ----------------------------------------------------------------------------------------- > > Key: JBTM-2350 > URL: https://issues.jboss.org/browse/JBTM-2350 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 > Environment: Wildfly 8.1.0, Wildfly 8.2.0, linux, OS X > Reporter: Tomasz Krakowiak > Assignee: Tomasz Krakowiak > Fix For: 5.0.5 > > > The problem is with availability of `UserTransaction`. > Availability of UserTransaction is stored in `ServerVMClientUserTransaction.isAvailables` which is `ThreadLocal<Boolean>`. > `TransactionalInterceptorRequired` when intercepting call, stores thread local value of `isAvailables` in `TransactionalInterceptorBase.previousUserTransactionAvailability` field of interceptor - which is of type boolean(not thread local). > Here's a story: > We have a bean - `beanA` - with single method annotated transactional - `beanA.transactional()`. > This method is being called from two threads, where: > - Thread 1 is participating in BMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is true. > - Thread 2 is participating in CMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is false. > Both threads call `beanA.transactional()` at the same time. > What may happen: > 1. Thread 1 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to true. > 2. Thread 2 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to false. > 3. Thread 1 - exits method `beanA.transactional()` > Interceptor restores thread local value of `isAvailables` to false (leaked value from thread 2!) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2350) CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability)

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2350?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2350: ----------------------------------- Fix Version/s: 5.0.5 > CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) > ----------------------------------------------------------------------------------------- > > Key: JBTM-2350 > URL: https://issues.jboss.org/browse/JBTM-2350 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 > Environment: Wildfly 8.1.0, Wildfly 8.2.0, linux, OS X > Reporter: Tomasz Krakowiak > Assignee: Tom Jenkinson > Fix For: 5.0.5 > > > The problem is with availability of `UserTransaction`. > Availability of UserTransaction is stored in `ServerVMClientUserTransaction.isAvailables` which is `ThreadLocal<Boolean>`. > `TransactionalInterceptorRequired` when intercepting call, stores thread local value of `isAvailables` in `TransactionalInterceptorBase.previousUserTransactionAvailability` field of interceptor - which is of type boolean(not thread local). > Here's a story: > We have a bean - `beanA` - with single method annotated transactional - `beanA.transactional()`. > This method is being called from two threads, where: > - Thread 1 is participating in BMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is true. > - Thread 2 is participating in CMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is false. > Both threads call `beanA.transactional()` at the same time. > What may happen: > 1. Thread 1 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to true. > 2. Thread 2 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to false. > 3. Thread 1 - exits method `beanA.transactional()` > Interceptor restores thread local value of `isAvailables` to false (leaked value from thread 2!) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2351: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/767/PROFIL... http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/768/PROFIL... > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2351: ---------------------------------- Summary: XTS qa tests fail to stop WildFly after excecution (was: com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit failed) > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit failed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2351: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit failed > ------------------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit failed

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2351: ----------------------------------- Summary: com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit failed Key: JBTM-2351 URL: https://issues.jboss.org/browse/JBTM-2351 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Reporter: Tom Jenkinson Assignee: Paul Robinson Fix For: 5.0.5 http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2350) CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability)

by Tomasz Krakowiak (JIRA)

[ https://issues.jboss.org/browse/JBTM-2350?page=com.atlassian.jira.plugin.... ] Tomasz Krakowiak commented on JBTM-2350: ---------------------------------------- [~mmusgrov] Thread local wouldn't work correctly if interceptor would be called recursively. > CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) > ----------------------------------------------------------------------------------------- > > Key: JBTM-2350 > URL: https://issues.jboss.org/browse/JBTM-2350 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 > Environment: Wildfly 8.1.0, Wildfly 8.2.0, linux, OS X > Reporter: Tomasz Krakowiak > Assignee: Tom Jenkinson > > The problem is with availability of `UserTransaction`. > Availability of UserTransaction is stored in `ServerVMClientUserTransaction.isAvailables` which is `ThreadLocal<Boolean>`. > `TransactionalInterceptorRequired` when intercepting call, stores thread local value of `isAvailables` in `TransactionalInterceptorBase.previousUserTransactionAvailability` field of interceptor - which is of type boolean(not thread local). > Here's a story: > We have a bean - `beanA` - with single method annotated transactional - `beanA.transactional()`. > This method is being called from two threads, where: > - Thread 1 is participating in BMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is true. > - Thread 2 is participating in CMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is false. > Both threads call `beanA.transactional()` at the same time. > What may happen: > 1. Thread 1 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to true. > 2. Thread 2 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to false. > 3. Thread 1 - exits method `beanA.transactional()` > Interceptor restores thread local value of `isAvailables` to false (leaked value from thread 2!) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2015