- Security clearance of port
- Availability of port resource
- Conflicts between multiple running servers
- Properly-declared URI endpoints
An RIA will asynchronously connect via a RemoteObject call on another port. It requires a valid connection. Utilities like netcat can save you from a quagmire of ineffectual random testing.
First, open the port in apache, as it will be the ORM-enabled server. Typically, the port is 8000 or 8080 for arbitrary reasons of convention and familiarity. Make sure your 8000 or 8080 is not tied up with memchache or some other port-requisite ancillary utility. Open up ports.conf and add the port in the configuration script.
TEST THE PORT
Restart the apache server. Using a port utility such as netcat, test port connectivity. One quick way is to use netcat from a command line. Netcat will attempt to connect to any port(s) you specify and report the protocol it encountered:
nc -v -w 2 -z target 20-30
FIREWALLS
Don't forget to modify your security settings to allow the port! Specifically, if you have set up a firewall, iptables requires an entry allowing public connections over the port in question or connections will fail. If they have been changed, be sure to restart the apache server and that the rules have been saved either via command-line or the initializing script, usually /etc/network/interfaces.
Be sure your apache server's NameVirtualHost settings allow the wildcard * and not only localhost connections. This way, requests from your http-alt port will bypass your proxy server altogether. Apache might warn you thus, but it can be ignored:
[Thu Sep 03 16:20:42 2009] [warn] NameVirtualHost *:80 has no VirtualHosts
With these potential obstructions addressed, you should be able to tunnel your way to fame and fortune.
NEXT UP
How to put that port to use in an RIA RemoteObject call.
No comments:
Post a Comment