Lucee 6 Boncode Connection Problems

Zackster · March 19, 2026, 11:30pm

Fix logging deadlock, connection timeout, and socket leak bugs

Bilal-S:master ← zspitzer:fix/logging-and-connection-bugs

opened 11:28PM - 19 Mar 26 UTC

## Summary Fixes multiple bugs in the logging and connection handling code that… cause IIS to hang permanently or return 502 errors. These have been reported by multiple Lucee users: - [#113](https://github.com/Bilal-S/iis2tomcat/issues/113) — IIS hangs at midnight when logging is enabled - [Lucee Forum: Boncode Connection Problems](https://dev.lucee.org/t/lucee-6-boncode-connection-problems/17145) — midnight crash with scheduled tasks - [Lucee Forum: 502 errors after idle](https://dev.lucee.org/t/lucee-7-win-2022-iis-boncode-502-errors-after-idle/17151) — 502 on first request after idle period ## Bugs fixed ### Midnight crash / IIS permanent hang - **Logger initialisation race** — `p_Logger` is static but `CheckMutex()` ran unsynchronised from every constructor. At midnight when the log filename rolls over, multiple threads raced to create the new logger, causing file-locking errors. Added `lock` around initialisation. - **Unhandled exception in `RecordSysEvent`** — `EventLog.SourceExists()` was called outside the try/catch. Under restricted IIS app pool identities it throws because Security/State event logs are inaccessible. Wrapped the whole method in try/catch. - **Mutex never released on exception** — All four logging methods (`LogMessage`, `LogException`, `LogPacket`, `LogMessageAndType`) acquired the mutex but only released it in the happy path. Any exception permanently abandoned the mutex, deadlocking all subsequent requests. Moved `ReleaseMutex()` into `finally` blocks. - **Null reference in `ConnectionError`** — `p_NetworkStream.Close()` called without null check. When errors occurred before the stream was assigned, this threw a secondary `NullReferenceException`. ### 502 after idle / connection timeout - **Keep-alive timer cast bug** — `(Timer)sender` cast to `System.Threading.Timer` instead of `System.Timers.Timer` due to the `using` import. The handler threw `InvalidCastException` on every fire, meaning connection timeouts have never worked. - **Socket/stream leak** — `CloseConnectionNoError()` had the close logic for `NetworkStream` and `TcpClient` commented out. Connections were never properly closed, leaking sockets and leaving them in CLOSE_WAIT/FIN_WAIT_2 state. ### Other fixes - Added missing `p_Logger != null` guards on three unprotected call sites - Changed `p_ConnectionsCounter++/--` to `Interlocked.Increment/Decrement` for thread safety ## Test plan - [x] CI builds successfully - [x] Integration test: IIS + Lucee 7 + patched DLLs serves pages through BonCode (port 80) - [x] Integration test: Tomcat direct (port 8888) still works - [ ] Tester with scheduled tasks running at midnight confirms no more hangs - [ ] Tester with idle connections confirms no more 502 on first request

There are updated DLLs as an artifact at the bottom of this page