> Authentication works fine. Problem is the brigde, especially that it > caches connections for re-use under the factory name. In your case that is > plainsocket@router2. Therefore, if you create a bridging with plainsocket > for user-a and then creates a new bridging for user-b with the same > factory, it re-uses the previous created connection and the user-b bridge > has the rights of user-a. > > Disabling the subscribe grant for user-a should resolve your problem. Sorry but I couldn't understand "Disabling the subscribe grant for user-a". I've already disabled the subscribe grant for user-a for topic.b. I made an extra socket which is configured to permit accesses only from router1 - named socket_for_router1@router2 listening at port 4005. I thought that making new socket resolve the problem, but it didn't. Is this a caching problem? And, I noticed that the number of JMS Swiftlet Usage increases per minute. It's because JMS Bridge Extension doesn't have predefined name and clientID and it uses another ones when it try to reconnect to the server. Is there any way to define the name and clientID of JMS Bridge Extension or is there any way to solve the problem? Thanks, -- 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/

Reply via email to