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