RE : [JBoss-user] JBossMQ with firewalls
I tried using suggestion for java.naming.provider.url using the IP address of the server and I still get the exact same result. I do have ports 1099 and forwarded to my server on the server side, and the same on the client side for the client (I don't think it's necessary but it can't hurt). Furthermore both machines are in the DMZ which I verified. The VPN suggestion is a good one. But I hate to set up a VPN just because I can't configure JBossMQ to work with firewalls. SwiftMQ claims their JMS server works fine with firewalls so I think I'm going to their product to see how it compares to JBossMQ. Thank you for your suggestions, I appreciate the help. If you have any other suggestions please let me know. Michael PS: I can't use FreeSwan because for now I'm testing with windows machines, we don't have a testing environment set up yet (which will be Linux). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dave Smith Sent: Wednesday, July 31, 2002 7:12 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] JBossMQ with firewalls In your jndi.properties did you add java.naming.provider.url= This will tell JNDI to make a network lookup via RMI. Note that on the office firewall you will have to forward ports 1099 and to the machine hosting jboss. I would suggest get freeswan(www.freeswan.org) VPN running between the two networks. Saves having to dealing with the firewalls. Also once you forward those ports they will be open to the entire world. On Wed, 2002-07-31 at 12:26, Michael Mattox wrote: > I'm trying to get JBossMQ working with a server and a client, both > connected to the internet and both behind firewalls. I have full > access to configure the firewalls however I want. I can open any > ports necessary. The problem is I have no idea which ports I should > open. So here's what I've done: I have JBoss and JBossMQ running on > my computer at work. The client works fine. I then put the client on > my home computer (both computers are connected to the internet with > DSL, and both have simple Barricade firewalls). It doesn't work at > home. I opened up all the ports I could find in the JBoss config > files, including 1099, , 8090, and 8091. I did this for both > computers. It still doesn't work. I even put them both in the DMZ. > Here is the line of code and the > exception: > > TopicConnectionFactory topicConnectionFactory = > (TopicConnectionFactory) jndiContext.lookup("ConnectionFactory"); > > javax.naming.CommunicationException: Receive timed out. Root exception > is java. > net.SocketTimeoutException: Receive timed out > at java.net.PlainDatagramSocketImpl.receive(Native Method) > at java.net.DatagramSocket.receive(DatagramSocket.java:671) > at > org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:91 > 9) > at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:997) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:436) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) > at javax.naming.InitialContext.lookup(InitialContext.java:347) > at com.x.detector.Detector.receiveEvents(Detector.java:83) > at com.x.detector.Detector.main(Detector.java:49) > > Again, this client works perfectly 100% of the time when I run it on > the same computer as the server. I'm sure this is related to the > firewall / NAT. Unfortunately I can't disable this at work to prove > it. > > If anyone has any ideas on getting this to work I'd greatly appreciate > it. > > Thanks, > Michael > > > > --- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBossMQ with firewalls
In your jndi.properties did you add java.naming.provider.url= This will tell JNDI to make a network lookup via RMI. Note that on the office firewall you will have to forward ports 1099 and to the machine hosting jboss. I would suggest get freeswan(www.freeswan.org) VPN running between the two networks. Saves having to dealing with the firewalls. Also once you forward those ports they will be open to the entire world. On Wed, 2002-07-31 at 12:26, Michael Mattox wrote: > I'm trying to get JBossMQ working with a server and a client, both > connected to the internet and both behind firewalls. I have full access > to configure the firewalls however I want. I can open any ports > necessary. The problem is I have no idea which ports I should open. So > here's what I've done: I have JBoss and JBossMQ running on my computer > at work. The client works fine. I then put the client on my home > computer (both computers are connected to the internet with DSL, and > both have simple Barricade firewalls). It doesn't work at home. I opened > up all the ports I could find in the JBoss config files, including 1099, > , 8090, and 8091. I did this for both computers. It still doesn't > work. I even put them both in the DMZ. Here is the line of code and the > exception: > > TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory) > jndiContext.lookup("ConnectionFactory"); > > javax.naming.CommunicationException: Receive timed out. Root exception > is java. > net.SocketTimeoutException: Receive timed out > at java.net.PlainDatagramSocketImpl.receive(Native Method) > at java.net.DatagramSocket.receive(DatagramSocket.java:671) > at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:91 > 9) > at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:997) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:436) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) > at javax.naming.InitialContext.lookup(InitialContext.java:347) > at com.x.detector.Detector.receiveEvents(Detector.java:83) > at com.x.detector.Detector.main(Detector.java:49) > > Again, this client works perfectly 100% of the time when I run it on the > same computer as the server. I'm sure this is related to the firewall / > NAT. Unfortunately I can't disable this at work to prove it. > > If anyone has any ideas on getting this to work I'd greatly appreciate > it. > > Thanks, > Michael > > > > --- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBossMQ with firewalls
I'm trying to get JBossMQ working with a server and a client, both connected to the internet and both behind firewalls. I have full access to configure the firewalls however I want. I can open any ports necessary. The problem is I have no idea which ports I should open. So here's what I've done: I have JBoss and JBossMQ running on my computer at work. The client works fine. I then put the client on my home computer (both computers are connected to the internet with DSL, and both have simple Barricade firewalls). It doesn't work at home. I opened up all the ports I could find in the JBoss config files, including 1099, , 8090, and 8091. I did this for both computers. It still doesn't work. I even put them both in the DMZ. Here is the line of code and the exception: TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory) jndiContext.lookup("ConnectionFactory"); javax.naming.CommunicationException: Receive timed out. Root exception is java. net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:671) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:91 9) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:997) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:436) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) at javax.naming.InitialContext.lookup(InitialContext.java:347) at com.x.detector.Detector.receiveEvents(Detector.java:83) at com.x.detector.Detector.main(Detector.java:49) Again, this client works perfectly 100% of the time when I run it on the same computer as the server. I'm sure this is related to the firewall / NAT. Unfortunately I can't disable this at work to prove it. If anyone has any ideas on getting this to work I'd greatly appreciate it. Thanks, Michael --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user