Simple adding/removing the war file itself from the
`${jetty.base}/webapps/` directory will essentially "undeploy" that webapp
on the running server.

Having separate log files on a single JVM usually requires a powerful
logging library that can sift log files based on context. (logback 1.x and
log4j2 can)

Joakim Erdfelt / [email protected]


On Wed, Dec 15, 2021 at 3:00 PM Greg Wilkins <[email protected]> wrote:

>
> Patrick,
>
> If you want to start applications individually and have separate log
> files, then you probably need to have different jetty-bases for them and
> different server ports.
>
> Alternately, you can hot deploy multiple webapps to a single running
> server.
>
> Or if you really need fine grained control, you could write your own
> deployer variation that start/stops the applications as you need.
>
>
>
>
>
>
> On Thu, 16 Dec 2021 at 03:15, Patrick Buchheit <[email protected]> wrote:
>
>> I'm getting ready to deploy an application with jetty 9.4 but there are
>> some configuration aspects I'm struggling to wrap my head around. How do I
>> layout my files in JETTY_BASE to allow the startup and shutdown of
>> individual applications if there are multiple wars in webapps? Is there a
>> command line option to specify which applications to start? How do I
>> configure the logging to have a separate log file for each application?
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/jetty-users
>>
>
>
> --
> Greg Wilkins <[email protected]> CTO http://webtide.com
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jetty-users
>
_______________________________________________
jetty-users mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/jetty-users

Reply via email to