You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/01/08 18:42:19 UTC
DO NOT REPLY [Bug 33014] New: -
setReadOnly always being called
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33014>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33014
Summary: setReadOnly always being called
Product: Commons
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Dbcp
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: graham@darkcoding.net
Using Hibernate, DBCP and Sybase I am getting the following warning from Hibernate:
010SK: Database cannot set connection option SET_READONLY_FALSE
This is because DBCP's PoolableConnectionFactory.activateObject(..) method is
calling 'setReadOnly' on the Connection and the database does not support it.
Hibernate spots the warning and logs it.
There is a guard in the 'activateObject' method to only call setReadOnly if
'_defaultReadOnly' is not null. All the constructors of
PoolableConnectionFactory set '_defaultReadOnly' to a 'boolean' so it will never
be null.
This goes against what the docs
(http://jakarta.apache.org/commons/dbcp/configuration.html) say about the
defaultReadOnly config parameter: "If not set then the setReadOnly method will
not be called".
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org