[JBoss JIRA] Commented: (JBAS-3258) JDBC artificats should throw SQLException when already closed
by Daniel Hannum (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3258?page=comments#action_12343669 ]
Daniel Hannum commented on JBAS-3258:
-------------------------------------
This temporary fix is not working for me. It won't compile because the two @Bind annotations are not allowed (duplicate annotation, it says). I've tried to adjust the pointcut to make it work with a single bind and it still throws the exceptions and still won't hit a breakpoint in the aspect.
How long until 4.0.4SP1 is out?
> JDBC artificats should throw SQLException when already closed
> -------------------------------------------------------------
>
> Key: JBAS-3258
> URL: http://jira.jboss.com/jira/browse/JBAS-3258
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Adrian Brock
> Assigned To: Weston Price
> Fix For: JBossAS-4.0.5.CR1, JBossAS-4.0.4.SP1
>
>
> In the change to fix JBAS-2741 I mistakenly made the JDBC wrappers throw an SQL
> exception if the artifact is already closed. They should just return with an exception.
> From the Javadoc:
> "Calling the method close on a Statement object that is already closed has no effect."
> e.g. In WrappedStatement
> public void close() throws SQLException
> {
> synchronized (lock)
> {
> if (closed)
> throw new SQLException("Already closed");
> closed = true;
> }
> lc.unregisterStatement(this);
> internalClose();
> }
> this should be:
> public void close() throws SQLException
> {
> synchronized (lock)
> {
> if (closed)
> return;
> closed = true;
> }
> lc.unregisterStatement(this);
> internalClose();
> }
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBREM-47) Dynamic classloading
by Tom Elrod (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-47?page=all ]
Tom Elrod updated JBREM-47:
----------------------------
Priority: Major (was: Critical)
> Dynamic classloading
> --------------------
>
> Key: JBREM-47
> URL: http://jira.jboss.com/jira/browse/JBREM-47
> Project: JBoss Remoting
> Issue Type: Feature Request
> Components: general
> Affects Versions: 1.0.1 beta
> Reporter: Tom Elrod
> Assigned To: Tom Elrod
> Fix For: 2.2.0.Beta1 (Bluto)
>
>
> Need ability for dynamic classloading to satisfy two needs. The first, is when an ejb lookup is done, and if do not have the class on the client, can download the client classes for remoting. This is much more efficient than having to serialize all these classes (as there may be many and may not even know what they are until runtime). Also, would like to add the ability for client or server to pass implementation for interfaces across the wire and if the other side does not have those classes, can load them. Once particular case when this might be needed is if using JMX sub-system, client could create custom QueryExp? implementation and pass to the server, and the server could load that class and perform the query. Will require security around 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
19 years, 10 months
[JBoss JIRA] Created: (JBCLUSTER-148) Include Tomcat's SavedRequest object into the replication process in a Jboss-Tomcat clustered environment to allow proper Single Sign On capabilities
by Alberto Rodriguez (JIRA)
Include Tomcat's SavedRequest object into the replication process in a Jboss-Tomcat clustered environment to allow proper Single Sign On capabilities
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-148
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-148
Project: JBoss Clustering
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: Q2Y6
Environment: independent
Reporter: Alberto Rodriguez
Assigned To: Brian Stansberry
Priority: Optional
In a JBoss clustered environment where session is replicated and single sign on is enabled, one cannot log in an protected clustered web application because of the lack of Serialization support of Tomcat's SavedRequest object.
Tomcat stores the information needed to restore the pre-authentication request in a note in the session in a SavedRequest object, this object is not included in the replication process because it doesn't implement Serializable.
The objective would be to make SavedRequest object Serializable in Tomcat and include this object and/or other notes in the serialization process executed when the session info is replicated.
--
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
19 years, 10 months