I am facing one issue constantly on the server. I have deployed the node js application. It's working fine for few hours after that automatically it goes down. It is showing proxy error in apache logs:
Introduction
I do have WebApi on.Net Core 1.1 & simple test application executing some scenario with calls to my API in multiple threads. Web API is hosted under IIS on WS 2012 R2.
Problem
When I do start my test application with 20 threads in 20-30s test application begin to receive 401 error from the server. After some investigation, I've noticed that dotnet.exe process is suddenly terminated & restarted on the server on high load.
There is no information neither in my logs nor in Windows event log (only one from IIS AspNetCore Module about starting new process: Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' started process '10248' successfully and is listening on port '23570')
I've tried to reproduce this on my machine without any success - this does not happen when my API is hosted in IIS Express from VS.
Question
What may be the reason?
I am new to Web Service and LAMP Stack.Currently I am working on a Web Application.It is a PHP Based Application that uses Apache Tomcat Web Server 8.0.26 ,MySQL Database ad Linux operating system(LAMP Stack).It has Web Services in Spring.
Following are the issues I am facing with the Application:-
1) Responses are slow over a period of few weeks from a web service hosted on tomcat.
Temporary Solution:-The problem is solved when we restart the Web Server.
2) What are the tools we can use to monitor tomcat / performance ?
Regards
Kaustubh
Take the dump of heap usage before and after of slow down and analyze. And also check your connection pooling with the database, check whether logs are getting rotated properly or not, check the number of active sessions in tomcat admin console.
I have installed Worklight 6.2 on Linux, using Liberty 8.5.5 and DB2 10.5. Created the DB2 databases for WRKLGHT and WLREPORT. Have executed the Server Configuration Tool and successfully created a Worklight Server configuration (did not have any errors in the Console view when running the Ant tasks, tables were created successfully in the database, and configuration shows deployed status in the SCT). Created a runtime environment in the SCT, also seemed to succeed (no errors in Console view, tables created/updated, runtime environment shows deployed in the SCT). Stopped and restarted the Liberty server.
Can hit Worklight admin at (/worklightconsole) and log in successfully using my demo user, however it then indicates there are no runtime environments. When trying to access runtime environment at /worklight/console (which should be the correct URL given how I created the runtime config in SCT using my Worklight project WAR), I get various errors: first "Service unavailable since initialization is not yet complete." then after retrying for about a minute or two I get "javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)".
Seems the management service is not starting up successfully. Upon reviewing the messages.log I see the following error precede it: "FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny serve. The most common reason is a failure in JMX communication with the ''worklightadmin'' service. You need to restart the web application after fixing the problem. [project worklight]" and this creates an FFDC log.
I know this is a lot of information but trying to be complete. Anything I should check to fix the JMX communication issue and get the management service starting?
Thank you for the replies back. Turns out there is an issue with Liberty (I was on 8.5.5.0) and the IBM JDK I was using (1.7_64). Swapped out to the Oracle JRE (1.7.0_60-b19), pointed Liberty to use it, and the problem was solved. I am pursuing a fix with the Liberty team through IBM Support for this issue.
I cannot give a unique solution, but I can explain the situation and this may lead to a solution.
The runtime servlet initialization tries to contact the Worklight Admin service. The Worklight Admin service is a web application that must be running when the runtime starts. The runtime was not able to find the Worklight Admin service. It waited a while, in case that the Worklight Admin service is just starting up, but then gave up due to a timeout because within a given time, it could not find the Worklight Admin service.
Possible reasons:
the web server is not at all configured to run the Worklight Admin service. In your case, this seems not the problem, since you can access the Worklight Console. You should also see in the log file whether the Worklight Admin service did start.
the worklightadmin service might never start up ... this could be a configuration problem, e.g. with the WLADMIN data base. This could also be detected from the server logs.
when the runtimes and the Worklight Admin service start up together, it might be that the Worklight Admin service simply takes too long to start. Let's say you have 100 webapps, and the runtime starts first and the Worklight Admin service starts last, it could be that the 98 other webapps take too much time to start. In that case, make your web server lighter ... run only Worklight on that webserver, nothing else.
the Worklight Admin service starts, but the runtime cannot communicate with it. This indicates that the JMX communication is misconfigured. Follow the documentation of the webserver how to configure JMX. For liberty, see http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_admin_restconnector.html?cp=SSD28V_8.5.5%2F1-5-2-10-1&lang=en
My application was running perfectly on cloudbees . Suddenly I got MongoHQ connection error .
When I restarted my application without making any change in the application , It was running perfectly again .
Caused by: java.io.IOException: couldn't connect to [sawyer.mongohq.com/*] bc:java.net.NoRouteToHostException: No route to host
at com.mongodb.DBPort._open(DBPort.java:228)
at com.mongodb.DBPort.go(DBPort.java:112)
at com.mongodb.DBPort.go(DBPort.java:93)
Is there any reason why cloudbees mongohq stop connecting in running application .
It sounds like there was an issue with Mongo connectivity - most likely at the Mongo end since I believe they live on AWS the same as the CloudBees app servers.
Check if you use the sawyer mongo instance
Check if problems started around this outage - http://status.mongohq.com/services/sawyer/2013/1/8