August 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1067) TxSupport helper getContent() and openConnection() leaves I/O streams open

by Radesh Rao (JIRA)

Radesh Rao created JBTM-1067: -------------------------------- Summary: TxSupport helper getContent() and openConnection() leaves I/O streams open Key: JBTM-1067 URL: https://issues.jboss.org/browse/JBTM-1067 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M1 Reporter: Radesh Rao Assignee: Michael Musgrove When there are large number of transactions in progress, the following exception is thrown: Caused by: org.jboss.jbossts.star.provider.HttpResponseException: java.net.SocketException: No buffer space available (maximum connections reached?): connect at org.jboss.jbossts.star.util.TxSupport.httpRequest(TxSupport.java:261) at org.jboss.jbossts.star.util.TxSupport.startTx(TxSupport.java:179) ............................... Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBTM-1066) TxSupport helper method getTransactions() returns 1 when there are no transactions

by Radesh Rao (JIRA)

Radesh Rao created JBTM-1066: -------------------------------- Summary: TxSupport helper method getTransactions() returns 1 when there are no transactions Key: JBTM-1066 URL: https://issues.jboss.org/browse/JBTM-1066 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M1 Reporter: Radesh Rao Assignee: Michael Musgrove Priority: Minor TxSupport.getTransactions() returns a List of size 1 when there were 0 transactions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (JBTM-1022) JTS when you try to get a transaction (e.g. in after_completion) and the transaction is committed, you get a TRANSACTION_ROLLEDBACK rather than TRANSACTION_UNAVAILABLE

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1022: ----------------------------------- Summary: JTS when you try to get a transaction (e.g. in after_completion) and the transaction is committed, you get a TRANSACTION_ROLLEDBACK rather than TRANSACTION_UNAVAILABLE Key: JBTM-1022 URL: https://issues.jboss.org/browse/JBTM-1022 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Reporter: Tom Jenkinson Assignee: Tom Jenkinson As the subject says, it is incorrect to return rollback rather it should be unavailable which can be translated to a JTA javax.transaction.Status.STATUS_NO_TRANSACTION -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
4
0 / 0

[JBoss JIRA] (JBTM-1023) JTA when putResource is called on a transaction that has been committed, the call is allowed to proceed. This is against the spec.

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1023: ----------------------------------- Summary: JTA when putResource is called on a transaction that has been committed, the call is allowed to proceed. This is against the spec. Key: JBTM-1023 URL: https://issues.jboss.org/browse/JBTM-1023 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Reporter: Tom Jenkinson Assignee: Tom Jenkinson In the case where it is called (e.g. in after_completion) it should get an IllegalStateException http://jcp.org/aboutJava/communityprocess/maintenance/jsr907/907ChangeLog... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

[JBoss JIRA] (JBTM-1021) JTS ExtendedResourceRecord cannot cope with a LastResourceRecord operating in 2PC mode

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1021: ----------------------------------- Summary: JTS ExtendedResourceRecord cannot cope with a LastResourceRecord operating in 2PC mode Key: JBTM-1021 URL: https://issues.jboss.org/browse/JBTM-1021 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Reporter: Tom Jenkinson Assignee: Tom Jenkinson ERR calls prepare, which calls LRR prepare which calls XARR commit_one_phase, which cleans up the CORBA servant. ERR then calls doSave which fails as the remote servant is cleaned up but can cope with this ERR then calls commit but gets an OBJECT_NOT_EXIST which ERR lumps in with SystemException and the ServerTopLevelAction returns this as a error, it should detect this case and allow 2PC to complete normally -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (JBTM-854) We need to ship some examples showcasing transaction features

by Michael Musgrove (JIRA)

We need to ship some examples showcasing transaction features ------------------------------------------------------------- Key: JBTM-854 URL: https://issues.jboss.org/browse/JBTM-854 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Fix For: 5.0.0.M1 We still get users asking various how to questions such as how to configure recovery or how switch object stores etc. We should provide examples demonstrating as many features as possible -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-893) Build is dependent upon Sun's JDK

by Tom Jenkinson (JIRA)

Build is dependent upon Sun's JDK --------------------------------- Key: JBTM-893 URL: https://issues.jboss.org/browse/JBTM-893 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.0.M2 We have a dependency in the arjuna module on jconsole.jar which is not shipped in openjdk for instance so our pom refers to JAVA_HOME/lib/jconsole.jar. This needs reviewing, we could add a profile that only includes the dependency on a build when the file exists and in other profiles does not build the classes that require this Jar, but if the code is critical we need to think about a rewrite to not depend on the (presumably) proprietary Jar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-486) Refactor log store

by Mark Little (JIRA)

Refactor log store ------------------ Key: JBTM-486 URL: https://jira.jboss.org/jira/browse/JBTM-486 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.6 Reporter: Mark Little Assignee: Mark Little Priority: Minor Fix For: 4.7 The new log store could do with some refactoring. No interface changes or modifications of data structures. -- 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

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-844) Remove support for 1.0 XTS api

by Tom Jenkinson (JIRA)

Remove support for 1.0 XTS api ------------------------------ Key: JBTM-844 URL: https://issues.jboss.org/browse/JBTM-844 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson The community supported feature appears to be no longer required. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBTM-877) Commit the Emma patch to svn

by Paul Robinson (JIRA)

Commit the Emma patch to svn ---------------------------- Key: JBTM-877 URL: https://issues.jboss.org/browse/JBTM-877 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M1 Andrew Dinn currently has the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2012