Thanks for the feedback.
After some (much) investigation, I believe I found the cause of my original
errors.
First, I had a JRun connector on the machine (global) on the webserver and
also had it on the individual web sites. This caused some greif so I
removed the global filter an installed it to each website.
The next problem I encounter was a little harder to catch. Originally, I
installed several apps to the default server. Then I made new JRun servers
to partition these apps into their own individual servers. Following the
instructions for creating new apps in the JRun Setup Guide (p. 93), I made a
copy of the default server directory, renamed it and then modified the
settings for the new server. The guide instructs to remove reference to
other applications in the local.properties file in the 'Web Applications
Settings' section, leaving only the default-app. Unfortunately, it neglects
to instruct you to remove the reference to the other applications in the '#
list of services to start' section near the bottom of the file. Due to the
fact that this is a copy of the default server, it still contained
references to the applications that were deployed to that server.
Here is the section of the local.properties that contains the references to
other applications.
# list of services to start
ejb.services=ejb,jms
ranConnector=yes
java.args={default}
java.jnipath={default}
java.classpath={default}
test1-app.rootdir=D:\\JRun\\servers\\default\\test1-app
test1-app.class={webapp.service-class}
webapp.mapping./test1=test1-app
test2-app.rootdir=D:\\JRun\\servers\\default\\test2-app
test2-app.class={webapp.service-class}
webapp.mapping./test2=test2-app
test3-app.rootdir=D:\\JRun\\servers\\default\\test3-app
test3-app.class={webapp.service-class}
webapp.mapping./test3=test3-app
test4-app.rootdir=D:\\JRun\\servers\\default\\test4-app
test4-app.class={webapp.service-class}
webapp.mapping./test4=test4-app
test1-app is the only app deployed to this server, but the other apps were
reference here as well. I have remove the other references and so far so
good.
I believe this will prevent the error I was getting, where apps that were
deployed to server1 where running in server2 and vice versa.
FYI
Tom D.
----- Original Message -----
From: "Victor Marinelli" <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 3:25 PM
Subject: Re: multiple jrun servers, one webserver
>
>
>
> > IMHO,
> > There is no way to connect multiple JRun servers to one instance of an
> HTTP
> > server.
>
> I am running 3 JRun servers which connect to one single instance of
Apache.
>
>
>
> >There is no way to map certain URL's to go to this JRun server,
> > versus this JRun server.
>
> I don't know the answer to this since I only use web applications.
>
>
>
>
>
> >The only thing you can do is to map URL's to go to
> > certain web apps, but they all must go to the same JRun server.
>
>
> Each one of my three JRun servers is running a web-app. The URL mapping
> (which must be unique) for each web-app
> is defined in the local.properties file located in the directory of the
JRun
> server that is running that specific web-app. Here is a breakdown:
>
> JRun server 1 - this server hosts web-app with a unique URL-mapping of
> /myWebApp1
> JRun server 2 - this server hosts web-app with a unique URL-mapping of
> /myWebApp2
> JRun server 3 - this server hosts web-app with a unique URL-mapping of
> /myWebApp3
>
> As you can see, you cannot specify the same URL mapping for each web-app
> across multiple servers since Jrun then won't know which server to use.
>
>
>
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
