Bug 668548

Summary:	Possible bug in file descriptor handler in 389 1.2.7
Product:	[Retired] 389	Reporter:	jazcek
Component:	Unknown	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED DUPLICATE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.2.7	CC:	andrey.ivanov, benl, dan, jmates, nhosoi
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-31 17:24:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	639035

Description jazcek 2011-01-10 19:04:54 UTC

Description of problem:  Whenever a connection times out with a T2 error, the 389 server will not accept any new connections.  All existing connections function perfectly


Version-Release number of selected component (if applicable): 389 1.2.7-5 from fc 14 directory


How reproducible:
100% of the time a T2 message is logged

Steps to Reproduce:
1. A host cause the 389 server to disconnect with a a T2 error
2. Try to reconnect from any host and it will be denied 
  
Actual results:
Server disconnections connection with an error and does not allow any new connections to occur

Expected results:
Server drops the connection with an error but continues to allow new connections to be made

Additional info:

Comment 1 Noriko Hosoi 2011-01-31 17:24:51 UTC


*** This bug has been marked as a duplicate of bug 668619 ***