May 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2413) narayana.sh fails on OS X

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2413?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2413: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/849 > narayana.sh fails on OS X > ------------------------- > > Key: JBTM-2413 > URL: https://issues.jboss.org/browse/JBTM-2413 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.1 > > > The build fails with: > ./scripts/hudson/narayana.sh: line 640: free: command not found -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2413) narayana.sh fails on OS X

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2413: -------------------------------------- Summary: narayana.sh fails on OS X Key: JBTM-2413 URL: https://issues.jboss.org/browse/JBTM-2413 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.1.1 The build fails with: ./scripts/hudson/narayana.sh: line 640: free: command not found -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2412) XA transactions should be recoverable by any JBoss instance

by Tom Ross (JIRA)

Tom Ross created JBTM-2412: ------------------------------ Summary: XA transactions should be recoverable by any JBoss instance Key: JBTM-2412 URL: https://issues.jboss.org/browse/JBTM-2412 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Recovery Affects Versions: 5.1.1 Environment: JBoss EAP Reporter: Tom Ross Assignee: Tom Jenkinson At the moment when JBoss server crashes, the JBoss instance has to be restarted in order for the XA transactions to be recovered. It should be possible that after the crash any JBoss instance still running should be able to recover those transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2400: ----------------------------------- I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.... ] Mark Little edited comment on JBTM-2400 at 5/15/15 9:45 AM: ------------------------------------------------------------ I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info/trace. was (Author: marklittle): I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-2400. ----------------------------- Resolution: Done > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2393: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana.io/pull/3, https://github.com/jbosstm/narayana/pull/848, https://github.com/jbosstm/documentation/pull/31 (was: https://github.com/jbosstm/narayana.io/pull/3) All pull requests are ready for review. For now I have added the same analytics id everywhere. If this will not work, we can improve it. > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-... > <transformerParameters> > <html.googleAnalyticsId>UA-XXXXXXX-X</html.googleAnalyticsId> > <html.googleTagManagerId>GTM-NJWS5L</html.googleTagManagerId> > <html.googleTagManagerChannel>MyProject</html.googleTagManagerChannel> > </transformerParameters> > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2411: ----------------------------------- Summary: Investigate jgroups-raft and whether this can help with cloud object store Key: JBTM-2411 URL: https://issues.jboss.org/browse/JBTM-2411 Project: JBoss Transaction Manager Issue Type: Task Components: Recovery, Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.later http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2410) Internationalize warning/info messages

by Mark Little (JIRA)

Mark Little created JBTM-2410: --------------------------------- Summary: Internationalize warning/info messages Key: JBTM-2410 URL: https://issues.jboss.org/browse/JBTM-2410 Project: JBoss Transaction Manager Issue Type: Task Components: STM Affects Versions: 5.1.1 Reporter: Mark Little Assignee: Mark Little Some of them aren't at the moment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2400: ----------------------------------- A comment for completeness only: trace is enabled then the user will see something from BasicAction when End fails to commit the transaction. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2015