# Dead lock in graph, that reads data from MySQL

**URL:** <https://forum.cloverdx.com/t/dead-lock-in-graph-that-reads-data-from-mysql/759>\
**Category:** CloverDX Platform\
**Created:** [October 1, 2010, 12:00am UTC](https://forum.cloverdx.com/t/dead-lock-in-graph-that-reads-data-from-mysql/759 "2010-10-01T00:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![avackova](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@avackova](https://forum.cloverdx.com/u/avackova)\
**Post date:** [October 1, 2010, 12:00am UTC](https://forum.cloverdx.com/t/dead-lock-in-graph-that-reads-data-from-mysql/759/1 "2010-10-01T00:00:00Z")

</div>

Sometimes graph, that cooperates with MySQL database (DBInputTable, DBJoin, DBLookupTable) hangs up. There is no error, but graph is still running and the number of processed records doesn’t change. What can be the cause?

---

<div class="post-metadata">

**Author:** ![avackova](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@avackova](https://forum.cloverdx.com/u/avackova)\
**Post date:** [October 1, 2010, 10:30am UTC](https://forum.cloverdx.com/t/dead-lock-in-graph-that-reads-data-from-mysql/759/2 "2010-10-01T10:30:54Z")

</div>

The reason is the bug in MySQL jdbc driver ([http://bugs.mysql.com/bug.php?id=31353](http://bugs.mysql.com/bug.php?id=31353)). To avoid the never-ending graph execution set _socketTimeout_ connection property. Then the graph will fail, but it won’t run “forever”.
