[
https://issues.apache.org/jira/browse/SLING-11730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-11730.
-------------------------------------
Resolution: Invalid
Thanks for the report [~prasad907109]. This does not look like a problem in
Sling, but rather a problem with the interactions between the Jackrabbit JCR
repository and your database. I suggest that you ask the [Apache Jackrabbit
Project](https://jackrabbit.apache.org/jcr/index.html) for assistance, probably
on the users' list.
> sling database connection exhausted
> -----------------------------------
>
> Key: SLING-11730
> URL: https://issues.apache.org/jira/browse/SLING-11730
> Project: Sling
> Issue Type: Bug
> Components: App CMS
> Affects Versions: JCR Jackrabbit Client 2.0.2
> Reporter: Prasad Shembekar
> Priority: Major
> Attachments: error-1.txt, repository-datasource.xml,
> repository-jndi.xml, repository-org.xml, standalone.xml
>
>
> We are using apache sling with following dependencies in our project.
> org.apache.jackrabbit : jackrabbit-core:2.1.1
> org.apache.sling: org.apache.sling.launchpad.base:2.3.0:war
> We are seeing database connection exhaust issue while running on wildfly 20
> and oracle 12c.
> Please see the attached error.txt for more details.
> We tried using connection pooling but still the issue persists.
> Attached the repository xmls for your references.
> repository-org.xml ---> Existing one.
> Tried with JNDI
> repository-jndi.xml
> standalone.xml
>
> Tried with Datasource
> repository-datasource.xml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
