| I believe I’ve checked everything you mention (see below) to no avail. One thought I had is that the servers are running different Mac OS versions. Could the WOAdaptor compiled for El Capitan on the head machine not be able to use a remote app instance running under Mt. Lion on the remote machine?
On Dec 7, 2015, at 11:02 PM, Klaus Berkling < email@hidden> wrote:
On Dec 6, 2015, at 9:21 PM, Jeff Schmitz < email@hidden> wrote:
I'm using one machine for a web server (e.g. Apache, womonitor) and one for the application server (wotaskd, my app)
I’ve set the WebObjectsConfig appropriately on the webserver machine, e.g.:
I have added the application server host and the application to java monitor on the web server and it all looks good.
I start up the remote application from the webserver javamonitor, but when I try to reach the app using the webserver URL, it says application not found. However, if I try to access the application by going straight to the application server URL, it works. (I do have apache setup on the application server as well).
I tested the 2001 and 1085 ports using telnet from the web server to the application server, and both ports are open.
One thing that isn’t clear in the wiki instructions is what the WOHost parameters should be set to on the app server machine. I set them to the app server itself’s address, and it works with a local instance of Apache/JavaMonitor, but should I keep them set to this when I want to run them as remote applications from the webserver?
If that’s not it, any other ideas?
If it's not a firewall issue, it might be a DNS issue if you are using host names. If memory serves then use the WOHost parameter as the hostname you use in JavaMonitor. If you have multiple IP addresses you'll need to check if everyone is listing on the right socket, check with lsof -i tcp:1085 or lsof -i tcp:2001
I can definitely telnet from the head machine to both port 2001 and 1085 on the app server. WOHost in the respective wotaskd property files on each server matches the respective host in JavaMonitor . Also, reverse DNS lookups are correct for both machines.
Make sure there is only one JavaMonior running, usually on the head node. One wotaskd on each server and only one apache web server - the head node.
JavaMonitor is only running on the head node. Each server has a wotaskd running, and apache is only running on the head node.
Try to completely set up one host only, so no www2 server anywhere - not in JavaMonitor nor WebObjectsConfig. First use localhost and make sure the app is working.
Everything works fine on the head node, which is running on instance of the application, and all WOHost parameters and specified JavaMonitor hosts are using domain name, NOT localhost.
Then use the servers' IP address, at this point you can't use 'localhost' anymore anywhere. Make sure your app is still working.
The head node is working using the domain name that comes up on a reverse lookup of the machine IP address. After that add the other host to WebObjectsConfig and JavaMonitor using the IP addresses (avoiding any DNS issues). Double check the syntax on that line. JavaMonitor should say that both hosts are available.
Done, again using domain name that comes up on reverse host lookup of the machine IP, e.g. netbrandeds-mini1.netbrandeds.infohost 208.52.189.44 JavaMonitor on the head machine does say both hosts are available. If you make changes in JavaMonitor to the configuration, make sure you see the SiteConfig.xml file change on both servers (usually in /Library/WebObjects/Configuration).
I did have to do a Synchronize Host to get both SiteConfig.xml files in agreement as to the URL to Adaptor setting. It originally was pointing to itself. However even after doing the sync, it’s still exhibiting the same behavior.
If both servers are talking to each other, add your application in JavaMonitor and add one instance for each host. Then try to turn them on and off and watch the processes on each of the hosts start and stop.
JavaMonitor is able to wotaskd on both servers and can start and stop application instances on each server. So, everything looks normal except the head node’s apache/WOAdaptor is not able to successfully invoke the instance on the secondary node to serve application pages. If I set the instance on the head node to Reject new Sessions, apache returns that no Instance is Found.
So, I’m still pretty stumped on this. In my apache.conf I have the following, which lists the two hosts. It doesn’t have to be in any particular order does it?
BTW, you should be able to manage all instance nodes and instances regardless of the web server. You can check the mechanics before you turn on the site.
Hope this helps. It's been a while since I've done this.
kib
"We keep moving forward, opening new doors, and doing new things, because we're curious and curiosity keeps leading us down new paths."
Walt Disney
Klaus Berkling
www.berkling.us | @kiberkli | Photography
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|