July 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reopened JBTM-2704: ----------------------------------- Reopening until WFLY-6890 blocker is merged. > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2704: ------------------------------------- I don't think it will be weird, the doc has to start somewhere. Regarding the other matter, we have to decide if the issue is resolved until all parts are merged. I don't think it can be considered resolved quite yet due to the outstanding WFLY requirement > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2704: --------------------------------------- I mean should I move to open so that it could be resolved once WFLY issue is resolved? But there isn't any documentation on this at the moment. Wouldn't the docs section look weird only with one note? I've also linked a docs JIRA as a follow up. > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2678: ------------------------------------- [~paul.robinson] - can you describe the failure window. It sounds worrying. [~gytis] - seems a candidate for deprecation but awaiting further feedback from Paul > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2704: ------------------------------------- No, just link to the docs is fine. But you should work on adding the docs for this before moving onto something else. And when I say, the "this" - I mean the particular issue we are discussing now. You just need to add the chapter for compensations into the docs, put "This is not complete" reference the docs issue JBTM-2680 and then add the note specific to this thing. Next time I will mention to add the docs PR before marking as ready to merge > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2614: ----------------------------------------------- Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1360648|https://bugzilla.redhat.com/show_bug.cgi?id=1360648] from NEW to ASSIGNED > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2678: --------------------------------------- Maybe we should remove @TxLogged annotation from the API then? > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-987) Document Compensations API

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris closed JBTM-987. -------------------------------- Fix Version/s: (was: 5.later) Assignee: (was: Paul Robinson) Resolution: Duplicate Issue > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Documentation > Reporter: Tom Jenkinson > Priority: Optional > Labels: TXFramework > > Should cover all existing features and provide a skeleton for the final document. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2680) Document compensations API

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2680?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2680: ---------------------------------- Component/s: Documentation > Document compensations API > -------------------------- > > Key: JBTM-2680 > URL: https://issues.jboss.org/browse/JBTM-2680 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > There is no documentation for compensations API in our docs. Most of the things are covered in the quickstarts and blog, but adding something to the docs would be good too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2704: --------------------------------------- So should I move it back to open even though the PR was merged? > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 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 July 2016