I need advice from experienced berth users.
I support 2 linux machines (with Jetty 9.0.3) behind a load balancer (Amazon cloud). From time to time my Jetty containers close for no reason "Thread-2". At the same time.
The following log is displayed and the container stops for no reason. No mistakes. With no exceptions. Gracefully closes. - This is already strange! But ... both 2 berths from two cars go down at the same time ... ???
Missing crash log (node 1):
2013-09-24 18: 51: 19.447: INFO: oejs.ServerConnector: Thread-2: Stopped ServerConnector @ 22480241 {HTTP / 1.1} {0.0.0.0:2323} ...
2013-09-24 18: 51: 23.443: INFO: oejsl.ELContextCleaner: Thread-2: javax.el.BeanELResolver cleared 2013-09-24 18: 51: 23.443: INFO: oejsh.ContextHandler: Thread-2: Stopped oejwWebAppContext @ 5892d4a8 {/, file: / home / ec2-user / jetty / webapps / ROOT /, UNAVAILABLE} {/ ROOT}
Missing crash log (node 2):
2013-09-24 18: 51: 22.152: INFO: oejs.ServerConnector: Thread-2: Stopped ServerConnector @ ba4bb9 {HTTP / 1.1} {0.0.0.0:2323} ...
2013-09-24 18: 51: 25.605: INFO: oejsl.ELContextCleaner: Thread-2: javax.el.BeanELResolver cleared 2013-09-24 18: 51: 25.605: INFO: oejsh.ContextHandler: Thread-2: Stopped oejwWebAppContext @ 460434 {/, file: / home / ec2-user / jetty / webapps / ROOT /, UNAVAILABLE} {/ ROOT}
Normal Stop Log for comparison (start.jar --stop)
2013-09-25 16: 25: 16.993: INFO: oejs.ServerConnector: ShutdownMonitor: stopped ServerConnector @ ba4bb9 {HTTP / 1.1} {0.0.0.0:2323} ...
2013-09-25 16: 25: 21.049: INFO: oejsl.ELContextCleaner: ShutdownMonitor: javax.el.BeanELResolver cleared 2013-09-25 16: 25: 21.049: INFO: oejsh.ContextHandler: ShutdownMonitor: Stopped oejwWebAppContext @ 46 , file: / home / ec2-user / jetty / webapps / ROOT /, UNAVAILABLE} {/ ROOT}
Note that "Thread-2" stops the server for no apparent reason, not the "ShutdownMonitor" thread. What can happen? Is there a hidden door that can stop the container besides starting "start.jar" with -stop?
Please, help!
Update:
Well, I found out that if I kill this process instead of calling "stop", the result is the same ... thread-2. Therefore, I believe linux is killing my process. Maybe OOM. I study. Perhaps this question is no longer needed. Thanks
Update 2:
The error was that I started the process in my terminal (without &), so it worked in the foreground, tied to this terminal. When the terminal session ended, the process ended.
Revo