Bug 118625 - Indexer, RequestManager, SimpleQueueManager, and DigestQueueManager threads die
Summary: Indexer, RequestManager, SimpleQueueManager, and DigestQueueManager threads die
Status: NEW
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
(Show other bugs)
Version: nightly
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-18 14:16 UTC by Brett Prucha
Modified: 2008-05-01 15:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Brett Prucha 2004-03-18 14:16:55 UTC
Description of problem:

I don't know if this is related to my SQL Server jdbc driver or if it 
applies to Oracle and PostgreSQL as well but the Indexer, 
RequestManager, SimpleQueueManager, and DigestQueueManager threads 
die when my database goes down.  These threads have a try catch block 
with a finally block that either call txn.commitTxn() or txn.abortTxn
().  The problem is that when the database goes down a "Connection 
reset by peer: socket write error" exception is thrown by my SQL 
Server jdbc implimentation.  After the exception is thrown the 
finally block is called with commit or abort.  The commit or abort 
then throw another "Connection reset by peer: socket write error" 
which is not caught causing the thread to terminate.


Note You need to log in before you can comment on or make changes to this bug.