May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1707) JBTM-377 not able to download patch 4.4.CR2, 4.2.3.CP09 for jboss version 4.2.3.GA

by Sube Singh (JIRA)

Sube Singh created JBTM-1707: -------------------------------- Summary: JBTM-377 not able to download patch 4.4.CR2, 4.2.3.CP09 for jboss version 4.2.3.GA Key: JBTM-1707 URL: https://issues.jboss.org/browse/JBTM-1707 Project: JBoss Transaction Manager Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Recovery Environment: JBoss 4.2.3.GA Reporter: Sube Singh Assignee: Tom Jenkinson We are facing "WARN [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.gandiva.inventory...." issue. To fix it we got to know about patch "4.4.CR2, 4.2.3.CP09" from url "https://issues.jboss.org/browse/JBTM-377" but did not find web-link to download the same patch. Please also suggest do we have to apply this patch or go for higher version of jboss that has fix of above discussed problem. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1696) arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1696?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1696. --------------------------------- Fix Version/s: 4.17.5 5.0.0.M3 Resolution: Done > arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything" > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1696 > URL: https://issues.jboss.org/browse/JBTM-1696 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Weinan Li > Priority: Minor > Fix For: 4.17.5, 5.0.0.M3 > > > arjunacore: artifactId is "arjunacore-all" but the name of the project is "ArjunaCore everything". it doesn't seem like a big issue, but when you are trying to track down a build failure, and you see the project name, it doesn't help you figure out where the failing code is. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1682) Create Quickstarts for using Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1682?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1682: -------------------------------- Priority: Minor (was: Critical) > Create Quickstarts for using Compensations API > ---------------------------------------------- > > Key: JBTM-1682 > URL: https://issues.jboss.org/browse/JBTM-1682 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Should cover the 3 examples covered in my JUDConn presentation and the associated blog post. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1682) Create Quickstarts for using Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1682?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1682: -------------------------------- Fix Version/s: 5.0.0.M3 (was: 5.0.0.M4) > Create Quickstarts for using Compensations API > ---------------------------------------------- > > Key: JBTM-1682 > URL: https://issues.jboss.org/browse/JBTM-1682 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Should cover the 3 examples covered in my JUDConn presentation and the associated blog post. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1706) Remove RTS subsystem's dependency on default Undertow server and host

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1706: ------------------------------------- Summary: Remove RTS subsystem's dependency on default Undertow server and host Key: JBTM-1706 URL: https://issues.jboss.org/browse/JBTM-1706 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Application Server Integration Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.0.M4 Make sure that RTS subsystem chooses correct Undertow server and host instead of requiring default Undertow configuration. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1705) Remove XTS CDI Extension

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1705: ----------------------------------- Summary: Remove XTS CDI Extension Key: JBTM-1705 URL: https://issues.jboss.org/browse/JBTM-1705 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Priority: Critical WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem. There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial version of Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Initial version of Compensations API > ------------------------------------ > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 2 weeks > Time Spent: 1 week, 1 day, 6 hours > Remaining Estimate: 0 minutes > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. > Tasks: > # Investigate existing WS-BA APIs > ## Try code examples if possible > # Produce an initial list of features that should be covered by the API > # Create a simple implementation backed by WS-BA. > Implementation work, to complete this issue: > # Manage lifecycle of transaction via the @Compensatable annotation > # Allow Compensation and Completion handlers to be registered via annotations > # Mechanism for allowing application to mark the transaction as CompensateOnly > # Merge into Narayana code base > # OOTB support in WildFly -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon()

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1650: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon() > ----------------------------------------------------------------- > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1684) TestTPConnect::tearDown tpdiscon() abort as the session has been deleted

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1684?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1684: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TestTPConnect::tearDown tpdiscon() abort as the session has been deleted > ------------------------------------------------------------------------ > > Key: JBTM-1684 > URL: https://issues.jboss.org/browse/JBTM-1684 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32-el5/948/ -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1700) Server startup is delayed if recovery starts before all resource plugins register

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1700?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1700: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=966296 > Server startup is delayed if recovery starts before all resource plugins register > --------------------------------------------------------------------------------- > > Key: JBTM-1700 > URL: https://issues.jboss.org/browse/JBTM-1700 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Livingston > Assignee: Tom Jenkinson > > If the startup of JBoss is sufficiently slow, it is possible for a recovery run to already be in progress when a resource plugin is added. When this occurs, the startup will block until the recovery run has finished. > It would be much better if starting a recovery run did not block AS startup. > An example of this occurring on EAP 5 is: > "main" prio=10 tid=0x00002aac680cc000 nid=0x5e67 waiting for monitor entry [0x00000000412cb000] > java.lang.Thread.State: BLOCKED (on object monitor) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.addXAResourceRecoveryHelper(XARecoveryModule.java:85) > - waiting to lock <0x00002aab3e8b9d68> (a java.util.LinkedList) > at com.arjuna.ats.jbossatx.jta.TransactionManagerService.addXAResourceRecovery(TransactionManagerService.java:695) > at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.startService(ManagedConnectionFactoryDeployment.java:500) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) > at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:124) > at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) > at org.jboss.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:283) > at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189) > at $Proxy43.start(Unknown Source) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) > at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) > ... > "Thread-21" prio=10 tid=0x00002aacdd1f7000 nid=0x5ee3 runnable [0x000000004416a000] > java.lang.Thread.State: RUNNABLE > ... > at org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:294) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:773) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:712) > - locked <0x00002aab3e8b9d68> (a java.util.LinkedList) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:201) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:799) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412) -- 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, 12 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 May 2013