You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/05/28 14:14:17 UTC

[jira] [Resolved] (OAK-2918) RDBConnectionHandler: handle failure on setReadOnly() gracefully

     [ https://issues.apache.org/jira/browse/OAK-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke resolved OAK-2918.
---------------------------------
    Resolution: Fixed

> RDBConnectionHandler: handle failure on setReadOnly() gracefully
> ----------------------------------------------------------------
>
>                 Key: OAK-2918
>                 URL: https://issues.apache.org/jira/browse/OAK-2918
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: rdbmk
>    Affects Versions: 1.2.2, 1.0.14, 1.3
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.3.0, 1.2.3, 1.0.15
>
>
> It appears that WAS wraps Oracle JDBC connection objects and throws upon setReadOnly():
> {noformat}
> java.sql.SQLException: DSRA9010E: 'setReadOnly' is not supported on the WebSphere java.sql.Connection implementation.
> at com.ibm.ws.rsadapter.spi.InternalOracleDataStoreHelper.setReadOnly(InternalOracleDataStoreHelper.java:369)
> at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.setReadOnly(WSJdbcConnection.java:3626)
> at org.apache.jackrabbit.oak.plugins.document.rdb.RDBConnectionHandler.getROConnection(RDBConnectionHandler.java:61)
> {noformat}
> ...which of course is a bug in WAS (setReadOnly() is documented as a hint, the implementation is not supposed to throw an exception here); see also <http://www-01.ibm.com/support/docview.wss?uid=swg1PM58588>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)