[OPENDJ-1969] IdleTimeLimitThread fails with null ConnectionHandlers or null ClientConnections Created: 27/Apr/15  Updated: 08/Nov/19  Resolved: 21/Nov/16

Status: Done
Project: OpenDJ
Component/s: core server
Affects Version/s: 2.6.0
Fix Version/s: 3.0.0, 2.8.0

Type: Bug Priority: Minor
Reporter: Chris Ridd Assignee: patrick diligent
Resolution: Fixed Votes: 0
Labels: release-notes

Support Ticket IDs:

 Description   

A customer reported this being logged every 5 seconds:

[21/Apr/2015:21:03:15 +0000] category=CORE severity=SEVERE_ERROR msgID=262783 msg=An unexpected error occurred in the idle time limit thread:  NullPointerException (IdleTimeLimitThread.java:125)

It looks like one of the connection handler's is returning a list containing a null ClientConnection. The only connection handlers enabled were the LDAP Connection Handler, Administration Connector, and the JMX Connection Handler.

(I note there were various JMX connection bugs in 2.6.0 which may be the root cause of the nulls.)

A consequence of the bug is that the idling thread fails and will never idle out any connections after the null.

I don't think there's much we can do here except log the connection handler name and skip if we get a null ClientConnection.



 Comments   
Comment by Chris Ridd [ 15/Jun/15 ]

Connection idling still works; the root cause for the null clientConnection is not understood.

Comment by Mark Craig [ 16/Jun/15 ]

Reopening to set release-notes label

Comment by Quentin CASTEL [X] (Inactive) [ 20/Nov/16 ]

modification of the status, in order to migrate the 'Zendesk ID' field to 'Support Ticket ID' field.

Generated at Fri Oct 23 08:40:19 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.