September 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-669) Review OSGi JTA Implementation

by Thomas Diesler (JIRA)

Review OSGi JTA Implementation ------------------------------ Key: JBTM-669 URL: https://jira.jboss.org/jira/browse/JBTM-669 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Reporter: Thomas Diesler Please review and provide feedback on the inital OSGi JTA implementation jboss-osgi-jta-1.0.0 http://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi/projects/bundl... JBoss OSGi Dev http://www.jboss.org/index.html?module=bb&op=viewforum&f=256 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-616) Improve Integration of Authentication support on AppServerJDBCXARecovery plugin

by Brad Maxwell (JIRA)

Improve Integration of Authentication support on AppServerJDBCXARecovery plugin ------------------------------------------------------------------------------- Key: JBTM-616 URL: https://jira.jboss.org/jira/browse/JBTM-616 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.CP05 Reporter: Brad Maxwell JBTM-432 - Authentication support on AppServerJDBCXARecovery plugin This allows the jmx username/password to be specified in the jbossts-properties.xml and allows the AppServerJDBCXARecovery plugin to function when the invokers are secured. Customers do not like having username / passwords in clear text in the jbossts-properties.xml and do not understand why the username / password has to be set in the first place. Providing encryption support for the user/pass in the jbossts-properties.xml or better yet integrating it better so that the user/pass is not required when using secure invokers would be nice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-591) Default configuration for com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable should be DISABLED.

by Vicky Kak (JIRA)

Default configuration for com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable should be DISABLED. -------------------------------------------------------------------------------------------------------------- Key: JBTM-591 URL: https://jira.jboss.org/jira/browse/JBTM-591 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Vicky Kak Assignee: Vicky Kak In typical JEE environment the RecoveryManager and TransactionManager are usually running in the same JVM, it is common use case. And for such usecases the interaction between the TM and RM should not use sockets and thus the listeners on the TransactionStatusManager are not required. Disabling the com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable property as default setting would make sense. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-539) the Recovery ORB is bound to 0.0.0.0

by Frank Schwarz (JIRA)

the Recovery ORB is bound to 0.0.0.0 ------------------------------------ Key: JBTM-539 URL: https://jira.jboss.org/jira/browse/JBTM-539 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, Configuration, JTS, Recovery Environment: JBoss AS 5.0.0.GA Reporter: Frank Schwarz from jbossjts-properties.xml:  <property name="com.arjuna.ats.jts.recoveryManagerAddress" value=""/> This is not quite right. I can see a binding to 0.0.0.0 instead of the ip-address the server was started with (run.cmd -b <...>) When I change this line to <property name="com.arjuna.ats.jts.recoveryManagerAddress" value="${jboss.bind.address}"/> the Recovery ORB is bound instead to 127.0.0.1 I have to be explicit on the ip-address to get the right binding. Please use the default ip-address as stated with the "-b option" to bind the Recovery ORB if nothing else is specified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBTM-521) Fatal error when obtaining POA

by Jason T. Greene (JIRA)

Fatal error when obtaining POA ------------------------------ Key: JBTM-521 URL: https://jira.jboss.org/jira/browse/JBTM-521 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jason T. Greene When updating to 4.6.0.GA, org.jboss.test.jca.test.TxInflowUnitTestCase in the AS testsuite triggers a fatal error obtaining a POA. com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:537) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.<init>(ServerControl.java:230) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:51) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(TransactionImple.java:57) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.importTransaction(TransactionImporterImple.java:90) at com.arjuna.ats.internal.jbossatx.jta.jca.XATerminator.registerWork(XATerminator.java:106) at org.jboss.resource.work.JBossWorkManager.importWork(JBossWorkManager.java:167) at org.jboss.resource.work.JBossWorkManager.doWork(JBossWorkManager.java:103) at org.jboss.test.jca.inflow.TestResourceAdapterTxInflow.basicTest(TestResourceAdapterTxInflow.java:81) at org.jboss.test.jca.inflow.TestResourceAdapterTxInflow.run(TestResourceAdapterTxInflow.java:55) at org.jboss.test.jca.inflow.TestResourceAdapter.testTxInflow(TestResourceAdapter.java:77) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:263) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-439) TMENDRSCAN could be earlier

by Mark Little (JIRA)

TMENDRSCAN could be earlier --------------------------- Key: JBTM-439 URL: https://jira.jboss.org/jira/browse/JBTM-439 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-421) BasicLockStore as ObjectStore

by Mark Little (JIRA)

BasicLockStore as ObjectStore ----------------------------- Key: JBTM-421 URL: https://jira.jboss.org/jira/browse/JBTM-421 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Priority: Minor BasicLockStore looks like an ObjectStore. There was an implementation that was an ObjectStore. Find it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-356) Resurrect BasicAction criticalStart and criticalEnd

by Mark Little (JIRA)

Resurrect BasicAction criticalStart and criticalEnd --------------------------------------------------- Key: JBTM-356 URL: http://jira.jboss.com/jira/browse/JBTM-356 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.3.0.GA Reporter: Mark Little Assigned To: Mark Little These used to do something useful (they still do in C++). They are still called, but don't do anything. They should. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-286) Make local JTA recovery expiration work in the same way as JTS

by Mark Little (JIRA)

Make local JTA recovery expiration work in the same way as JTS -------------------------------------------------------------- Key: JBTM-286 URL: http://jira.jboss.com/jira/browse/JBTM-286 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-310) Compare thread-locking approach from OTSArjuna with current JBossTS code

by Mark Little (JIRA)

Compare thread-locking approach from OTSArjuna with current JBossTS code ------------------------------------------------------------------------ Key: JBTM-310 URL: http://jira.jboss.com/jira/browse/JBTM-310 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Transaction Core Reporter: Mark Little Assigned To: Mark Little Worth checking if there are any further changes that could affect us. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2010