You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Cory Prowse (JIRA)" <ji...@apache.org> on 2010/10/23 04:57:20 UTC
[jira] Created: (JCR-2798) JCAManagedConnectionFactory should chain
cause exception
JCAManagedConnectionFactory should chain cause exception
--------------------------------------------------------
Key: JCR-2798
URL: https://issues.apache.org/jira/browse/JCR-2798
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-jca
Affects Versions: 2.1.1
Reporter: Cory Prowse
In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception. This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
Jukka Zitting on 12-Oct-2010 said:
This constructor is not available in J2EE version 1.3, so for now
we've been using the ResourceException.setLinkedException() method for
this (see JCR-761). To address your need we could either upgrade the
platform requirement to J2EE 1.4 or start using the J2SE method
Exception.initCause() instead of setLinkedException(). Can you file an
improvement issue in Jira about this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Resolved] (JCR-2798) JCAManagedConnectionFactory should
chain cause exception
Posted by "Claus Köll (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll resolved JCR-2798.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Claus Köll
> JCAManagedConnectionFactory should chain cause exception
> --------------------------------------------------------
>
> Key: JCR-2798
> URL: https://issues.apache.org/jira/browse/JCR-2798
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jca
> Affects Versions: 2.1.1
> Reporter: Cory Prowse
> Assignee: Claus Köll
> Priority: Minor
> Fix For: 2.4
>
>
> In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception. This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
> Jukka Zitting on 12-Oct-2010 said:
> This constructor is not available in J2EE version 1.3, so for now
> we've been using the ResourceException.setLinkedException() method for
> this (see JCR-761). To address your need we could either upgrade the
> platform requirement to J2EE 1.4 or start using the J2SE method
> Exception.initCause() instead of setLinkedException(). Can you file an
> improvement issue in Jira about this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-2798) JCAManagedConnectionFactory should
chain cause exception
Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2798:
-------------------------------
Fix Version/s: (was: 2.4)
2.3.3
> JCAManagedConnectionFactory should chain cause exception
> --------------------------------------------------------
>
> Key: JCR-2798
> URL: https://issues.apache.org/jira/browse/JCR-2798
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jca
> Affects Versions: 2.1.1
> Reporter: Cory Prowse
> Assignee: Claus Köll
> Priority: Minor
> Fix For: 2.3.3
>
>
> In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception. This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
> Jukka Zitting on 12-Oct-2010 said:
> This constructor is not available in J2EE version 1.3, so for now
> we've been using the ResourceException.setLinkedException() method for
> this (see JCR-761). To address your need we could either upgrade the
> platform requirement to J2EE 1.4 or start using the J2SE method
> Exception.initCause() instead of setLinkedException(). Can you file an
> improvement issue in Jira about this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-2798) JCAManagedConnectionFactory should
chain cause exception
Posted by "Claus Köll (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll updated JCR-2798:
----------------------------
Priority: Minor (was: Major)
> JCAManagedConnectionFactory should chain cause exception
> --------------------------------------------------------
>
> Key: JCR-2798
> URL: https://issues.apache.org/jira/browse/JCR-2798
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jca
> Affects Versions: 2.1.1
> Reporter: Cory Prowse
> Priority: Minor
>
> In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception. This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
> Jukka Zitting on 12-Oct-2010 said:
> This constructor is not available in J2EE version 1.3, so for now
> we've been using the ResourceException.setLinkedException() method for
> this (see JCR-761). To address your need we could either upgrade the
> platform requirement to J2EE 1.4 or start using the J2SE method
> Exception.initCause() instead of setLinkedException(). Can you file an
> improvement issue in Jira about this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-2798) JCAManagedConnectionFactory should
chain cause exception
Posted by "Claus Köll (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136807#comment-13136807 ]
Claus Köll commented on JCR-2798:
---------------------------------
initCause() instead of setLinkedException() will be used now.
fixed in rev 1189620
> JCAManagedConnectionFactory should chain cause exception
> --------------------------------------------------------
>
> Key: JCR-2798
> URL: https://issues.apache.org/jira/browse/JCR-2798
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jca
> Affects Versions: 2.1.1
> Reporter: Cory Prowse
> Priority: Minor
>
> In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception. This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
> Jukka Zitting on 12-Oct-2010 said:
> This constructor is not available in J2EE version 1.3, so for now
> we've been using the ResourceException.setLinkedException() method for
> this (see JCR-761). To address your need we could either upgrade the
> platform requirement to J2EE 1.4 or start using the J2SE method
> Exception.initCause() instead of setLinkedException(). Can you file an
> improvement issue in Jira about this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira