[Twisted-Python] Signalling twistd with SIGUSR1 to rotate also interrupts txAMQP connections

We run some services that use txAMQP within twistd to connect to an AMQP bus. When we send twistd a SIGUSR1 to rotate its logs, it appears our application loses connection to the AMQP bus and needs to reconnect. This doesn't crash the app, but means the app may be offline momentarily when it should be available to process data. Is it possible that twistd is processing the SIGUSR1 and then passing it onto our app and txAMQP? We want to be able to force a log rotate without the entire app, or the connections it has open, resetting.