[
https://issues.apache.org/jira/browse/OLINGO-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501232#comment-16501232
]
Wallace commented on OLINGO-1269:
---------------------------------
Pull request can be found here:
https://github.com/apache/olingo-odata2/pull/17
> Database connection isn't released when updating a not-existed entity
> ---------------------------------------------------------------------
>
> Key: OLINGO-1269
> URL: https://issues.apache.org/jira/browse/OLINGO-1269
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.10
> Reporter: Wallace
> Priority: Minor
> Labels: JPA, connection-pooling, transaction
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I am using odata2-jpa (version 2.0.10) in my project. When I batch update a
> not-existed entity with an Odata request, connections in connection pool are
> used up rapidly and "Connection is not available, request timed out" occurs.
> HTTP Method: PATCH
> HTTP URL: http://localhost:8080/Webinar.svc/Conferences(2)
> HTTP Body:
> {
> "Name": "MSA Architecture111",
> "StartDate": "2018-05-06T08:00:00",
> "EndDate": "2018-05-10T17:00:00"
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
