[developers] Security Problem in Connecting Distributed Routers

[Kazutoshi Ono]

> In case that "Small Company" is totally untrusted I would recommend to use > the JMS bridge instead of routing. The bridge connects as JMS client, > therefore you can create a group/user on the gateway router of "Big > Company" with the specific rights on the bridging resources (queues, > topics). "Small Company" then has a JMS Bridge Extension Swiftlet on his > gateway router that connects to the "Big Company" gateway and bridges the > resources you have defined. Bridging can take place also via SSL; just > connect to a defined JSSE listener on the "Big Company" gateway router. Please let me ask one more question. I downloaded JMS Bridge Extension Swiftlet and tried to make a very simple bridge connected to router2, but in most of cases, swiftmq explorer hangs up and never comes back (The routers don't hang up but CLI and explorer become to be unable to connect to the routers). What I tried is as follows (I did it with WebLogic Configuration Example.): 0. Environment: [Hardware] x86 Family 6 Model 8 Stepping 3 AT/AT COMPATIBLE 261,612 KB RAM [OS] Microsoft Windows 2000 5.00.2195 [JDK] java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C) Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode) [SwiftMQ] Booting SwiftMQ 1.2c (12/16/2000) ... ready. JMS Bridge Extension Swiftlet Version [1.0] 1. Install JMS Bridge Extension Swiftlet into router1. 2. Copy bridge_swiftmq.properties to conf directory. -- start -- java.naming.factory.initial=com.swiftmq.jndi.InitialContextFactoryImpl java.naming.provider.url=smqp://localhost:4002/timeout=10000 -- end -- 3. Added an entity to JMS Bridge/Servers with swiftmq exploer. The operation succeeded, and generated configuration is as follows. -- start -- swiftlet.xt$bridge.servers.names=test_server swiftlet.xt$bridge.servers.test_server.configfile=../../conf/bridge_swiftmq.properties swiftlet.xt$bridge.servers.test_server.objectfactory=com.swiftmq.extension.bridge.JNDIObjectFactory swiftlet.xt$bridge.servers.test_server.retryinterval=60000 swiftlet.xt$bridge.class=com.swiftmq.extension.bridge.BridgeSwiftlet -- end -- 4. Tried to add an entity to JMS Bridge/Servers/test_server with swiftmq explorer. [Case1] Name: test_bridge Bridging Direction: remote_to_local Local Destination Name: testqueue@router1 Local Destination Type: queue Remote Factory Name: javax.jms.QueueConnectionFactory Remote Destination Name: testqueue Remote Destination Type: queue Transfer Persistence: persistent --> push "Create..". --> swiftmq explorer hangs up. [Case2] Remote Factory Name: QueueConnectionFactory <-- changed this line. --> push "Create..". --> swiftmq explorer hangs up. [Case3] Local Destination Name: testqueue <-- changed this line. --> push "Create..". --> swiftmq explorer hangs up. [Other Cases] I tried topic cases, as_source cases, etc. But in every case, swiftmq explorer hangs up and I couldn't make a bridge. 5. So, I tried to configure a bridge manually (Wrote properties directly). In this case, swiftmq explorer doesn't hang up but the bridge is ignored and deleted when the properties file is over-written. -- start -- swiftlet.xt$bridge.servers.test_server.bridging.names=test swiftlet.xt$bridge.servers.test_server.bridging.test.direction=remote_to_local swiftlet.xt$bridge.servers.test_server.bridging.test.localname=testqueue@router1 swiftlet.xt$bridge.servers.test_server.bridging.test.localtype=queue swiftlet.xt$bridge.servers.test_server.bridging.test.remotefactoryname=QueueConnectionFactory swiftlet.xt$bridge.servers.test_server.bridging.test.remotename=testqueue swiftlet.xt$bridge.servers.test_server.bridging.test.remotetype=queue swiftlet.xt$bridge.servers.test_server.bridging.test.transferpersistence=as_source -- end -- Is this a bug or my mis-configuration? Could you send me a simple sample properties file just to connect to router2? Thanks in advance, -- Kazutoshi ------------------------------------------------------ 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/