Hello Mike. Sounds like there's perhaps a step or two you may have missed in
that multiple JRun/IP address setup. That's tricky business.
As for the JWS, if you're talking about a production server, then YOU SHOULD
ABSOLUTELY SHUT OFF THE JWS. It's not made for production, and it's a
security hole if you leave it on in production. Also, there's a tiny bit of
additional overhead to have it running. For development, it's ok to leave it
on. In fact, it can be helpful to use the JWS to debug certain problems
dealing with Web server connections and such.
HTH,
Patrick
-----Original Message-----
From: Michael Goodwin [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 5:04 PM
To: JRun-Talk
Subject: RE: External web server config issue
Thanks Pat I will try that. I did have the default server working for the
last couple of months and then tried to create a new instance of the server
and that worked. But when I tried to map the default instance to one IP and
the new instance to another IP that is when things went bad. Just a quick
question, if I am using an external server, should the jrun web server be
turned "off" in the JMC settings?
Also thanks for getting back to me on this issue. I was just about ready to
remove and reinstall everything form scratch (o/s to jrun)...
-- Mike
-----Original Message-----
From: Pat Quinn [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 8:44 AM
To: JRun-Talk
Subject: RE: External web server config issue
Hey Mike. Did you have JRun connected to and working with the original
Default Web site in IIS? If so, then one possibility is that you installed
that first ISAPI filter as a global filter. Right-click on the host computer
in the left pane of the Internet Service Manager and check (Edit) the
properties for WWW. Click the ISAPI filters tab on the properties sheet; if
you see the JRun Connector Filter there, then that's your problem. Highlight
and remove it. Then go to the same tab under the Default Web site and Add
the ISAPI filter there.
That'll get you started in the right direction. If that makes your
configuration work, then good. But I'm guessing there'll still be problems.
There are 1 or 2 serious "gotchas" with multi-hosting and similar
configurations. I actually have a DevCenter article on this coming out in a
week or so.
HTH,
Patrick Quinn
Allaire Consulting
-----Original Message-----
From: Michael Goodwin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 2:46 PM
To: JRun-Talk
Subject: External web server config issue
I am having a configuration problem.
I am trying to set (JRun 3.0/IIS 4 SP5) up to work with multiple Jrun
servers and multiple domains. I have created a new instance of the default
server and it seemed to be working fine. When I created a new site in IIS
with its own IP, then I went into the JMC and attempted to configure the
External Web Server Address to the IP and listening address to the same IP.
I also changed the default installation to explicit IP addresses to ensure
no conflict.
I did confirm that IIS serves html docs properly.
Does anyone have any experience with this config, and if so could you please
shed some light?
Thanks,
-- Mike
Michael Goodwin
Project Manager
Advanta Solutions, Inc.
www.advantasolutions.com
401 E. Ocean Blvd.
Long Beach, CA 90802
ph: 562.491.3500
fax: 562.491.0070
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
