Here's a complex one that I hope someone can help us with. We have routers on two machines. Call A the machine that contains two topics (AU and TR), a publisher, and a subscriber, and B the machine that contains a second topic, TN. A and B are on different subnets. Subscribers to the topics on A and B always correctly receive messages when they are up. Further, when TR receives a message, subscriber on A uses a reply-to to send a message to topic TN on B. All of this works. Change 1: make both subcribers on A and B durable, so that they would receive messages published to AU after being off. With only this change, only the durable subscriber on A receives messages on AU after being off. A is on the same machine as the router containing topic AU. B does not receive the message. If B is off when the message is published to the topic, B never receives it. A's use of reply-to to send messages to TN on B still works. Change 2: add a static route on B to machine A. This fixes the durable subscriber - B now also receives messages published to AU after being off (as does A). However, the reply-to no longer works. A appears to send a message to B's reply-to topic TN, but it is never delivered. Argh. Change 3: add a topic name in the properties file of A that is the same as the name of the topic TN (which is created on B). Now the reply-to works. The problem is, when the router on A is started, we don't know the name of the topic - it is unique to machine B. And machines can come and go, so it is impossible to populate the properties file statically. And we don't want to bring the router up and down just to reread the properties file. We are using SwiftMQ with 2.1.0 on Linux with Java 1.3.0. I'd appreciate any help or suggestions. Chris ------------------------------------------------------ SwiftMQ developers mailing list * http://www.swiftmq.com To unsubscribe from this list, send an eMail to [EMAIL PROTECTED] and write in the body of your message: UNSUBSCRIBE developers <your-email-address> Archive: http://www.mail-archive.com/developers@mail.iit.de/
