Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] web app specific port in single jetty instance

Either way, syncing component updates seems like the interesting design-for-production issue for a high-traffic site, and an existing solution could be the cause of the single-process constraint, if already locally-solved or by an existing package less interesting to folk who are addicted to original solutions:


On 7/29/19 2:28 AM, Bill Ross wrote:
Can you describe why? It seems to once-educated me that a server's whole job is to service a port, and I'd expect you can run multiple jetty servers within a 'larger' server process, so they could share infrastructure as easily as separate webapps do.


On 7/29/19 2:22 AM, deepak dhandapani wrote:
Here, we need to created multiple server instances which is not feasible for our application.
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top