You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Andrew Scott <an...@aegeon.com.au> on 2007/06/21 02:41:16 UTC
Stupid Connector question
This might be a stupid question to you guys. But I am new to J2EE
Application Servers, etc.
Is it possible to set roller to use the context on a specific port that is
not the port of the Application Server. I ask this because I can do this
with JRun, so that the port is different to the Tomcat Management Console
port number.
Is it a simple matter of a server.xml in the roller webapp or is something
in the roller customer properties.
Any advice would be great.
Andrew Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
<http://www.aegeon.com.au> www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
Re: Stupid Connector question
Posted by Gary Kephart <ga...@pobox.com>.
Andrew Scott wrote:
> Thats the thing I am not asking for tomcat to run on multiple ports.
>
> I want roller too run any any port...
Since web apps are deployed _within_ an app server, they cannot run
without an app server. The app server receives the HTTP requests and
routes them to the appropriate wep app. The app server is listening to
the ports, not the web apps.
Gary
--
http://blog.photeus.com/
The penalty that good men pay for not being interested in politics is to
be governed by men worse than themselves - Plato, philosopher (427-347 BCE)
Re: Stupid Connector question
Posted by Andrew Scott <an...@aegeon.com.au>.
Thats the thing I am not asking for tomcat to run on multiple ports.
I want roller too run any any port...
On 6/22/07, Matt Raible <ma...@raibledesigns.com> wrote:
>
> Yes, whatever port you configured in server.xml is the port that
> Tomcat will run on. I'm not sure if it's possible to specify multiple
> connectors and run Tomcat on multiple ports. However, the one thing
> you can do is put Apache in front of Tomcat, run Tomcat on whatever
> port you want and connect Apache to Tomcat using mod_jk. This uses an
> ajp protocol that allows you to connect Apache to Tomcat directly and
> is very efficient.
>
> Matt
>
> On 6/21/07, Andrew Scott <an...@aegeon.com.au> wrote:
> > Ok,
> >
> > Currently using Tomcat, and its running on the default port 8080.
> >
> > Which is set in server.xml. My question is that it will only run on that
> > port, even though the context is /Roller it is not accessible by any
> other
> > port.
> >
> > I am new to this, I have looked into the Tomcat docs and I am not sure
> what
> > I need to do to make the context available on any port.
> >
> >
> >
> > On 6/22/07, Guy Katz <gk...@allot.com> wrote:
> > >
> > > This is an application server specific issue so you will have to take
> a
> > > look at your vendor's documentation (a lot of them use tomcat anyway
> so
> > > if you are already familiar with tomcat that's good).
> > > What you ask for is very basic so I would be very surprised if you
> will
> > > not be able to achieve what you want.
> > >
> > > -----Original Message-----
> > > From: Gary Kephart [mailto:gary_kephart@pobox.com]
> > > Sent: Thursday, June 21, 2007 5:05 PM
> > > To: user@roller.apache.org
> > > Subject: Re: Stupid Connector question
> > >
> > > Andrew Scott wrote:
> > >
> > > >This might be a stupid question to you guys. But I am new to J2EE
> > > >Application Servers, etc.
> > > >
> > > >
> > > >
> > > >Is it possible to set roller to use the context on a specific port
> that
> > > is
> > > >not the port of the Application Server. I ask this because I can do
> > > this
> > > >with JRun, so that the port is different to the Tomcat Management
> > > Console
> > > >port number.
> > > >
> > > >
> > > >
> > > >Is it a simple matter of a server.xml in the roller webapp or is
> > > something
> > > >in the roller customer properties.
> > > >
> > > >
> > >
> > > J2EE applications are deployed into the application server. It is the
> > > server, not the applications, that is listening to the ports.
> > >
> > > Gary
> > >
> > > --
> > > http://blog.photeus.com/
> > >
> > > The penalty that good men pay for not being interested in politics is
> to
> > >
> > > be governed by men worse than themselves - Plato, philosopher (427-347
> > > BCE)
> > >
> > >
> > >
> >
> >
> > --
> >
> >
> >
> > Senior Coldfusion Developer
> > Aegeon Pty. Ltd.
> > www.aegeon.com.au
> > Phone: +613 8676 4223
> > Mobile: 0404 998 273
> >
>
>
> --
> http://raibledesigns.com
>
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
Re: Stupid Connector question
Posted by Matt Raible <ma...@raibledesigns.com>.
Yes, whatever port you configured in server.xml is the port that
Tomcat will run on. I'm not sure if it's possible to specify multiple
connectors and run Tomcat on multiple ports. However, the one thing
you can do is put Apache in front of Tomcat, run Tomcat on whatever
port you want and connect Apache to Tomcat using mod_jk. This uses an
ajp protocol that allows you to connect Apache to Tomcat directly and
is very efficient.
Matt
On 6/21/07, Andrew Scott <an...@aegeon.com.au> wrote:
> Ok,
>
> Currently using Tomcat, and its running on the default port 8080.
>
> Which is set in server.xml. My question is that it will only run on that
> port, even though the context is /Roller it is not accessible by any other
> port.
>
> I am new to this, I have looked into the Tomcat docs and I am not sure what
> I need to do to make the context available on any port.
>
>
>
> On 6/22/07, Guy Katz <gk...@allot.com> wrote:
> >
> > This is an application server specific issue so you will have to take a
> > look at your vendor's documentation (a lot of them use tomcat anyway so
> > if you are already familiar with tomcat that's good).
> > What you ask for is very basic so I would be very surprised if you will
> > not be able to achieve what you want.
> >
> > -----Original Message-----
> > From: Gary Kephart [mailto:gary_kephart@pobox.com]
> > Sent: Thursday, June 21, 2007 5:05 PM
> > To: user@roller.apache.org
> > Subject: Re: Stupid Connector question
> >
> > Andrew Scott wrote:
> >
> > >This might be a stupid question to you guys. But I am new to J2EE
> > >Application Servers, etc.
> > >
> > >
> > >
> > >Is it possible to set roller to use the context on a specific port that
> > is
> > >not the port of the Application Server. I ask this because I can do
> > this
> > >with JRun, so that the port is different to the Tomcat Management
> > Console
> > >port number.
> > >
> > >
> > >
> > >Is it a simple matter of a server.xml in the roller webapp or is
> > something
> > >in the roller customer properties.
> > >
> > >
> >
> > J2EE applications are deployed into the application server. It is the
> > server, not the applications, that is listening to the ports.
> >
> > Gary
> >
> > --
> > http://blog.photeus.com/
> >
> > The penalty that good men pay for not being interested in politics is to
> >
> > be governed by men worse than themselves - Plato, philosopher (427-347
> > BCE)
> >
> >
> >
>
>
> --
>
>
>
> Senior Coldfusion Developer
> Aegeon Pty. Ltd.
> www.aegeon.com.au
> Phone: +613 8676 4223
> Mobile: 0404 998 273
>
--
http://raibledesigns.com
RE: Stupid Connector question
Posted by Guy Katz <gk...@allot.com>.
you should ask the tomcat users mailing list.
this has nothing to do with roller.
thanks.
________________________________
From: Andrew Scott [mailto:andrew.scott@aegeon.com.au]
Sent: Fri 6/22/2007 1:26 AM
To: user@roller.apache.org
Subject: Re: Stupid Connector question
Ok,
Currently using Tomcat, and its running on the default port 8080.
Which is set in server.xml. My question is that it will only run on that
port, even though the context is /Roller it is not accessible by any other
port.
I am new to this, I have looked into the Tomcat docs and I am not sure what
I need to do to make the context available on any port.
On 6/22/07, Guy Katz <gk...@allot.com> wrote:
>
> This is an application server specific issue so you will have to take a
> look at your vendor's documentation (a lot of them use tomcat anyway so
> if you are already familiar with tomcat that's good).
> What you ask for is very basic so I would be very surprised if you will
> not be able to achieve what you want.
>
> -----Original Message-----
> From: Gary Kephart [mailto:gary_kephart@pobox.com]
> Sent: Thursday, June 21, 2007 5:05 PM
> To: user@roller.apache.org
> Subject: Re: Stupid Connector question
>
> Andrew Scott wrote:
>
> >This might be a stupid question to you guys. But I am new to J2EE
> >Application Servers, etc.
> >
> >
> >
> >Is it possible to set roller to use the context on a specific port that
> is
> >not the port of the Application Server. I ask this because I can do
> this
> >with JRun, so that the port is different to the Tomcat Management
> Console
> >port number.
> >
> >
> >
> >Is it a simple matter of a server.xml in the roller webapp or is
> something
> >in the roller customer properties.
> >
> >
>
> J2EE applications are deployed into the application server. It is the
> server, not the applications, that is listening to the ports.
>
> Gary
>
> --
> http://blog.photeus.com/
>
> The penalty that good men pay for not being interested in politics is to
>
> be governed by men worse than themselves - Plato, philosopher (427-347
> BCE)
>
>
>
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
Re: Stupid Connector question
Posted by Andrew Scott <an...@aegeon.com.au>.
Ok,
Currently using Tomcat, and its running on the default port 8080.
Which is set in server.xml. My question is that it will only run on that
port, even though the context is /Roller it is not accessible by any other
port.
I am new to this, I have looked into the Tomcat docs and I am not sure what
I need to do to make the context available on any port.
On 6/22/07, Guy Katz <gk...@allot.com> wrote:
>
> This is an application server specific issue so you will have to take a
> look at your vendor's documentation (a lot of them use tomcat anyway so
> if you are already familiar with tomcat that's good).
> What you ask for is very basic so I would be very surprised if you will
> not be able to achieve what you want.
>
> -----Original Message-----
> From: Gary Kephart [mailto:gary_kephart@pobox.com]
> Sent: Thursday, June 21, 2007 5:05 PM
> To: user@roller.apache.org
> Subject: Re: Stupid Connector question
>
> Andrew Scott wrote:
>
> >This might be a stupid question to you guys. But I am new to J2EE
> >Application Servers, etc.
> >
> >
> >
> >Is it possible to set roller to use the context on a specific port that
> is
> >not the port of the Application Server. I ask this because I can do
> this
> >with JRun, so that the port is different to the Tomcat Management
> Console
> >port number.
> >
> >
> >
> >Is it a simple matter of a server.xml in the roller webapp or is
> something
> >in the roller customer properties.
> >
> >
>
> J2EE applications are deployed into the application server. It is the
> server, not the applications, that is listening to the ports.
>
> Gary
>
> --
> http://blog.photeus.com/
>
> The penalty that good men pay for not being interested in politics is to
>
> be governed by men worse than themselves - Plato, philosopher (427-347
> BCE)
>
>
>
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
RE: Stupid Connector question
Posted by Guy Katz <gk...@allot.com>.
This is an application server specific issue so you will have to take a
look at your vendor's documentation (a lot of them use tomcat anyway so
if you are already familiar with tomcat that's good).
What you ask for is very basic so I would be very surprised if you will
not be able to achieve what you want.
-----Original Message-----
From: Gary Kephart [mailto:gary_kephart@pobox.com]
Sent: Thursday, June 21, 2007 5:05 PM
To: user@roller.apache.org
Subject: Re: Stupid Connector question
Andrew Scott wrote:
>This might be a stupid question to you guys. But I am new to J2EE
>Application Servers, etc.
>
>
>
>Is it possible to set roller to use the context on a specific port that
is
>not the port of the Application Server. I ask this because I can do
this
>with JRun, so that the port is different to the Tomcat Management
Console
>port number.
>
>
>
>Is it a simple matter of a server.xml in the roller webapp or is
something
>in the roller customer properties.
>
>
J2EE applications are deployed into the application server. It is the
server, not the applications, that is listening to the ports.
Gary
--
http://blog.photeus.com/
The penalty that good men pay for not being interested in politics is to
be governed by men worse than themselves - Plato, philosopher (427-347
BCE)
Re: Stupid Connector question
Posted by Gary Kephart <ga...@pobox.com>.
Andrew Scott wrote:
>This might be a stupid question to you guys. But I am new to J2EE
>Application Servers, etc.
>
>
>
>Is it possible to set roller to use the context on a specific port that is
>not the port of the Application Server. I ask this because I can do this
>with JRun, so that the port is different to the Tomcat Management Console
>port number.
>
>
>
>Is it a simple matter of a server.xml in the roller webapp or is something
>in the roller customer properties.
>
>
J2EE applications are deployed into the application server. It is the
server, not the applications, that is listening to the ports.
Gary
--
http://blog.photeus.com/
The penalty that good men pay for not being interested in politics is to
be governed by men worse than themselves - Plato, philosopher (427-347 BCE)
Re: Stupid Connector question
Posted by Dave <sn...@gmail.com>.
On 6/20/07, Andrew Scott <an...@aegeon.com.au> wrote:
> This might be a stupid question to you guys. But I am new to J2EE
> Application Servers, etc.
>
> Is it possible to set roller to use the context on a specific port that is
> not the port of the Application Server. I ask this because I can do this
> with JRun, so that the port is different to the Tomcat Management Console
> port number.
>
> Is it a simple matter of a server.xml in the roller webapp or is something
> in the roller customer properties.
I'm not sure exactly what you mean, but generally speaking Roller
doesn't know or care what port is used to access it. You should use
your app server's console or it's config files to set it up to use a
different port.
- Dave