March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4088) Background validation seconds

by Adrian Brock (JIRA)

Background validation seconds ----------------------------- Key: JBAS-4088 URL: http://jira.jboss.com/jira/browse/JBAS-4088 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Adrian Brock Assigned To: Weston Price Support background-validation-seconds and deprecate background-validation-minutes Unlike the idle timeout, the background validation needs to be more finegrained. -- 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

3
9
0 / 0

[JBoss JIRA] Created: (JBFORUMS-151) Change Look&Feel

by Ryszard Kozmik (JIRA)

Change Look&Feel ---------------- Key: JBFORUMS-151 URL: http://jira.jboss.com/jira/browse/JBFORUMS-151 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 Beta This task is a placeholder for subtasks. Tasks placed here will be connected with refactoring off all views to use new graphics design. Also there will be a couple of new views tasks needed for new graphics which will also be placed under this task. -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-127) Eliminate all GPL dependencies from the new forums

by Sohil Shah (JIRA)

Eliminate all GPL dependencies from the new forums -------------------------------------------------- Key: JBFORUMS-127 URL: http://jira.jboss.com/jira/browse/JBFORUMS-127 Project: JBoss Forums Issue Type: Task Affects Versions: 1.0.0 Alpha Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 1.1.0 Alpha Need to identify any GPL dependencies and convert to LGPL -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-129) Modify the schema being used from PHPBB

by Sohil Shah (JIRA)

Modify the schema being used from PHPBB --------------------------------------- Key: JBFORUMS-129 URL: http://jira.jboss.com/jira/browse/JBFORUMS-129 Project: JBoss Forums Issue Type: Sub-task Reporter: Sohil Shah Assigned To: Sohil Shah -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-890) Custom flags per node, incorporate and consolidate some domain-specific flags

by Elias Ross (JIRA)

Custom flags per node, incorporate and consolidate some domain-specific flags ----------------------------------------------------------------------------- Key: JBCACHE-890 URL: http://jira.jboss.com/jira/browse/JBCACHE-890 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani I believe that with java.util.EnumSet and a list of enumerations, that some of the specific flags we track on a node could be consolidated. Immediately what comes to mind are the CacheLoader flags "childrenLoaded" and "dataLoaded" Further, I believe that some additional functionality could be incorporated. For instance: 1. For certain internal nodes, they could be marked as "internal" or "local" and not replicated. Or possibly hidden from access entirely. 2. Some nodes might be marked as "read-only" or "non-persisted" or "non-evictable" 3. Some nodes might have special sorted ordering. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3981) Statment caching in update query which return value

by erahamim (JIRA)

Statment caching in update query which return value ---------------------------------------------------- Key: JBAS-3981 URL: http://jira.jboss.com/jira/browse/JBAS-3981 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: jboss 4.0.5 on windows xp / linux with database oracle 10.0.2 Reporter: erahamim Priority: Minor When I set statements cache in oracle-xa-ds.xml: <prepared-statement-cache-size>100</prepared-statement-cache-size> For the following statement: BEGIN UPDATE table SET A=? WHERE ID=? AND TIME=? RETURNING TIME INTO ?; END con = DataSourceManager.getConnection(); statement = con.prepareCall( 'The above query'); statement.setInt(1,1); statement.setTimestamp(2, myTime); statement.registerOutParameter(3, Types.TIMESTAMP); statement.executeUpdate(); final Timestamp ts = statement.getTimestamp(lastIndex); In this scenario, I'm always getting back the time result even if the update didn't match any row in database. When I drop the statement cache I get the result only if there was a row that was updated by this statement. I can't use the return value from executeUpdate() since it always return 1. -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3511) JMS ASF integration and JMS Session Pools need resource management improvements

by Weston Price (JIRA)

JMS ASF integration and JMS Session Pools need resource management improvements ------------------------------------------------------------------------------- Key: JBAS-3511 URL: http://jira.jboss.com/jira/browse/JBAS-3511 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.3 SP1 Reporter: Weston Price Assigned To: Weston Price Priority: Minor A client has requested that the JMS applications server integration facilities for resource management and JMS session pooling be improved primarily in two areas: 1) The ability to not create all JMS sessions on container startup. 2) The ability to recycle/release JMS sessions based on a configurable timeout. Both these features would need to be added to the existing JMSContainerInvoker as well as carried forward to the JBossJCA adapter prior to production release. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3943) JMS/JCA adapter should provide for security domain authentication in addition to JMS client credential

by Weston Price (JIRA)

JMS/JCA adapter should provide for security domain authentication in addition to JMS client credential ------------------------------------------------------------------------------------------------------ Key: JBAS-3943 URL: http://jira.jboss.com/jira/browse/JBAS-3943 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Current the JCA/JMS adapter does not allow for security domain based authentication. There is nothing in the JCA spec or in the JMS spec that would prohibit this type of authentication. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4200) Last Resource Gambit for non XA MDB

by Weston Price (JIRA)

Last Resource Gambit for non XA MDB ----------------------------------- Key: JBAS-4200 URL: http://jira.jboss.com/jira/browse/JBAS-4200 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Currently non XA MDB's do not support the LRG but rely on the local JMS API for redelivery support. It should be considered if we should provide this. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4010) XATerminator interrface of TxManager is not including error codes in XAExceptions thrown

by Adrian Brock (JIRA)

XATerminator interrface of TxManager is not including error codes in XAExceptions thrown ---------------------------------------------------------------------------------------- Key: JBAS-4010 URL: http://jira.jboss.com/jira/browse/JBAS-4010 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Assigned To: Weston Price Attachments: XAException.diff According to the javadoc for XATerminator, it should include an error code in the XAException thrown: e.g. see http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/XATerminator.htm... This is similar to the fix for the JBossXALocalException done in JBAS-2807 However, our XATerminator impl in TxManager is not including the error code in the thrown XAException. I'm attaching a diff that shows how to fix this for prepare(), i.e. add XA_RBROLLBACK but this also needs doing for the other methods commit/forget/rollback and tests creating to prevent regression. -- 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, 1 month

2
4
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 March 2007