View Incident Report

Serious

Reported By: Graeme Cox
Reported On: 9/11/2008
For: Version 2.01 Build 4

# 2757 Improper Session Termination Can Cause Runaway CPU Consumption On One Processor

We are experiencing continual lockups of the ElevateDB Server. The lockup happened again today. Memory was at 450mb, 17 sessions, 12 active connections. CPU was at a constant 25%.

I think your correct, a runaway session thread (or some session issues with connection/ dis connection) is causing the issue.

Comments

The problem was caused by the session comms manager not handling a receive of 0 bytes, which indicates a disconnection on the other end of the connection, properly. The thread would then enter a hard loop and peg the processor that it was running on. After this occurred a few times, all available processors on the machine would be pegged 100%.

Resolution

Fixed Problem on 9/12/2008 in version 2.01 build 5

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap