April 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3011) Uploading lra coordinator docker image should be part of the narayana release process

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-3011: ------------------------------------- Summary: Uploading lra coordinator docker image should be part of the narayana release process Key: JBTM-3011 URL: https://issues.jboss.org/browse/JBTM-3011 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Build System, LRA Affects Versions: 5.8.1.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka when narayana release is run we should consider pushing the lra docker image to the docker hub at the https://hub.docker.com/r/jbosstm/lra-coordinator/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3005) Add a quickstart showing the Tomcat and DBCP2

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3005?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3005: --------------------------------------- [~mbabacek] my two cents, I'm returning to your previous [comment|https://issues.jboss.org/browse/JBTM-3005?focusedCommentId=135582...] as you say that it's still valid (is that right?) I seems there is recovery manager not running at all. Could be there is some misconfiguration in your war file? The point is to have configured {{NarayanaJtaServletContextListener}} which configures the recovery manager (https://github.com/jbosstm/narayana/blob/master/tomcat/tomcat-jta/src/mai...). Either way I tried the test where I borrowed your {{context.xml}} and run it as it is in the {{tomcat-jta}} repo: https://github.com/ochaloup/narayana/commit/548aa471686dc40260bf7653e5178... and that way the test passes. {code} docker run -p 5432:5432 --rm -ePOSTGRES_USER=test -e POSTGRES_PASSWORD=test postgres:9.4 -c max-prepared-transactions=110 -c log-statement=all git clone https://github.com/ochaloup/narayana.git -b dbcp2 cd narayana ./build.sh clean install -Pcommunity -DskipTests -Didlj-enabled=true cd tomcat/tomcat-jta export CATALINA_HOME=... # need to be configured $CATALINA_HOME/conf/tomcat-users.xml with '<user username="test" password="test" roles="manager-script"/>' mvn clean verify -Parq-tomcat -Dit.test=BaseITCase#testRecovery {code} > Add a quickstart showing the Tomcat and DBCP2 > --------------------------------------------- > > Key: JBTM-3005 > URL: https://issues.jboss.org/browse/JBTM-3005 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.8.1.Final > > > This quickstart needs to show how to use the DBCP2 in Tomcat to support the XA transaction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3005) Add a quickstart showing the Tomcat and DBCP2

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/JBTM-3005?page=com.atlassian.jira.plugin.... ] Michal Karm Babacek commented on JBTM-3005: ------------------------------------------- [~tomjenkinson], [~zhfeng], hi guys, I did try yesterday and then again today. Some observations: * My [comment|https://issues.jboss.org/browse/JBTM-3005?focusedCommentId=135582...] is still valid. It does not work as expected. I appreciate Amos' [quickstart|https://github.com/jbosstm/quickstart/pull/221/files], but I utterly fail to understand why don't you fix/rewrite/modify [the original rudimentary recovery test|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomc...]. I did my best to port the quickstart to the aforementioned test suite, basically dropping the former code altogether. See: [This web app|https://github.com/Karm/narayana/blob/narayana-tomcat-ts-WIP/tomcat/t...]. (And its byteman rule in resources). * It does not work still, with commit causing the phase2commit flat out kill the app; I know it is not being caught in the quickstart app, but it should - [log|https://paste.fedoraproject.org/paste/q~FMpWhTbIgmqswlz1GOaw], [dbtrace|https://paste.fedoraproject.org/paste/ylEYS-SiFVxltjVALuF2KQ]. * Connections to the DB are being exhausted: Each recovery call takes a connection and keeps it: [see log|https://paste.fedoraproject.org/paste/HLD7PIAvkG7Fjvbcx-De8Q], which leads to DB trace: [see trace|https://paste.fedoraproject.org/paste/sjhrHoMVYXQxhYlsSnum7A] * You can find the whole tomcat (17MB) with the web app war file (context.xml, Tomcat DBCP2 with managed package, all in it) on this [gdrive link|https://drive.google.com/file/d/1YU_wPyw7U3PofCQeZdWxZTvUajijgCoP/vi...]. The source of the web app is [here|https://github.com/Karm/narayana/blob/narayana-tomcat-ts-WIP/tomcat/...]. Note the [TransactionalDataSourceFactory.java|https://github.com/Karm/narayana/blob...]. Also note that the Tomcat DBCP jar and Tomcat Juli jar are present in the war file and not in /lib to avoid classloader issues. * This is how I start it: {{java -javaagent:$BYTEMAN_HOME/lib/byteman.jar=script:$BTM_SCRIPT -Djava.security.egd=file:/dev/./urandom -Djava.util.logging.config.file=$CATALINA_HOME/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dignore.endorsed.dirs= -classpath $CATALINA_HOME/bin/bootstrap.jar:$CATALINA_HOME/bin/tomcat-juli.jar -Dcatalina.base=$CATALINA_HOME -Dcatalina.home=$CATALINA_HOME -Djava.io.tmpdir=$CATALINA_HOME/temp org.apache.catalina.startup.Bootstrap start}} * The how-to on starting PostgreSQL container and its parameters (e.g. max_connections=20) is here JBTM-3004. h3. Call to action I would like to kindly ask you to either clearly explain in a doc why a particular approach with Helper and enlisting is taken in the [quickstart|https://github.com/jbosstm/quickstart/pull/221/files] and not in [the original rudimentary recovery test|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomc...], or to open [the original rudimentary recovery test|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomc...] and refactor it. I naturally prefer the latter. I would like to also ask you to at least once try with PostgreSQL and not with H2. We need at least 1 semi-real-world use case example with a real driver to a real database with a real connection pool issues. The whole thing with Docker and PostgreSQL outlined on JBTM-3004 is meant to help you to give it a spin in ~2 minutes without any DBAllocator / remote DB hassle. The final goal is to have [the original rudimentary recovery test|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomc...] ported to the usage of the recovery helper and the new factory so as it works with Tomcat DBCP2, Byteman rules (and not things like [this|https://github.com/jbosstm/quickstart/pull/221/files#diff-c05f008e01...]). I am willing to do the leg work, to move stuff around, to modify the listener on the Tomcat side, to polish the TS, but I need your help with the Narayana specifics and the current quickstart just doesn't cut it. > Add a quickstart showing the Tomcat and DBCP2 > --------------------------------------------- > > Key: JBTM-3005 > URL: https://issues.jboss.org/browse/JBTM-3005 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.8.1.Final > > > This quickstart needs to show how to use the DBCP2 in Tomcat to support the XA transaction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3009) Add the Transactional datasource factory in the tomcat-jta

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3009?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #1297 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add the Transactional datasource factory in the tomcat-jta > ---------------------------------------------------------- > > Key: JBTM-3009 > URL: https://issues.jboss.org/browse/JBTM-3009 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > This factory is used to create the datasource with the common-dbcp2 and support XA and pooling, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3010: -------------------------------- Description: We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > We tend to prefer the integration code for specific application servers be kept outside of the main Narayana transaction manager repository as it tends to iterate under different release cycle also. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3010?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-3010: ------------------------------------- I suggest for now we move it to a new repo called NarayanaTomcat under jbosstm and then if necessary it could be moved elsewhere in future. > Move the tomcat-jta module out of the narayana repo > --------------------------------------------------- > > Key: JBTM-3010 > URL: https://issues.jboss.org/browse/JBTM-3010 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3010) Move the tomcat-jta module out of the narayana repo

by Amos Feng (JIRA)

Amos Feng created JBTM-3010: ------------------------------- Summary: Move the tomcat-jta module out of the narayana repo Key: JBTM-3010 URL: https://issues.jboss.org/browse/JBTM-3010 Project: JBoss Transaction Manager Issue Type: Task Reporter: Amos Feng Assignee: Amos Feng Priority: Minor Fix For: 5.next -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3009) Add the Transactional datasource factory in the tomcat-jta

by Amos Feng (JIRA)

Amos Feng created JBTM-3009: ------------------------------- Summary: Add the Transactional datasource factory in the tomcat-jta Key: JBTM-3009 URL: https://issues.jboss.org/browse/JBTM-3009 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next This factory is used to create the datasource with the common-dbcp2 and support XA and pooling, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3007) XTS endpoint registration could cause NullPointerException

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3007?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3007: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.8.1.Final Resolution: Done > XTS endpoint registration could cause NullPointerException > ---------------------------------------------------------- > > Key: JBTM-3007 > URL: https://issues.jboss.org/browse/JBTM-3007 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.8.1.Final > > > There is an issue of possible throwing {{NullPointerException}} on creating Soap fault when endpoint registration failed. > https://github.com/jbosstm/narayana/blob/master/XTS/WS-C/dev/src/com/arju... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2966?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2966: ---------------------------------- Fix Version/s: 5.next (was: 5.8.1.Final) > narayana-quickstarts-jts quickstart does not run standalone > ----------------------------------------------------------- > > Key: JBTM-2966 > URL: https://issues.jboss.org/browse/JBTM-2966 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 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 April 2018