Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

avoid port number :8080 in URL ?

 
varun bihani
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can anybody help me with the solution to avoid :8080 (tomcat port number) in the URL for applications that is being developed in servlets/jsp/hibernate ?

I know there is connector mod_jk that ppl use to integrate apache and tomcat, but that is much big problem for me becoz:
I have more than 40 other jsp sites that have been running for last 8 yrs with the port number in URL.. if I integrate , means I have to make changes in all of them

Any help would b appreciatable.

Varun
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64700
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"ppl" and "becoz" are not words. Please use real words when posting.
 
varun bihani
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am so sorry..
ppl = people
becoz= because.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64700
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No need to apologize. The guideline is to benefit you. Please read this for more information.
 
Rahul Bhattacharjee
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by varun bihani:
Can anybody help me with the solution to avoid :8080 (tomcat port number) in the URL for applications that is being developed in servlets/jsp/hibernate ?


The only way to do is to configure the listener / connector to the default port 80, in that case you can avoide writing the port number in the URL.

Now about the other applications that are running in the same server.

I do not know whether its possible or not. You can configure multiple listeners for the server / tomcat.Let the one which is there to be like that and configure one more listner (a cyote listner) for you particular web application.If this is permitted , then your problem is solved.
 
varun bihani
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Rahul Bhattacharjee:


The only way to do is to configure the listener / connector to the default port 80, in that case you can avoide writing the port number in the URL.


Now about the other applications that are running in the same server.

I do not know whether its possible or not. You can configure multiple listeners for the server / tomcat.Let the one which is there to be like that and configure one more listner (a cyote listner) for you particular web application.If this is permitted , then your problem is solved.


THAT MEANS, I NEED TO USE SOME CONNECTOR LIKE mod_jK ??
how can I find out if its possible to configure 2 listners ?what is cyote listner ?
 
Rahul Bhattacharjee
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by varun bihani:


THAT MEANS, I NEED TO USE SOME CONNECTOR LIKE mod_jK ??
how can I find out if its possible to configure 2 listners ?what is cyote listner ?


mod_jk is for connecting apache's web server to tomcat.
Look at the tomcat docs for installing a new listner for your purpose.
 
Chetan Parekh
Ranch Hand
Posts: 3640
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
<Connector port="80"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />
 
varun bihani
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
but if I do this, you sure, other requests to port 80 like apache will be fine. like php, cgi ??
 
Chetan Parekh
Ranch Hand
Posts: 3640
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Varun, you are right. If will effect your existing setup. Sorry I miss understood your requirments.
 
varun bihani
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So, it is ok..
I assume, I should use connectors or listeners as Rahul suggested.. ?
 
Rahul Bhattacharjee
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Chetan Parekh:
Varun, you are right. If will effect your existing setup. Sorry I miss understood your requirments.


Can we not configure two listners? One for the existing application , which may continue to listen to port 8080 and the new one for this application which wants to route requests through 80.
If two connectors can be configured then its done.I guess now it becomes a question eligible for Tomcat forum.
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can only have only a single process serving on any one port.
If you try to have 2 Tomcats running on port 80, the second will fail to start.
 
Rahul Bhattacharjee
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No , we want to have two listners operating on two different ports.
One the default at 8080 and one more we want to add for port 80 , in the same tomcat.
 
Ben Souther
Sheriff
Posts: 13411
Firefox Browser Redhat VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If something else, Apache HTTPD for instance, is already bound to port 80, then Tomcat will need to use a different port.
 
Ben Souther
Sheriff
Posts: 13411
Firefox Browser Redhat VI Editor
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic