February 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-635) tackle host and process id lock contention

by Jonathan Halliday (JIRA)

tackle host and process id lock contention ------------------------------------------ Key: JBTM-635 URL: https://jira.jboss.org/jira/browse/JBTM-635 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 The Utility methods for getting host inet addr and process id are heavily used (by Uid creation) and need to be as fast as possible. Revisit caching and synchronization to streamline these. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBTM-632) tackle ActionManager lock contention

by Jonathan Halliday (JIRA)

tackle ActionManager lock contention ------------------------------------ Key: JBTM-632 URL: https://jira.jboss.org/jira/browse/JBTM-632 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 ActionManager uses a Hashtable for _allActions. Under high load this is becomes a bottleneck. Move to ConcurrentHashMap. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBTM-613) TxControl.getStore should not recreate ObjectStore on each call

by Jonathan Halliday (JIRA)

TxControl.getStore should not recreate ObjectStore on each call --------------------------------------------------------------- Key: JBTM-613 URL: https://jira.jboss.org/jira/browse/JBTM-613 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 The TxControl.getStore method creates a new ObjectStore instance each time it's called i.e. for every tx. Since creation steps though some complex and highly synchronized inventory/naming code, it's expensive. The store instance should be created once and cached by TxControl. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBTM-530) Thrown Exceptions often loose the original cause

by Davide Cavestro (JIRA)

Thrown Exceptions often loose the original cause ------------------------------------------------ Key: JBTM-530 URL: https://jira.jboss.org/jira/browse/JBTM-530 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5.0 Reporter: Davide Cavestro In JBossTM exceptions are often catched and left behind in favor of a new dedicated Exception (or Error) contextually thrown. This lead to a steady lack of information about the origin of the final symptom. As an example, see the following code snippet (extracted from com.arjuna.ats.internal.arjuna.objectstore.JDBCStore.JDBCStore()) ... try { initialise(""); } catch (Exception e) { throw new ObjectStoreError(); } ... Here the original exception "e" is lost in favor of a new ObjectStoreError. No one will never know the cause of the thrown ObjectStoreError, nor see what's wrong without using a debugger (if ever available). Since I saw the binary distribution of JBossTM (at least version 4.5.0) is compiled for Java 1.5, I suppose you aren't denied to use the standard exception chaining mechanism introduced since Java 1.4 (namely the java.lang.Throwable.cause field) Please consider refactoring your code to chain the exception causes. It would be very useful. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBTM-498) Rename jbosscore.jar

by Mark Little (JIRA)

Rename jbosscore.jar -------------------- Key: JBTM-498 URL: https://jira.jboss.org/jira/browse/JBTM-498 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Priority: Minor When building the core engine the resultant jar is called jbosscore.jar, which is a little misleading. Maybe jbossts-core.jar? -- 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
2
0 / 0

[JBoss JIRA] Created: (JBTM-642) Complete RecordType and ObjectStoreType factories

by Mark Little (JIRA)

Complete RecordType and ObjectStoreType factories ------------------------------------------------- Key: JBTM-642 URL: https://jira.jboss.org/jira/browse/JBTM-642 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.9.0 -- 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
4
0 / 0

[JBoss JIRA] Created: (JBTM-709) Improve test coverage for txoj

by Mark Little (JIRA)

Improve test coverage for txoj ------------------------------ Key: JBTM-709 URL: https://jira.jboss.org/jira/browse/JBTM-709 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.0 -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBTM-705) update db2, sybase test server cfg

by Jonathan Halliday (JIRA)

update db2, sybase test server cfg ---------------------------------- Key: JBTM-705 URL: https://jira.jboss.org/jira/browse/JBTM-705 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.9.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.10.0 Update the qa test config to use current versions of db2 and sybase instead of obsolete ones. see also JBQA-2860 -- 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
4
0 / 0

[JBoss JIRA] Created: (JBTM-684) Byteman overriding injection bug is causing unit tests to fail

by Andrew Dinn (JIRA)

Byteman overriding injection bug is causing unit tests to fail -------------------------------------------------------------- Key: JBTM-684 URL: https://jira.jboss.org/jira/browse/JBTM-684 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn The 1.2.1 byteman jar installed in the ext directory suffers from bug https://jira.jboss.org/jira/browse/BYTEMAN-80. This is causing some of the reaper unit tests to fail. In the absence of a fix to the Byteman bug the best way to bypass this is to disable overriding injection by setting property org.jboss.byteman.skip.override.rules in the ant macro run.tests.macro. This means that overriding injection cannot be used when scripting unit tests but as it is currently inherently flaky this is no bad thing. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-670) jts/iiop as embedded in jbossAS 5.1.0 - transaction examples are not working

by jzendle (JIRA)

jts/iiop as embedded in jbossAS 5.1.0 - transaction examples are not working ---------------------------------------------------------------------------- Key: JBTM-670 URL: https://jira.jboss.org/jira/browse/JBTM-670 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1 Environment: JBoss 5.1.0GA, java 1.5.22, windows xp, Reporter: jzendle The examples described in this article on the wiki at https://www.jboss.org/community/wiki/TransactionPropagationwithJBoss Are not working. The 1st OTS test case dies on the client side with the following stack trace: [java] 1.3 [java] 1.4 [java] 1.5 [java] > Starting OTS tx with ejb2 [java] 15:13:01,837 { main} () [WARN ,arjLoggerI18N] [com.arjuna.ats.arj una.coordinator.TxControl_1] - Name of XA node not defined. Using a0d257d:be9:4b 22c3ed:0 [java] looking up OTSEjb2StatelessBean on host venus and orb name JBoss [java] jndi url: corbaloc::venus:3528/JBoss/Naming/root [java] javax.transaction.TransactionRequiredException: CORBA TRANSACTION_RE QUIRED 0 No; nested exception is: [java] org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception: javax .transaction.TransactionRequiredException: Transaction Required vmcid: 0x0 min or code: 0 completed: No [java] at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException (Util.java:203) [java] at javax.rmi.CORBA.Util.mapSystemException(Util.java:67) [java] at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.ja va:149) [java] at org.jboss.jbossts.qa.astests.ejb2._MyRemote_Stub.foo(Unknown Source) [java] at com.arjuna.ats.tools.TxTest.ejbTest(TxTest.java:264) [java] at com.arjuna.ats.tools.TxTest.doTest(TxTest.java:119) [java] at com.arjuna.ats.tools.TxTest.main(TxTest.java:82) [java] Caused by: org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception : javax.transaction.TransactionRequiredException: Transaction Required vmcid: 0 x0 minor code: 0 completed: No [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeC onstructorAccessorImpl.java:39) [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Del egatingConstructorAccessorImpl.java:27) [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:50 1) [java] at org.jacorb.orb.SystemExceptionHelper.read(Unknown Source) [java] at org.jacorb.orb.ReplyReceiver.getReply(Unknown Source) [java] at org.jacorb.orb.Delegate.invoke_internal(Unknown Source) [java] at org.jacorb.orb.Delegate.invoke(Unknown Source) [java] at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457 ) [java] at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.ja va:124) [java] ... 4 more [java] 4 [java] ots: true -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2010