[#JRA-6796] Connection leak when database error occurs causes JIRA to eventually hang - Atlassian JIRA

Issue Details (XML | Word | Printable)

Key:	JRA-6796
Type:	Bug
Status:	Open
Priority:	Major
Assignee:	Anton Mazkovoi [Atlassian]
Reporter:	Scott Farquhar [Atlassian]
Votes:	2
Watchers:	4

Operations

If you were logged in you would be able to see more operations.

JIRA

Connection leak when database error occurs causes JIRA to eventually hang

Created: 26/May/05 02:28 AM Updated: 24/Oct/06 11:48 PM

Component/s:

Backend / Domain Model

Affects Version/s:

3.1, 3.1.1

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian], Jeff Turner [Atlassian], pierre-yves voirol and Scott Farquhar [Atlassian]
Since last comment:	3 years, 19 weeks, 1 day ago
Labels:

Description

Under certain conditions, connections are leaked:

Tomcat (not certain if we need this)
Oracle (with tryclob...) or MSSQL
Try running quicksearch with a key that isn't found - this will search through the change history
Because Oracle (and MSSQL presumably) can't do exact text match queries in CLOBs (though 'like' queries work), and exception is thrown
This exception propagates up to JIRA code. However, ofbiz doesn't close the connection.
If you do this enough times (more than number of connections in DB pool - 8 in Tomcat's commons-dbcp) then you run out of connections, and JIRA appears to hang.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 26/May/05 02:38 AM

More info about DBCP connection parameters is available here:

http://jakarta.apache.org/commons/dbcp/configuration.html

[ Permlink | « Hide ]

pierre-yves voirol added a comment - 26/May/05 11:31 AM

Hi Scott,

Here at Pro-Concept Inc., Oracle is our "core" database and i can tell you that it's possible for Oracle to search "like" queries in CLOB.

If you have a Oracle DB on hand, try this :

1) create table my_table_with_clob (
my_clob_column clob);

2) insert some rows in this table

3) issue following statement against this table :

select * from my_table_with_clob where my_clob_column like 'wathever you want%'

4) should you see the rows containing the searched value.

FYI : here at Pro-Concept we run Oracle 9.2.0.1 through 9.2.0.6 and Oracle 10g and like "queries" on clob work very well

Cheers,
Pierre-Yves

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 26/May/05 11:19 PM

Fixing description - it's exact matches which fail, not 'like' queries.