You cut my ps. that explained the configuration.
Am 03.06.2008 um 12:11 schrieb Aristedes Maniatis:
On 03/06/2008, at 7:56 PM, Alexander Spohr wrote:
Am 03.06.2008 um 03:20 schrieb Aristedes Maniatis:
The docs for WOHost say "The name of the host on which the
application is running or, in a multihomed environment, the
address of the adaptor the application should use. I don't quite
get the 'address of the adaptor' part. It seems to indicate
something about the URL or the machine Apache is running on, but I
don't understand how that makes any sense.
multihomed means one machine with multiple ip-interfaces (ethernet-
adaptors).
So the sentence says that you should tell your app which of these
interface to listen to.
It has nothing to do with multiple instances or multiple machines.
Sorry to split hairs, but "the address of the adaptor the
application should use" means what?
SERVER-X has 2 ethernet-adaptors.
adaptor1’s address is 10.0.0.2
adaptor2’s address is 11.1.2.99
So you have to decide what address the adaptor has, that your app
should use.
Requests come *from* (several) machines with Apache adaptors *to*
the WOApplication.
We talk about ETHERNET-adaptors, physical sockets to put a TP-cable
in, not about mod_WebObjects or Apache.
You imply that the docs mean that WOHost should point to the host/IP
of the interface on which those requests come in.
Yes.
That's not really what the docs say: they refer to the address of
the adaptor. But which one?
The address of your chosen adaptor for the app (or wotaskd). If you
chose another adaptor to handle te requests you need to specify the
others adaptors address.
There could be more than one such adaptors on different Apache front
end servers.
Apache has nothing to do with it. And you only should have only one
ethernet-socket per network, so only one adaptor talks with the web-
servers.
For that matter I don't even understand why it matters which
interface those requests come in on, as long as they hit the
application on the right port.
Every port is bound to exactly one interface. You can not listen on
port 80 on ALL interfaces. You can only listen to 10.0.0.2:80 or/and
11.1.2.99:80
Maybe here is your misunderstanding of how ethernet and ports work.
But I guess that's why there are so many emails in the list archives
all complaining around this issue of reverse lookups, DNS, etc. The
issues which they appear to cause are very subtle. We hope to make
changes to our deployment tomorrow to see if this fixes things for us.
Not subtle: One interface, one port - one port, only on one interface.
We looked at the Anjo version of Java monitor today, but weren't
game to try it in our production environment. It looks a little...
unfinished. But who knows what improvements have gone on behind the
GUI to improve its reliability. All very welcome.
JavaMonitor is a good frontend to wotaskd. Only replace it if you dont
want to use wotaskd.
Hope this time I explained it better :)
atze
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
