December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-167) Update installation instructions to fix getRollbackOnly functionality

by Kevin Conner (JIRA)

Update installation instructions to fix getRollbackOnly functionality --------------------------------------------------------------------- Key: JBTM-167 URL: http://jira.jboss.com/jira/browse/JBTM-167 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.2 Reporter: Kevin Conner Assigned To: Kevin Conner Update installation instructions and jars to provide a patch for JBAS-3847. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-140) The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout.

by Kevin Conner (JIRA)

The JTS UserTransaction raises the wrong exception if the transaction has been terminated through the transaction reaper as a consequence of a timeout. ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-140 URL: http://jira.jboss.com/jira/browse/JBTM-140 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.2 -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBTM-13) Produce Arjuna Transaction Service integration plan.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-13?page=all ] Mark Little closed JBTM-13. --------------------------- > Produce Arjuna Transaction Service integration plan. > ---------------------------------------------------- > > Key: JBTM-13 > URL: http://jira.jboss.com/jira/browse/JBTM-13 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Mark Little > Assigned To: Mark Little > Attachments: ATS+JBoss.rtf > > Time Spent: 2 days > Remaining Estimate: 0 minutes > -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-98) Adding padding support to Xid for Oracle OCI driver

by Mark Little (JIRA)

Adding padding support to Xid for Oracle OCI driver --------------------------------------------------- Key: JBTM-98 URL: http://jira.jboss.com/jira/browse/JBTM-98 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 Plus add it to qualification drivers for DTF. -- 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

17 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-3847) Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back

by Kevin Conner (JIRA)

Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back -------------------------------------------------------------------------------------------------- Key: JBAS-3847 URL: http://jira.jboss.com/jira/browse/JBAS-3847 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Kevin Conner The current implementation of EJBContext.getRollbackOnly will return true if the current transaction context has status Status.STATUS_MARKED_ROLLBACK. If using JBossTS, a transaction timeout results in the transaction being rolled back asynchronously (not just marked for rollback). Code using the getRollbackOnly method as an indicator of the current transaction status will not function as expected. The transaction status undergoes the following transition Status.STATUS_ACTIVE -> Status.STATUS_ROLLING_BACK -> Status.STATUS_ROLLEDBACK. Extending getRollbackOnly to check for Status.STATUS_MARKED_ROLLBACK, Status.STATUS_ROLLING_BACK and Status.STATUS_ROLLEDBACK will allow this code to function as expected. This was opened via salesforce https://na1.salesforce.com/50030000002X6dw. -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3938) CLONE -Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back

by Dimitris Andreadis (JIRA)

CLONE -Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back --------------------------------------------------------------------------------------------------------- Key: JBAS-3938 URL: http://jira.jboss.com/jira/browse/JBAS-3938 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Kevin Conner Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 The current implementation of EJBContext.getRollbackOnly will return true if the current transaction context has status Status.STATUS_MARKED_ROLLBACK. If using JBossTS, a transaction timeout results in the transaction being rolled back asynchronously (not just marked for rollback). Code using the getRollbackOnly method as an indicator of the current transaction status will not function as expected. The transaction status undergoes the following transition Status.STATUS_ACTIVE -> Status.STATUS_ROLLING_BACK -> Status.STATUS_ROLLEDBACK. Extending getRollbackOnly to check for Status.STATUS_MARKED_ROLLBACK, Status.STATUS_ROLLING_BACK and Status.STATUS_ROLLEDBACK will allow this code to function as expected. -- 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

17 years, 9 months

1
3
0 / 0

[JBoss JIRA] Closed: (JBESB-29) Create administration guide

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-29?page=all ] Mark Little closed JBESB-29. ---------------------------- Resolution: Done > Create administration guide > --------------------------- > > Key: JBESB-29 > URL: http://jira.jboss.com/jira/browse/JBESB-29 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core, Documentation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.0 > > Time Spent: 20 minutes > Remaining Estimate: 0 minutes > -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-29) Create administration guide

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-29?page=all ] Mark Little updated JBESB-29: ----------------------------- Fix Version/s: 4.0 (was: 5.0) > Create administration guide > --------------------------- > > Key: JBESB-29 > URL: http://jira.jboss.com/jira/browse/JBESB-29 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core, Documentation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.0 > > -- 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

17 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-373) Port of JGRP-365 to CVS head (2.5)

by Bela Ban (JIRA)

Port of JGRP-365 to CVS head (2.5) ---------------------------------- Key: JGRP-373 URL: http://jira.jboss.com/jira/browse/JGRP-373 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.5 -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Assigned: (JGRP-176) Asynchronous dispatching of requests in RequestCorrelator

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-176?page=all ] Bela Ban reassigned JGRP-176: ----------------------------- Assignee: Vladimir Blagojevic (was: Bela Ban) Needed for 'breaking the locks on state transfer' > Asynchronous dispatching of requests in RequestCorrelator > --------------------------------------------------------- > > Key: JGRP-176 > URL: http://jira.jboss.com/jira/browse/JGRP-176 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8, 2.2.9, 2.2.9.1 > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Fix For: 2.5 > > > In RequestCorrelator.handleRequest(), we call handle(Message) on the registered RequestHandler (RpcDispatcher in the case of JBossCache). > Because of http://jira.jboss.com/jira/browse/JBCACHE-326, we need to provide an asynchronous way of calling handle(Message), which doesn't need to wait for the call to return, but is notified later when the response is ready (or not at all if the call is asynchronous). > This could be implemented using a subinterface of RequestHandler (e.g. AsyncRequestHandler), and a *future*. -- 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

17 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006