Hello, I've been playing with c++ broker federation recently and have some questions. I am trying to setup a push exchange federation from source broker to destination broker. The brokers are both version 0.10
the federation is set up using similar command as: $ qpid-route route add dst_broker:1888 admin/1234@src_broker:1889 -s -d -t ssl "my.exchange" "#" This setup seems alright. Messages are passing through, however: 1) when I stop the destination broker and start it again, the following log messages starts to apper in cca 2s interval: the destination broker: 2012-01-18 18:50:36 info SASL: Mechanism list: PLAIN 2012-01-18 18:50:36 warning Client closed connection with 541: internal-error: Sasl error: SASL(-4): no mechanism available: No worthy mechs found (qpid/SaslFactory.cpp:280) 2012-01-18 18:50:38 info SASL: Mechanism list: PLAIN 2012-01-18 18:50:38 warning Client closed connection with 541: internal-error: Sasl error: SASL(-4): no mechanism available: No worthy mechs found (qpid/SaslFactory.cpp:280) 2012-01-18 18:50:40 info SASL: Mechanism list: PLAIN source broker: 2012-01-18 18:50:56 info Inter-broker link established to dst_broker:1888 2012-01-18 18:50:56 info Inter-broker link disconnected from dst_broker:1888 Closed by peer The link never gets reconnected until i restart the source broker also. After that everything works well again.. 2) when I try to remove the route using following command: $ qpid-route route del dst_broker:1888 admin/1234@src_broker:1889 -s -d -t ssl "my.exchange" "#" both brokers start logging rapidly, quickly filling up all disk space with the log file. destination broker log: 2012-01-18 18:16:37 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2012-01-18 18:16:37 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2012-01-18 18:16:37 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) source broker log: 2012-01-18 18:16:35 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2012-01-18 18:16:35 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2012-01-18 18:16:35 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) What could that mean? Perhaps a bug? Certainly a nice way to DOS my destination broker, while only needing the acl rights to create a link. 3) The automatically created bridge queue (bridge_queue_2_UUID) on the source broker seems to always have the durable flag disabled. I might have done something wrong..will retest it soon, but might this be by design? In that case, if i wanted to be able to send messages to src broker in the time, when the link src -> dst is down and have all the messages resent to the destination broker once the link is up again, what should I do? Use a queue route and have the source queue set to durable manually? 4) Why does no link appear in the qpid-tool on destination router in the push mode? Is there a way to tell how many federated brokers are connected to the destination broker? Regards Martin
