File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes EJBs and NAT. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJBs and NAT." Watch "EJBs and NAT." New topic

EJBs and NAT.

Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 720

Good morning guys,

just another question that at the moment I can't verify by myself... since I cannot reproduce the needed enviroment for a test.
Let's say we have a number of FAT swing client in a remote LAN, which can connect to a public IP of a remote datacenter in which
an appserver is installed. Let's suppose that we have no problem in opening ports from specific remote IP addresses; when a client
asks for a certain port, these are NATted to the actual appserver.
Now, I know for sure that with HTTP requests the whole thing works. I'm in doubt if it may still work when using EJB Stateful.
I would bet yes...
Has somebody some experience in a scenario like this ?

Thank you in advance.
Wouter Oet
Saloon Keeper

Joined: Oct 25, 2008
Posts: 2700

Why do you think it wouldn't work?

"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 720

Thank you for your reply....

Well, my doubt was only an hypothesys, there were no evidence that EJBs looked up over internet may not work... I thought that since RMI it's a bit problematic when you bind a remote object on a machine with several addresses and/or behind a firewall, similar problems may occur with ejbs. At the moment, as I stated before, I cannot setup a test enviroment; I'm going to start testing ASAP.

I'm currently call EJBs method incapsulating call in http transport; now I want to test JRMI/IIOP since i think that http calls may lead to performance issues due mainly to network latency. Perhaps a remote Session Facade bean may be more performant.

I agree. Here's the link:
subject: EJBs and NAT.
It's not a secret anymore!