> ok, did that, and no jvm starts which is what manual mode
> seems to be. I'm a little confused here, you mentioned one
> of the configuration files. I only have one file, jserv.conf,
> what other are you referring to? I'm definitely not clear on
> something here. Is the basic idea, don't let Apache start
> Jserv, do it manual so I control a single invocation?
> Is there a command line syntax described anywhere to properly
> start jserv with the jserv propertie file and everything.
Here is your model as I see it (lets start without jserv):
httpd 1: listens on port 80
httpd 2: listens on port 443
h1 has its own httpd.conf file (this is where you defined the 80).
h2 has its own httpd.conf file (this is where you defined the 443).
now, you add jserv into the mix:
h1 starts up fine, it starts a jvm process which binds to port 8007 and
things are fine.
h2 starts up fine, it starts a jvm process which tries to bind to port 8007
and things are not fine because two process cannot bind to the same port.
solution is to have only one httpd start up the jvm. this would mean
creating two different jserv.conf files. h1 would point to conf1 and h2
would point to conf2. the only different between the two conf files would be
that h1 is responsible for starting the jvm and h2 would not try to start
the jvm.
there is a really good document which explains Apache JServ's 3-tier'ed
model.
<http://java.apache.org/faq/index.cgi?file=36>
ps. please stop cc'ing me on the messages, i'm subscribed to the list. ;-)
thanks,
-jon
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
