We are observing that JTrac is crashing every 5-7 days with same exception. I am attaching the log file & the screenshot of the view we see when we visit the JTrac URL after the exception happens. Please help.
An exception is just an error, so what do you mean by "crash"?
The error message about a bad URI doesn't tell us anything - is a URL being accessed at that time?
The screenshot looks like a pretty empty directory, where there should be lots of stuff, assuming you're running JTrac as an exploded war - are you? If that's the case, I'm not surprised that Jetty can't handle the access - there's nothing to serve, after all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, if I wasn't clear. I am not running JTrac as exploded war. The behavior is that jtrac starts fine & works for a few days & we see the screen(image sent before) in place of the login screen. Since the last time this happened I saw the exception happening last in the log file which made me think that it could be related to the behavior but today when this happened again, I see that in the log file the same exception happened multiple times & jtrac continued to work until we saw the screen with the contents of /jtrac/ directory with nothing in. After stopping & restarting it, jtrac behaves normally again. The only extra thing I am doing here is to run jtrac behind nginx using the following rule,
location ~ (/jtrac|/app|/resources|/boaform|actuator|/wiki|/api|/flow) {
proxy_pass http://192.168.15.56:8888; ** <----jtrac running on port 8888**
proxy_set_header Host $host;
}
Please let me know if I can provide any other diagnostic information that would help.
Thanks,
Aejaz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are observing that JTrac is crashing every 5-7 days with same exception. I am attaching the log file & the screenshot of the view we see when we visit the JTrac URL after the exception happens. Please help.
https://imgur.com/H23z6va
Thanks,
Aejaz
An exception is just an error, so what do you mean by "crash"?
The error message about a bad URI doesn't tell us anything - is a URL being accessed at that time?
The screenshot looks like a pretty empty directory, where there should be lots of stuff, assuming you're running JTrac as an exploded war - are you? If that's the case, I'm not surprised that Jetty can't handle the access - there's nothing to serve, after all.
Sorry, if I wasn't clear. I am not running JTrac as exploded war. The behavior is that jtrac starts fine & works for a few days & we see the screen(image sent before) in place of the login screen. Since the last time this happened I saw the exception happening last in the log file which made me think that it could be related to the behavior but today when this happened again, I see that in the log file the same exception happened multiple times & jtrac continued to work until we saw the screen with the contents of /jtrac/ directory with nothing in. After stopping & restarting it, jtrac behaves normally again. The only extra thing I am doing here is to run jtrac behind nginx using the following rule,
location ~ (/jtrac|/app|/resources|/boaform|actuator|/wiki|/api|/flow) {
proxy_pass http://192.168.15.56:8888; ** <----jtrac running on port 8888**
proxy_set_header Host $host;
}
Please let me know if I can provide any other diagnostic information that would help.
Thanks,
Aejaz