The issue is been seen from two days that tomcat is not accessible though the process is running.
Due to this few functionalities are not working.
This is not new configuration.
May I know if someone could help me in finding the issue.
thanks
Related
Hi. I'm having a pretty nasty issue with the app I'm responsible for. The app was running on osgi/karaf + spring + apache camel 2.14.1. I removed osgi/karaf, upgraded spring, and moved all that to the spring boot. Camel version was upgraded to 2.24.1. And we started to see some occasional perf. issues on prod. I wasn't able to see the logs until yesterday, but what I saw there confused me a lot. The app at some point stopped processing the files for one of the routes, while the second route was working fine...
And it lasted for almost 2 hours. Yes, we have pretty high load on it but it was always like that. I just can't figure out what exactly could possibly cause that.
Few small details though... The files which this failing route is monitoring are put to the folder through the symb link. So if the monitoring folder name is /test, there is a link to it in $HOME/test(for a different user) and the other process connects through the sftp and puts files to that folder(it's not a problem with that process, I'm 100% sure that the files were on the server but this thing just didn't see them).
I to be honest have no idea where to dig. The server is pretty old, and the FS is pretty defragmented, we have also disk usage on 100%(but our admins don't think it's related + it was like that before and there were no issues). Java changed by the way from 1.6 to 1.8. I also checked the memory, it doesn't seem like there is an issue, one global GC during the 12 hours, minor collections are not that frequent. I would really appreciate any thoughts... Thank you very much!
I've encountered some problems when I tried to upgrade or add a dyno on my application. After using 2 dynes, it seems like my application process started looping and the process in not proceeding. It's working fine when I'm using 1 dyno server. Do I still have to configure anything? Because based on the tutorials that I've watched, I only have to drag to add server and Heroku will do the other process. Please help me. Thank you so much!
We have a Spring Boot app that at one point runs a Thread that calls a rest API and does something. When I run it on my machine it works well. Then if I run the same code on another machine it throws the error
SocketTimeoutException: Read timed out issue
So I thought there was some problem with server timeout. So on the other machine I've tried setting server.connection-timeout:-1 in the application.yml. since I've pulled the code from github, all the settings were identical. Then, after changing this on the other machine, it worked well there too.
So I am curious about the difference could be, maybe some settings on the machine itself? Where can I look?
I have a webapp deployed successfully in Jetty webserver.
The webserver responds to requests fine.
When I access the app it renders the home page.
Recently I noticed that when I don't use the app for certain period of time it breaks somehow. The period is somewhere around 2/3 weeks.
When I access the webapp after 2/3 weeks of idle I receive this output.
If I try to access any other link, i.e. the login page (/login.faces) I receive:
Problem accessing /error/not-found.faces. Reason:
/error/not-found.xhtml Not Found in ExternalContext as a Resource
which normally used to work before idling.
If I restart the webserver everything returns to normal and works fine. There are scheduled tasks set which make the app interact every day with database. (There is a scheduled task for fetching currency rates via webservice).
Therefore, my question is what would be the cause which breaks the site and makes it unavailable after idling? Is this a webserver (jetty) issue? Am I missing any setting which is crucial?
FYI, the project structure is: Java with Spring, Hibernate, JSF (PrimeFaces) and Jetty
This occurred due to permissions in CentOS.
If anyone faces the same issue make sure to check the logs have appropriate permissions to read and write
I'm having a Weblogic server with one Admin Server and 3 managed servers in a single cluster. ADF application is deployed in this cluster. I'm getting stuck threads intermittently in one of the managed servers. Is there any way to kill these threads which got stuck? I don't want to hinder the activities of the users in another managed servers. I just want to kill the thread associated with that particular user whose application that got stuck. Is this possible?
I'm using Windows OS.
Any help is highly appreciated.
Stuck threads cannot be killed.
All you can do is to find the root cause and fix it. Make a thread dump and analyse it.
Check this link for some guidance.