October 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-284) Make sure distributed transaction example within JBossAS is clearly illustrated

by Mark Little (JIRA)

Make sure distributed transaction example within JBossAS is clearly illustrated ------------------------------------------------------------------------------- Key: JBTM-284 URL: http://jira.jboss.com/jira/browse/JBTM-284 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 MR1 Will need to remember to use the JBossTS rmi-iiop tool (rmic) because OTS 1.1 should only propagate transactions to TransactionalObjects and no Java entites will ever qualify. -- 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

13 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-411) Other implementations for getpid

by Mark Little (JIRA)

Other implementations for getpid -------------------------------- Key: JBTM-411 URL: https://jira.jboss.org/jira/browse/JBTM-411 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: future VirtualMachine (JDK 6) JBoss Web ... If native is loaded then org.apache.tomcat.jni.Stdlib.getpid() or org.apache.tomcat.jni.Stdlib.getppid() for a parent process of jvm See the Stdlib.java for docs -- 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

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-573) Manually prune entries from logs

by Mark Little (JIRA)

Manually prune entries from logs -------------------------------- Key: JBTM-573 URL: https://jira.jboss.org/jira/browse/JBTM-573 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 Provide a command-line tool to allow entries in logs to be removed. Needs further thought. -- 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

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-518) Provide explicit ../lib/arjuna_wst1_0.jar, so WS-BusinessActivity Framework works "out of the box" with JBoss 5.00GA

by BEN COTTON (JIRA)

Provide explicit ../lib/arjuna_wst1_0.jar, so WS-BusinessActivity Framework works "out of the box" with JBoss 5.00GA --------------------------------------------------------------------------------------------------------------------- Key: JBTM-518 URL: https://jira.jboss.org/jira/browse/JBTM-518 Project: JBoss Transaction Manager Issue Type: Support Patch Security Level: Public (Everyone can see) Environment: software platform Reporter: BEN COTTON The current JBoss WS-BusinessActivity Framework 0.2.1 code (both demos and txbridge) currently imports the com.arjuna.wst.* and com.arjuna.mw.wst.* class libraries. These libraries are WST 1.0 compliant and will not work "out of the box" with JBoss 5.00GA (which requires WST 1.1 compliance). This patch provides and explicit https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/bencotton/BAFRAME... so that the BA Framework (both demos and txbridge) will work "out of the box" with JBoss 5.00GA. Another JIRA will document patching the org.jboss.ba.demo.* and org.jboss.txbridge.* Java source code to explicitly import WST 1.1 classes. -- 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

13 years, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBTM-599) Synchronization problem in CacheStore

by Andrew Dinn (JIRA)

Synchronization problem in CacheStore ------------------------------------- Key: JBTM-599 URL: https://jira.jboss.org/jira/browse/JBTM-599 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Dinn This bug manifests occasionally when running the CachedTest. The AsyncStore thread suspends inside its run method on a (120 sec) timed wait because the cache is not full. When I managed to catch this case in the debugger I found that there were many writer threads (~30) suspended inside addWork in an untimed wait on the overflow lock. So, these writing threads make no progress for 120 seconds. The AsyncStore thread does notify the object on which the writers are waiting but there is clearly a window where the writers can go to sleep while the cache is full and not get notified when the AsyncStore thread has emptied 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

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-437) Make sure JBossTS configuration in EAP has recovery set up by default

by Mark Little (JIRA)

Make sure JBossTS configuration in EAP has recovery set up by default --------------------------------------------------------------------- Key: JBTM-437 URL: https://jira.jboss.org/jira/browse/JBTM-437 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-578) Put back branch equivalent code for ArjunaCore transactions

by Mark Little (JIRA)

Put back branch equivalent code for ArjunaCore transactions ----------------------------------------------------------- Key: JBTM-578 URL: https://jira.jboss.org/jira/browse/JBTM-578 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Fix For: future Needed for interop. -- 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, 1 month

3
7
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, 1 month

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, 1 month

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, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2009