August 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3126) @LRA may begin a nested LRA without the presence of @NestedLRA

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3126?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-3126. ---------------------------------- > @LRA may begin a nested LRA without the presence of @NestedLRA > --------------------------------------------------------------- > > Key: JBTM-3126 > URL: https://issues.jboss.org/browse/JBTM-3126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > If a JAX-RS method is invoked and the following conditions are met: > - the invoked method is annotated with LRA.Type.REQUIRES_NEW; > - the invoked method is not annotated with @Nested; > - there is an LRA context present on the incoming request > then the implementation (of the LRA spec) will begin a nested LRA which is contrary to the specified behaviour. Note that there is an [outstanding issue regarding nested LRAs|https://github.com/eclipse/microprofile-lra/issues/117] but this issue affects the implementation of the current specification and needs fixing. > In addition there is also the situation where the outbound JAX-RS request filter may override the LRA context header (this issue can be reproduced by starting an LRA and then starting a JAX-RS request with a different "LRA context header" - the expected behaviour in this case is to run the request with the context set by the user. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3126) @LRA may begin a nested LRA without the presence of @NestedLRA

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3126?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3126: ----------------------------------- Fix Version/s: 5.9.6.Final (was: 5.next) > @LRA may begin a nested LRA without the presence of @NestedLRA > --------------------------------------------------------------- > > Key: JBTM-3126 > URL: https://issues.jboss.org/browse/JBTM-3126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > If a JAX-RS method is invoked and the following conditions are met: > - the invoked method is annotated with LRA.Type.REQUIRES_NEW; > - the invoked method is not annotated with @Nested; > - there is an LRA context present on the incoming request > then the implementation (of the LRA spec) will begin a nested LRA which is contrary to the specified behaviour. Note that there is an [outstanding issue regarding nested LRAs|https://github.com/eclipse/microprofile-lra/issues/117] but this issue affects the implementation of the current specification and needs fixing. > In addition there is also the situation where the outbound JAX-RS request filter may override the LRA context header (this issue can be reproduced by starting an LRA and then starting a JAX-RS request with a different "LRA context header" - the expected behaviour in this case is to run the request with the context set by the user. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3130: ----------------------------------- Fix Version/s: 5.9.6.Final > QA tests do not work with recent Oracle and MySQL drivers > --------------------------------------------------------- > > Key: JBTM-3130 > URL: https://issues.jboss.org/browse/JBTM-3130 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Major > Fix For: 5.9.6.Final > > > Running QA tests with recent drivers fails for MySQL and Oracle: > {code:java} > 2019-03-27 11:10:17,440 out: Failed > 2019-03-27 11:10:17,440 err: java.lang.Exception: JDBC2 driver oracle.jdbc.OracleDriver not recognised > 2019-03-27 11:10:17,440 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} > {code:java} > 2019-03-27 12:30:59,843 out: Failed > 2019-03-27 12:30:59,844 err: java.lang.Exception: JDBC2 driver com.mysql.cj.jdbc.Driver not recognised > 2019-03-27 12:30:59,844 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-3131. ---------------------------------- Resolution: Done > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > Fix For: 5.9.6.Final > > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc82...). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3131: ----------------------------------- Fix Version/s: 5.9.6.Final > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > Fix For: 5.9.6.Final > > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc82...). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3135) Update BlackTie to build with a 64-bit C compiler on Windows

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3135?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3135: ----------------------------------- Fix Version/s: 5.9.6.Final (was: 5.next) > Update BlackTie to build with a 64-bit C compiler on Windows > ------------------------------------------------------------ > > Key: JBTM-3135 > URL: https://issues.jboss.org/browse/JBTM-3135 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Build System > Reporter: Thomas Jenkinson > Assignee: Zheng Feng > Priority: Major > Fix For: 5.9.6.Final > > > JDK11 does not provide a 32-bit compiler and our existing build system uses a 32 bit compiler on Windows so it is failing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3135) Update BlackTie to build with a 64-bit C compiler on Windows

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3135?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3135: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update BlackTie to build with a 64-bit C compiler on Windows > ------------------------------------------------------------ > > Key: JBTM-3135 > URL: https://issues.jboss.org/browse/JBTM-3135 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Build System > Reporter: Thomas Jenkinson > Assignee: Zheng Feng > Priority: Major > Fix For: 5.9.6.Final > > > JDK11 does not provide a 32-bit compiler and our existing build system uses a 32 bit compiler on Windows so it is failing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-3129. ---------------------------------- > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.<clinit>(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3129: ----------------------------------- Fix Version/s: 5.9.6.Final (was: 5.next) > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.6.Final > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.<clinit>(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-3130. ---------------------------------- > QA tests do not work with recent Oracle and MySQL drivers > --------------------------------------------------------- > > Key: JBTM-3130 > URL: https://issues.jboss.org/browse/JBTM-3130 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Major > Fix For: 5.9.6.Final > > > Running QA tests with recent drivers fails for MySQL and Oracle: > {code:java} > 2019-03-27 11:10:17,440 out: Failed > 2019-03-27 11:10:17,440 err: java.lang.Exception: JDBC2 driver oracle.jdbc.OracleDriver not recognised > 2019-03-27 11:10:17,440 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} > {code:java} > 2019-03-27 12:30:59,843 out: Failed > 2019-03-27 12:30:59,844 err: java.lang.Exception: JDBC2 driver com.mysql.cj.jdbc.Driver not recognised > 2019-03-27 12:30:59,844 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 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 August 2019