Skip to content

Oracle IntegrationTests fail occasionally with ORA-12516 #1815

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.

Sign up for GitHub

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

Jump to bottom
Closed
schauder opened this issue Jun 13, 2024 · 1 comment
Closed

Oracle IntegrationTests fail occasionally with ORA-12516 #1815

schauder opened this issue Jun 13, 2024 · 1 comment
Labels
type: task A general task
Milestone
3.2.7 (2023.1.7)

Comments

@schauder
Copy link
Contributor

After reading
https://dba.stackexchange.com/questions/110819/oracle-intermittently-throws-ora-12516-tnslistener-could-not-find-available-h
I suspect this is because the TNS-Listener takes some time to take note of closed connections, thus overestimating the number of open connections.
This seems likely when connections are opened and closed in rapid succession as is the case with tests.
@loiclefevre
Copy link
Contributor

Using a connection pool shared across the tests would help.

schauder added a commit that referenced this issue Jun 14, 2024
@schauder
Create one connection pool for Oracle.
02eef36 
We now use one pooled `DataSource` for Oracle.

This should avoid problems with the TNS-Listener, which seems to have a problem with constantly opening and closing connections.

Closes #1815
schauder added a commit that referenced this issue Jun 14, 2024
@schauder
Create one connection pool for Oracle.
007b45f 
We now use one pooled `DataSource` for Oracle.

This should avoid problems with the TNS-Listener, which seems to have a problem with constantly opening and closing connections.

Closes #1815
@schauder schauder mentioned this issue Jun 14, 2024
Closed
schauder added a commit that referenced this issue Jun 14, 2024
@schauder
Create one connection pool for Oracle.
2f1d2e8 
We now use one pooled `DataSource` for Oracle.

This should avoid problems with the TNS-Listener, which seems to have a problem with constantly opening and closing connections.

Closes #1815
Original pull request #1816
schauder added a commit that referenced this issue Jun 14, 2024
@schauder
Create one connection pool for Oracle.
8eca0a7 
We now use one pooled `DataSource` for Oracle.

This should avoid problems with the TNS-Listener, which seems to have a problem with constantly opening and closing connections.

Closes #1815
Original pull request #1816
@schauder schauder added this to the 3.2.7 (2023.1.7) milestone Jun 14, 2024
@mp911de mp911de added the type: task A general task label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: task A general task
Projects
None yet
Milestone
3.2.7 (2023.1.7)
Development

Successfully merging a pull request may close this issue.

Create one connection pool for Oracle spring-projects/spring-data-relational
3 participants
@schauder @mp911de @loiclefevre