[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
16 years, 10 months
[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
16 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-1488) Session Invalidation issue when Tomcat SSO is turned on
by Sohil Shah (JIRA)
Session Invalidation issue when Tomcat SSO is turned on
-------------------------------------------------------
Key: JBPORTAL-1488
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1488
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Server
Affects Versions: 2.6.CR2, 2.4.1 SP1
Reporter: Sohil Shah
Assigned To: Sohil Shah
Priority: Minor
Fix For: 2.6 Final, 2.4.2 Final
It turns out that when Tomcat SSO is turned on, when a user's session is invalidated,
as the portal server iterates through all the active war sessions and invalidates them, the main portal session is invalidated as well.
The code calls session.invalidate on the main portal session after that and gets and IllegalStateException because the session is already invalidated.
This exception needs to be handled smoothly so that user does not see a failure upon logout
Note: This issue surfaces only when Tomcat SSO is actiavted.
--
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, 10 months
[JBoss JIRA] Created: (JBPORTAL-1730) IdentityServiceControllerImpl : unregister existing MBean service before to re register them
by Antoine Herzog (JIRA)
IdentityServiceControllerImpl : unregister existing MBean service before to re register them
--------------------------------------------------------------------------------------------
Key: JBPORTAL-1730
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.1 Final
Reporter: Antoine Herzog
Priority: Optional
Fix For: 2.6.3 Final
In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
the Identity Beans are registered as JMX MBeans.
When redeploying the service, an exception is thrown, as the services are yet deployed.
javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
// Unregister the former service is if it is yet there.
// This to avoid the exception when redeploying this service
if (getServer().isRegistered(
new ObjectName(module.getServiceName()))) {
getServer().unregisterMBean(
new ObjectName(module.getServiceName()));
}
Thanks,
--
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, 10 months