Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Problem re-assigning a new Connector to an embedded tomcat instance

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there!

I'm trying to assign a new Connector to an embedded tomcat instance to change the port it listens to at runtime.

At the moment i'm trying it like this:


In the end, the server is not listening anymore to the old port 18080, but also doesn't seem to listen to the new port 18181. What can i do? How do i have to properly set a new Connector?

Best regards,

David

 
Saloon Keeper
Posts: 22289
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that any Connector mods you do are going to have to be done before you start the embedded Tomcat.

Why would you want to change listener ports on a running server anyway?
 
David Web
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm working on a legacy application thats startup procedure takes more time than we can afford to have the server down. So i'm checking if i can start a new instance on another port, shut down the running server and switch the port asap to the actually needed port.
 
Tim Holloway
Saloon Keeper
Posts: 22289
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You should consider setting up a cluster, instead, since you're already committed to running multiple instances of the webapp concurrently. That will allow you to work within standard frameworks plus gain all the benefits of a cluster. Including being able to get outside support, which is a lot easier to do when working with standards than with one-off solutions.

You might also want to consider offloading the long-running process to an external backend such as an RMI server, if it's something that works for your needs.
 
    Bookmark Topic Watch Topic
  • New Topic