October 2007 - jboss-jira - Jboss List Archives

[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

16 years, 11 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

16 years, 11 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

16 years, 11 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

16 years, 11 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

16 years, 11 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

16 years, 11 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1299) better handling of error when dependent class not in jar file

by Michael Neale (JIRA)

better handling of error when dependent class not in jar file ------------------------------------------------------------- Key: JBRULES-1299 URL: http://jira.jboss.com/jira/browse/JBRULES-1299 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder, drools-brms Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.1.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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4896) NPE in JBossMetaDataWrapper

by Thomas Diesler (JIRA)

NPE in JBossMetaDataWrapper --------------------------- Key: JBAS-4896 URL: http://jira.jboss.com/jira/browse/JBAS-4896 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Scott M Stark -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4899) Failed to resolve schema nsURI= location=null

by Thomas Diesler (JIRA)

Failed to resolve schema nsURI= location=null --------------------------------------------- Key: JBAS-4899 URL: http://jira.jboss.com/jira/browse/JBAS-4899 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Alexey Loubyansky -- 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

16 years, 11 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007