Re: Running two instances of Orion on the same IP and port
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 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
Re: Running two instances of Orion on the same IP and port
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? Yest there is, there can be only one HTTPD listening to the same port. You could run have the other instance listen to 8080 for example. I don't think binding another ip to the box will help you eiter. sven -- == Sven E. van 't Veer http://www.cachoeiro.net Java Developer [EMAIL PROTECTED] ==
RE: Running two instances of Orion on the same IP and port
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 need to do is create a new application and a new web site that is bound to a virtual host on the same instance of Orion. Orion does a good job of keeping applications separate, so you should be able to test to your hearts content. If you ever need to restart things (on the test host) then you can simply restartthe test application from the console. You need not restart Orion itself. HTH Russ -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Larry VelezSent: Tuesday, November 28, 2000 4:46 PMTo: Orion-InterestSubject: Running two instances of Orion on the same IP and port 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
Running two instances of Orion on the same IP and port
Title: Running two instances of Orion on the same IP and port 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
Re: Running two instances of Orion on the same IP and port
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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? yes, how are two VMs supposed to share a server socket??? IMO this does not work. robert thanx, Larry (-) Robert Krüger (-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH (-) Brüder-Knauß-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de
RE: Running two instances of Orion on the same IP and port
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 instances on the same port? AFAIK each port can have a maximum of one webserver using it. This isnt an orion restriction but a general webserver restriction. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Larry VelezSent: Wednesday, 29 November 2000 7:46 AMTo: Orion-InterestSubject: Running two instances of Orion on the same IP and port 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
RE: Running two instances of Orion on the same IP and port
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 requests to port 25? Orion or the mail server? The answer is whoever bound the port first. And once a process has bound to a critical port (such as a Web server binding to port 80), it usually doesn't "let go" until the process is stopped. Scott Stirling West Newton, MA -Original Message-To: Orion-InterestSubject: Running two instances of Orion on the same IP and port 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
RE: Running two instances of Orion on the same IP and port
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 with them I always used the same 'process' with different virtual hosts. Many of them never required restarting because they were just webservers and not application servers as Orion is. With our development Orion setup we often make changes that require a restart and I was trying to avoid the restart of one Orion from affecting all the sites being served by that box. The only reason I was trying to use the same IP and port was because I did not understand why it should not work. Now I do. thanx, Larry -Original Message- From: Scott Stirling To: Orion-Interest Sent: 11/28/2000 8:28 PM Subject: RE: 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 process at 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 to handle SMTP requests to port 25? Orion or the mail server? The answer is whoever bound the port first. And once a process has bound to a critical port (such as a Web server binding to port 80), it usually doesn't let go until the process is stopped. Scott Stirling West Newton, MA -Original Message- To: Orion-Interest Subject: Running two instances of Orion on the same IP and port 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 reason for us doing it this way is to have a test installation of Orion that will be restarted often and a second 'stable 'installation that will run some ancillary sites for our internal network. 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? thanx, Larry
