Thanks Karl Yes, i do agree that looking at the Jetty logs should give us some clue. I will check and get back on this.
On Tue, Jul 16, 2019 at 2:31 PM Karl Wright <[email protected]> wrote: > Hosting on a different app server is something you could easily do. Or, > since this takes many months before it appears, you might just live with it. > But first, there should be access logs the Jetty writes to. It should be > possible for you to see what's happening from those logs if you can find > them. It would be good to understand exactly what was going wrong, I'm > sure you would agree. If running on unix, you could also monitor the jetty > process to see whether file handles appear to be leaking. > Karl > > > On Tue, Jul 16, 2019 at 2:25 PM Praveen Bejji <[email protected]> > wrote: > >> @Michael, >> >> There are no error in the on the logs. The app just goes down abruptly. >> >> @Karl, >> Assuming that Jetty server has some issue, what do you suggest? Is >> hosting Manifold on some other server(say Tomcat ) an alternative? >> >> >> On Mon, Jul 15, 2019 at 9:04 AM Michael Cizmar < >> [email protected]> wrote: >> >>> Are there some errors or anything interest in the log? >>> >>> >>> >>> -- >>> >>> Michael Cizmar >>> >>> >>> >>> >>> >>> *From: *Karl Wright <[email protected]> >>> *Reply-To: *"[email protected]" <[email protected]> >>> *Date: *Monday, July 15, 2019 at 7:56 AM >>> *To: *"[email protected]" <[email protected]> >>> *Subject: *Re: Reg. unstable Manifold instance >>> >>> >>> >>> I have heard of this issue before. The app server is what is giving >>> back the 404 errors. I wonder if the version of jetty we ship has a >>> resource leak of some kind. >>> >>> >>> >>> Karl >>> >>> >>> >>> >>> >>> On Sun, Jul 14, 2019 at 11:34 PM Praveen Bejji <[email protected]> >>> wrote: >>> >>> Hi, >>> >>> >>> >>> We have been running manifoldcf for almost 6 months now. We see that the >>> Web app goes down intermittently and gives an 404 error. However, we are >>> able to access the authority URL and could see that jobs are running as >>> scheduled. >>> >>> Restarting Manifold fixes the issue but it appears again after couple of >>> weeks. This has been our routine for few months now. >>> >>> >>> >>> To give some background on our setup, Manifold is running in quick start >>> single process model on an Linux server. Linux server has a 8 Core CPU with >>> 16 Gig of RAM. Manilfold is hosting a documentum connector and 2-3 custom >>> connectors. >>> >>> >>> >>> Any help will be greatly appreciated. >>> >>> >>> >>> -PK >>> >>>
