Setup the first instance of Orion as usual.
Setup the 2nd instance of Orion on a different port.
Use TunnelServlet in Orion 1 to forward requests to Orion 2 for necessary
vhosts.
-Joe Walnes
At 21:46 28/11/2000, you wrote:
Orioners,
Has anyone ever tried to run two instances of Orion on the
Larry Velez wrote:
I know that binding a second IP to the box and having the second Orion
listen on that IP would probably work. Is there an obvious reason
that the way I am attempting always gives me an "Error starting HTTP
server: Address already in use" error on the second instance?
Title: Running two instances of Orion on the same IP and port
Larry,
Orion
is acting just as it should. You cannot have to two servers bind to the same
port (This could create all sorts of problems). There is no web server I am
aware of that will do this. That being said, all you really
At 16:46 28.11.00 , you wrote:
Orioners,
Has anyone ever tried to run two instances of Orion on the same machine,
IP and port. What I am trying to do is have a second instance of Orion
listen to only certain virtual hosts (headers) and the first pick up any
unknown or blank headers.
The
Title: Running two instances of Orion on the same IP and port
I'm
not sure that its possible
I
would suggest doing the following
- run
2 instance of orion
- run
the 'development' instance on port 8080
- run
the 'internal network' instance on port 80
Why do
you want to run both
Title: Running two instances of Orion on the same IP and port
This
has nothing to do with Orion per se. It's a fact of life that only one
processat a time can bind to a port on a host. For example, say you
had Orion bound to port 25 along with your email server. Who would try
tohandle SMTP
Title: RE: Running two instances of Orion on the same IP and port
You guys are right. I see now the error of my ways. I was forgetting the fundamental difference that the second Orion process runs as a second VM. I was trying to recreate a setup I had often done with other webservers but
