October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-1418) test not all resources available

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1418?page=all ] Adrian Brock closed JBAS-1418. ------------------------------ Resolution: Out of Date > test not all resources available > -------------------------------- > > Key: JBAS-1418 > URL: http://jira.jboss.com/jira/browse/JBAS-1418 > Project: JBoss Application Server > Issue Type: Sub-task > Components: Transaction Manager > Reporter: Bill Burke > -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1406) XidFactory should never pad Xids

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1406?page=all ] Adrian Brock closed JBAS-1406. ------------------------------ Resolution: Out of Date > XidFactory should never pad Xids > -------------------------------- > > Key: JBAS-1406 > URL: http://jira.jboss.com/jira/browse/JBAS-1406 > Project: JBoss Application Server > Issue Type: Sub-task > Components: Transaction Manager > Reporter: Bill Burke > -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1402) Transaction Recovery

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ] Adrian Brock closed JBAS-1402. ------------------------------ Resolution: Out of Date Assignee: (was: Adrian Brock) This issue can be closed. The JCA issues still need resolving with some api for the a generic TM to get XAResources during recovery. There is a thread about this in the JCA forum, but I'm not sure if any JIRA issues were created beyond what is mentioned here. I'll close the ones here and re-raise the issue in the JCA forum. > Transaction Recovery > -------------------- > > Key: JBAS-1402 > URL: http://jira.jboss.com/jira/browse/JBAS-1402 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Manager > Affects Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > > Implement optional transaction recovery > The simplest mechanism is to do this is with a local database > using the last resource gambit where during its "prepare" it logs the XID in a table. > If this last resource fails to commit, recovery will not find the transaction > in the table which means it will rollback the whole transaction. > This has limitations where a different local resource is required within the transaction > but not this local database used as the recovery log. > Another implementation is a local file. Though more complicated it should give superior > performance. > But, it does not work well with the last resource gambit, e.g. you cannot tell > whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation > before the result is returned from the db. > The other work required: > 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier. > Currently the RARs need the transaction manager at deployment time. The > recovery service needs to be an external service depending upon both the > tm and the managed connection factories. > At least this will require a GUID for the XID so we can avoid duplicates between > unrecovered XIDs and any new XIDs created before recovery is complete. > 2) JBossMQ needs to implement XAResource.recover() -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-1405) Padding should be a JCA option

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1405?page=all ] Adrian Brock closed JBAS-1405. ------------------------------ Resolution: Out of Date > Padding should be a JCA option > ------------------------------ > > Key: JBAS-1405 > URL: http://jira.jboss.com/jira/browse/JBAS-1405 > Project: JBoss Application Server > Issue Type: Sub-task > Components: JCA service > Reporter: Bill Burke > > There should be a JCA switch that wraps any method of XAResource that takes an Xid and pads the Xid if needed by the JCA resource. Some XAResources like Oracle need padding, others may have problems with padding. It is stupid to have this switch on the XidFactory only. -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4870) Redelivery flags not updated in case of JBossMQ node failure

by Adrian Brock (JIRA)

Redelivery flags not updated in case of JBossMQ node failure ------------------------------------------------------------ Key: JBAS-4870 URL: http://jira.jboss.com/jira/browse/JBAS-4870 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA When the JBossMQ node fails with messages currently being delivered to the clients, the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS). The issue is that the redelivery status (in the database) is not updated until the server receives the NACK (which it won't do if it has crashed). A potential fix, is to update the status early before delivering the message to the client, see the forum thread for more detail. -- 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

18 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4826) TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour

by Michael Smith (JIRA)

TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour ------------------------------------------------------------------------------- Key: JBAS-4826 URL: http://jira.jboss.com/jira/browse/JBAS-4826 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/ -- 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

18 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1481) Reimplement portal security interface without JACC

by Julien Viet (JIRA)

Reimplement portal security interface without JACC -------------------------------------------------- Key: JBPORTAL-1481 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1481 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Julien Viet -- 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

18 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-607) SEQUENCER: incorrect ordering on concurrent sends

by Bela Ban (JIRA)

SEQUENCER: incorrect ordering on concurrent sends ------------------------------------------------- Key: JGRP-607 URL: http://jira.jboss.com/jira/browse/JGRP-607 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.1 SP5, 2.5.2, 2.6 The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes -- 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

18 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-596) Document JOIN&state transfer, for JChannel and in the Multiplexer

by Bela Ban (JIRA)

Document JOIN&state transfer, for JChannel and in the Multiplexer ----------------------------------------------------------------- Key: JGRP-596 URL: http://jira.jboss.com/jira/browse/JGRP-596 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Vladimir Blagojevic Priority: Minor Fix For: 2.6 JOIN&STATE transfer needs to get documented in doc/manual/en/modules/api.xml. We also need to add documentation for the same for the multiplexer -- 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

18 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1194) DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC

by Brian Stansberry (JIRA)

DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC --------------------------------------------------------------- Key: JBCACHE-1194 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.4.1.SP5 Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Fix For: 1.4.1.SP6 It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses. This is the cause of the behavior reported at JBAS-4726. -- 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

18 years, 9 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007