ReadWriteSplit only keeps used connection alive, query crashes after unused connection times out

Problem

after 60s maxscale sends "MySQL server has gone away" to the client

Setup

• wait_timeout is 60s
• master + slave
• client connects to maxscale with hintfilter and read-write-split
• worker opens connection to maxscale on startup
• worker is reading every 1s from maxscale
• worker never writes (or hints) anything to the master

Files

• my.cnf of slave
• maxscale.cnf
• maxscale.log with "enable log-priority debug"

Speculation

I'm guessing that the connection to the master times out after 60s because it is not being used, this is somehow causing maxscale to close the connection to the client...

the read-write split should be able to also handle that only one connection is being used