It doesn't seem to be working. As indicated I moved the listener from the source to the sink and I moved the connector from the sink to the source.
Here's the Source Routing Configuration:
swiftlet.sys$routing.connectors.names=router22
swiftlet.sys$routing.connectors.router22.hostname=123.456.678.901
swiftlet.sys$routing.connectors.router22.password=pwd
swiftlet.sys$routing.connectors.router22.port=14112
swiftlet.sys$routing.connectors.router22.retrytime=60000
swiftlet.sys$routing.connectors.router22.socketfactory.class=com.swiftmq.net.JSSESocketFactory
swiftlet.sys$routing.staticroute.routers.names=router22
---
And here's the Sink Routing Configuration:
swiftlet.sys$routing.listeners.names=sslsocket
swiftlet.sys$routing.listeners.sslsocket.keepalive.interval=60000
swiftlet.sys$routing.listeners.sslsocket.hostaccesslist.names=123.456.678.901
swiftlet.sys$routing.listeners.sslsocket.password=pwd
swiftlet.sys$routing.listeners.sslsocket.port=14112
swiftlet.sys$routing.listeners.sslsocket.socketfactory.class=com.swiftmq.net.JSSESocketFactory
swiftlet.sys$routing.staticroute.routers.names=router11
--
Naturally, the Host IP addresses have been changed.
The explorer on the source side can only connect to router1 (URL: localhost) and the explorer on the sink side can't see any routers (URL: 123.456.678.901:4001).
Please advise. Thank you.
Regards, Mike
At 09:47 AM 9/13/2001 +0200, you wrote:
> Considering the potential configuration complexity and resource
> requirements (1 port/source, etc.) required with the current setup, can
> I
> reverse the sink/connector, source/listener configuration such that the
> sink uses the listener? Or, is there some other way to more efficiently
> accomplish the one-to-many, sink-to-source objective?
Yes, just make it reverse. The routing connection is independent and it
doesn't matter which side establishes the connection. So in your case the
sink router should have the routing listener on some port and all the
source routers have a connector.
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
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/[email protected]/
