I've been trying to debug an error during topology setup, and I think I've narrowed it down to a failed queueDeclare call. This was very hard to figure out, as it looked a lot like a hanging process - but I've managed to poke around enough to realise that the default rpc timeout response is 10 minutes (which seems like a bad default to me, but that's a different issue).
https://github.com/rabbitmq/rabbitmq-java-client/blob/5.8.x-stable/src/main/java/com/rabbitmq/client/ConnectionFactory.java#L1446-L1456
As far as I can tell, it isn't possible to override this parameter.
It would be good to extend the options to cover setting this.
Would it also be reasonable to extend an open interface for future settings, either by mapping keys to calls via reflection, or by exposing a callback which would be passed the ConnectionFactory and could modify it?
I've been trying to debug an error during topology setup, and I think I've narrowed it down to a failed
queueDeclarecall. This was very hard to figure out, as it looked a lot like a hanging process - but I've managed to poke around enough to realise that the default rpc timeout response is 10 minutes (which seems like a bad default to me, but that's a different issue).https://github.com/rabbitmq/rabbitmq-java-client/blob/5.8.x-stable/src/main/java/com/rabbitmq/client/ConnectionFactory.java#L1446-L1456
As far as I can tell, it isn't possible to override this parameter.
It would be good to extend the options to cover setting this.
Would it also be reasonable to extend an open interface for future settings, either by mapping keys to calls via reflection, or by exposing a callback which would be passed the ConnectionFactory and could modify it?