# Inactive client Check\_CDB\_Phase closed

**URL:** <https://dmap-community.ductus.global/t/inactive-client-check-cdb-phase-closed/4431>\
**Category:** CDB and CDB API\
**Created:** [April 27, 2023, 9:56pm UTC](https://dmap-community.ductus.global/t/inactive-client-check-cdb-phase-closed/4431 "2023-04-27T21:56:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [May 2, 2023, 10:49am UTC](https://dmap-community.ductus.global/t/inactive-client-check-cdb-phase-closed/4431/4 "2023-05-02T10:49:56Z")

</div>

> [@venkonan](#):
>
> ```auto
> "DEBUG> 21-Apr-2023::06:26:53.001 TM2 confd[5454]: devel-cdb inactive client Check_CDB_Phase closed"
> 
> ```
> 
> Client side log:
> 
> ```auto
> com.tailf.conf.ConfException: unexpected end of file
> 
> ```

“End of file” or EOF means that the socket, here TCP connection, closed. Since the ConfD developer log and the Java application client side both report that the connection was closed, it seems like a TCP communication issue between them, not an issue with the application or ConfD.

You can simulate the connection issue as described previously in this post: [Control socket closed with error -2 and then ConfD client exit with "INTERNAL ERROR" - #4 by cohult](http://dmap-community.ductus.global/t/control-socket-closed-with-error-2-and-then-confd-client-exit-with-internal-error/3852/4)

---

_[View the full topic](https://dmap-community.ductus.global/t/inactive-client-check-cdb-phase-closed/4431)._
