February 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2091) Narayana 5.0.0.Final Release Notes page broken

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2091?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2091. --------------------------------- Resolution: Done Corrected current link and added extra step to NRP: https://community.jboss.org/wiki/NarayanaReleaseProcess > Narayana 5.0.0.Final Release Notes page broken > ---------------------------------------------- > > Key: JBTM-2091 > URL: https://issues.jboss.org/browse/JBTM-2091 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Hladky > Assignee: Tom Jenkinson > > Hi, we received following ticket: https://engineering.redhat.com/rt/Ticket/Display.html?id=275511 > Original text: > I was attempting to look at the release notes for Narayana 5.0.0.Final and I am getting a Page Not Found error. http://docs.jboss.org/jbosstm/5.0.0.Final/guides/release_notes/index.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2091) Narayana 5.0.0.Final Release Notes page broken

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2091?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2091: ------------------------------------- Sorry about that, we are using Jira to provide the release notes now. Here is the one for 5.Final: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310200&versi... > Narayana 5.0.0.Final Release Notes page broken > ---------------------------------------------- > > Key: JBTM-2091 > URL: https://issues.jboss.org/browse/JBTM-2091 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Hladky > Assignee: Tom Jenkinson > > Hi, we received following ticket: https://engineering.redhat.com/rt/Ticket/Display.html?id=275511 > Original text: > I was attempting to look at the release notes for Narayana 5.0.0.Final and I am getting a Page Not Found error. http://docs.jboss.org/jbosstm/5.0.0.Final/guides/release_notes/index.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2092) Increase the orphan detection safety interval

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2092?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2092: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/595, https://github.com/jbosstm/narayana/pull/596 > Increase the orphan detection safety interval > --------------------------------------------- > > Key: JBTM-2092 > URL: https://issues.jboss.org/browse/JBTM-2092 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 5.0.0.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.17, 5.1.0.Alpha1 > > > It currently matches the recovery backoff interval, which means that an Xid can be spotted in phase 1 and rolled back in phase 2 without being checked with the recovery manager again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2092) Increase the orphan detection safety interval

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2092: ----------------------------------- Summary: Increase the orphan detection safety interval Key: JBTM-2092 URL: https://issues.jboss.org/browse/JBTM-2092 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.0.Final Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.17, 5.1.0.Alpha1 It currently matches the recovery backoff interval, which means that an Xid can be spotted in phase 1 and rolled back in phase 2 without being checked with the recovery manager again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2091) Narayana 5.0.0.Final Release Notes page broken

by David Hladky (JIRA)

David Hladky created JBTM-2091: ---------------------------------- Summary: Narayana 5.0.0.Final Release Notes page broken Key: JBTM-2091 URL: https://issues.jboss.org/browse/JBTM-2091 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Hladky Assignee: Tom Jenkinson Hi, we received following ticket: https://engineering.redhat.com/rt/Ticket/Display.html?id=275511 Original text: I was attempting to look at the release notes for Narayana 5.0.0.Final and I am getting a Page Not Found error. http://docs.jboss.org/jbosstm/5.0.0.Final/guides/release_notes/index.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE)

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2090: ----------------------------------- Summary: BlackTie process terminating with default action of signal 13 (SIGPIPE) Key: JBTM-2090 URL: https://issues.jboss.org/browse/JBTM-2090 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.1.0.Alpha1 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACK... {code} ==11776== Process terminating with default action of signal 13 (SIGPIPE) ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) ==11776== by 0x49B74A: CppUnit::TestCaller<TestTPConnect>::tearDown() (TestCaller.h:182) ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) ==11776== by 0x4F6F83: main (TestRunner.cxx:27) --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2078) BlackTie doesn't build on Fedora 20 64bit

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2078?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2078: --------------------------------- It looks like similar with JBTM-1787. I will check g++ version in fc20 > BlackTie doesn't build on Fedora 20 64bit > ----------------------------------------- > > Key: JBTM-2078 > URL: https://issues.jboss.org/browse/JBTM-2078 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.1.0.Alpha1 > > > generate-exe: > libnames not specified or empty. > libnames not specified or empty. > [cc] 1 total files to be compiled. > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx: In function ‘int main(int, char**)’: > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx:31:39: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings] > [cc] putenv("BLACKTIE_CONFIGURATION=linux"); > [cc] ^ > [cc] Starting link > [cc] /lib64/libaprutil-1.so.0: undefined reference to `apr_pool_pre_cleanup_register' > [cc] collect2: error: ld returned 1 exit status -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2050) Add a quickstart showing the JTA 1.2 annotations in use inside WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2050?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2050: ------------------------------------- Hi Gytis, I added some comments to your pull request. Tom > Add a quickstart showing the JTA 1.2 annotations in use inside WildFly > ---------------------------------------------------------------------- > > Key: JBTM-2050 > URL: https://issues.jboss.org/browse/JBTM-2050 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.1.0.Alpha1 > > > For example, it can use @Transactional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2054) Investigate what JNDI names should be used in ArjunaJTA/cdi classes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2054?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2054: ------------------------------------- These values should be the ones set in "JTAEnvironmentBean" > Investigate what JNDI names should be used in ArjunaJTA/cdi classes > ------------------------------------------------------------------- > > Key: JBTM-2054 > URL: https://issues.jboss.org/browse/JBTM-2054 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 6.0.0.Final > > > Currently ArjunaJTA/cdi uses java:/jboss namespace for JNDI lookup. However, in standalone mode such names do not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2054) Investigate what JNDI names should be used in ArjunaJTA/cdi classes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2054?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2054: -------------------------------- Fix Version/s: 5.1.0.Alpha1 (was: 6.0.0.Final) > Investigate what JNDI names should be used in ArjunaJTA/cdi classes > ------------------------------------------------------------------- > > Key: JBTM-2054 > URL: https://issues.jboss.org/browse/JBTM-2054 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.1.0.Alpha1 > > > Currently ArjunaJTA/cdi uses java:/jboss namespace for JNDI lookup. However, in standalone mode such names do not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 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 February 2014