February 2007 - jboss-jira - Jboss List Archives

[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-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

[JBoss JIRA] Created: (JBAS-4001) JMS/JCA inflow adapter needs to be backported from head to 4.2 and 4.0.5 CP releases

by Weston Price (JIRA)

JMS/JCA inflow adapter needs to be backported from head to 4.2 and 4.0.5 CP releases ------------------------------------------------------------------------------------ Key: JBAS-4001 URL: http://jira.jboss.com/jira/browse/JBAS-4001 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 Reporter: Weston Price Assigned To: Weston Price The JCA/JMS inflow adapter changes in HEAD need to be backported to 4.x releases. Changes made affect transaction processing that will resolve transaction problems for redelivery for BMT and CMT Not support MDB's. -- 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-3406) JMX Console throws 500 exception on regular expressions

by gregorypierce (JIRA)

JMX Console throws 500 exception on regular expressions ------------------------------------------------------- Key: JBAS-3406 URL: http://jira.jboss.com/jira/browse/JBAS-3406 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: OSX 10.4.7 Reporter: gregorypierce When going through the Getting Started guide there is a note to search for service=JNDIView. After bringing up the JNDIView I entered a regular expression to search for all of the JNDI services and the server threw a 500 exception as opposed to saying that that format was not supported. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-3829) The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed.

by Jean-Frederic Clere (JIRA)

The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed. ------------------------------------------------------------------------------------ Key: JBAS-3829 URL: http://jira.jboss.com/jira/browse/JBAS-3829 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Environment: A cluster of 2 nodes with mod_jk. Reporter: Jean-Frederic Clere Assigned To: Jean-Frederic Clere Priority: Minor When a request comes to node2 and has a JVMRoute in JSESSIONID set to node1 the JVMRoute has to be changed to the node2 to make sure that following request will go to node2. That seems to work only for the first request going to node2 further requests does not send the cookie with JSESSIONID. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle

by Owen Taylor (JIRA)

Way to set JNDI properties for twiddle -------------------------------------- Key: JBAS-3637 URL: http://jira.jboss.com/jira/browse/JBAS-3637 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Owen Taylor Priority: Minor It is frequently useful to be able to set JDNI properties when running twiddle - for example, you might want to set jnp.disableDiscovery when checking the status of a particular server that might not be running. Right now, this is difficult to do. You can export a JBOSS_CLASSPATH which contains a jndi.properties file before running twiddle.sh, but then you have to include all the standard jars in it, which is quite annoying. A pssible fixes would be one of: A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default construction (also useful for getting a log4j.properties that doesn't drop twiddle.log in the cwd, perhaps) B) A command line option for specifying a particular properties file to load and pass to 'new InitialContext()' (slightly more convenient than A) C) A command line option to define particular properties: twiddle.sh -jnpProperty=jnp.disableDiscovery=true (Or some better syntax) The twiddle code actually does: Properties props = new Properties(System.getProperties()); props.put(Context.PROVIDER_URL, serverURL); ctx = new InitialContext(props); In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take effect, and system properties won't be looked at in the other code path either. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-989) Create performance test suite to test failover

by Manik Surtani (JIRA)

Create performance test suite to test failover ---------------------------------------------- Key: JBCACHE-989 URL: http://jira.jboss.com/jira/browse/JBCACHE-989 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc. -- 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

1
5
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 February 2007