Hello,

On November 4 we applied the 2.2.1 security patch for GroupWise Messenger, and ever since then we've had an annoying problem. Every day we come in to reports that people cannot log in to messenger with a "Directory Error." To fix it, we restart the archive and messenger agents. We could write a cron script which restarts it automatically daily but we'd rather find the root cause. The log when the issue starts has something similar to this:

01:23:09 BA0 SPL User {User and Context FQDN} disconnected via {IP Address}
01:23:09 BA0 SPL Login: {User and Context FQDN} via {IP Address}
01:23:20 BA0 TCP Monitor thread closing connection with address ::ffff:{IP Address} (activity time out).
01:23:20 BA0 TCP *** PHYSICAL PORT DISCONNECTED, Tbl Entry=8, Socket=19
02:39:34 BA0 TCP *** NEW PHYS. CONNECTION, Tbl Entry=8, Socket=19
02:40:26 BA0 TCP *** NEW PHYS. CONNECTION, Tbl Entry=13, Socket=24
02:41:33 BA0 TCP *** NEW PHYS. CONNECTION, Tbl Entry=15, Socket=31
02:41:33 BA0 SPL Login failed [0xAE07]: {Username, not FQDN} - DDC: Could not create or duplicate a directory context
02:41:33 BA0 TCP *** PHYSICAL PORT DISCONNECTED, Tbl Entry=15, Socket=31

After this happens, no one else can log in until the services are restarted.

Has anyone else seen this behavior since applying the most recent security patch?