Re: Securing active MQ

2009-02-12 Thread Joe Fernandez
I believe throwing an exception is the right thing to do. Joe Free ActiveMQ User Reference Guide @ http://www.ttmsolutions.com mcarter wrote: > > > >> >> Re #2 - you could write yourself a broker plugin thingy that extends >> BrokerService and implements the addConnection(ConnectionContext

Re: Securing active MQ

2009-02-12 Thread mcarter
> > Re #2 - you could write yourself a broker plugin thingy that extends > BrokerService and implements the addConnection(ConnectionContext context, > ConnectionInfo info) method; within which you can check the IP address of > the remote client making the connection request. > > I've imple

Re: Securing active MQ

2009-02-10 Thread ar13
We have still been unable to get activemq to honor the configuration file broker name and uselocalhost options. AMQ still tries to resolve the ip provided in the transport connector to a dns name . It does this even when provided with a broker name and setting the transport connector use localhos

Re: Securing active MQ

2009-01-27 Thread ar13
OK I have been unable to get ActiveMQ to work in a system with two connected networks in the this set up system A has two NICs NIC 0 connected to the public network NIC 1 connected to a private network I have configured AMQ to only listen on the private network for messages. I have posted th

Re: Securing active MQ

2009-01-23 Thread ar13
I have scrapped the uri addition . I tried changing the broker name property and the useLocalHostBrokerName to false. However the problem is unchanged AMQ still gets the machine DNS name from the public interface and then complains that it is unable to resolve the public DNS name on the privat

Re: Securing active MQ

2009-01-23 Thread ar13
I also tried adding " ?useLocalHost=true " to the Transport connector as follows which also fails, AMQ still gets the machine domain name from the public interface and then tries to resolve that name on the private network interface. Is this bug or is there something i am missing .? It se

Re: Securing active MQ

2009-01-23 Thread ar13
Ok i set the broker name..and commented out the network connect line. However I still get "unknown host exception" .. the host name in the error is the domain name of the server but AMQ must be getting that information over the other "public" interface ..which i have not used in the config . Is

Re: Securing active MQ

2009-01-22 Thread ar13
Ok so this line http://activemq.apache.org/schema/core"; brokerName="localhost" dataDirectory="${activemq.base}/data"> Allows me to change the broker name ..which will be used to create the UID ? Joe Fernandez wrote: > > The broker is trying to create a "unique id" for itself. Someth

Re: Securing active MQ

2009-01-22 Thread Joe Fernandez
The broker is trying to create a "unique id" for itself. Something along these lines ID:PEDRO-3500-123265619-8203-0:0 Where "PEDRO" is the host name. You can assign the broker a name via the cfg file, but it still needs the UID. Theline is telling the broker to establish a forwarding br

Re: Securing active MQ

2009-01-22 Thread ar13
Thanks for the reply I saw that too. That poses a problem . The private network I have set up for JMS has no DNS service , intentionally . Why does active MQ need an name? Can't it just default to the IP ? Can i set this name in the config file ? re#1 so this line ins correct under transport c

Re: Securing active MQ

2009-01-22 Thread Joe Fernandez
Looks like the broker is trying to generate an id for itself, but can't because this statement is hurling an unknownhost exception hostName = InetAddress.getLocalHost().getHostName(); So I reckon the IP address of the local host cannot be resolved. Check your network settings. Re #1 - the way