Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LazyConnectionDataSourceProxy causes exception in WebSphere with an Oracle database [SPR-10312] #14946

spring-projects-issues opened this issue Feb 18, 2013 · 0 comments
in: data type: bug


Copy link

@spring-projects-issues spring-projects-issues commented Feb 18, 2013

Tim Alkemade opened SPR-10312 and commented

When DataSourceUtils calls connection.setReadOnly, it catches the exception, logs it and continues.
When LazyConnectionDataSourceProxy gets instructions to call connection.setReadOnly, it does not catch the exception. This causes problems when using WebSphere 7 with an oracle database. The Oracle database does not support readOnly, and WebSphere 7 will throw an exception (see also even though setReadOnly is only a hint. So the exception should be logged and ignored similar to what happens in DataSourceUtils.

Attached is a maven project which can be used to reproduce the issue and a stack trace.

Affects: 3.1 GA


@spring-projects-issues spring-projects-issues added type: bug in: data labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.2.2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: data type: bug
None yet

No branches or pull requests

2 participants