[rabbitmq-discuss] JSON-RPC Channel Plugin

• Previous message: [rabbitmq-discuss] Published message not queued after publish-ok received when connection quickly closed
• Next message: [rabbitmq-discuss] JSON-RPC Channel Plugin
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

The JSON-RPC Channel plugin appears to log to stdout which makes it immune to the "rabbitmqctl rotate_logs" command. As we're using it in production, the startup file is getting pretty large in places. Is this considered a bug? Any suggestions?

An example of what ends up being spit out in the startup log:

debug:: HTTP Channel started, timeout 300
debug:: HTTP Channel timed out, closing.

(picture lots and lots of those)

Regards,

Gavin 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110505/105dfa27/attachment.htm>

• Previous message: [rabbitmq-discuss] Published message not queued after publish-ok received when connection quickly closed
• Next message: [rabbitmq-discuss] JSON-RPC Channel Plugin
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]