I use tomcat 6.0.32. When I do shutdown tomcat says that
tomcat did not stop in time. pid file was not removed
I get some memory leak error messages ..while doing shutdown . The error message are like below.
Sep 5, 2011 3:49:41 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/abc] appears to
have started a thread named [failedAuthRateLimit_RateLimitAger)] but
has failed to stop it. This is very likely to create a memory leak.
What could be the reason ...does the memory leak prevents tomcat from shutting down ?
The error message doesn't prevent the tomcat to shutdown, but it warns you that there is a potential memory leak which should be fixed.
There were some worker threads , which were preventing proper shutdown of tomcat. Now I resolved it, by properly shutting down the worker threads before shutting down the tomcat
Related
I am trying to install flink on windows running into all sorts of problems . Please help.
Downloading the tar file from net, does not give me windows bat file options. Used the download links at https://flink.apache.org/downloads.html#apache-flink-1111. So i cannot run start-local.bat. Infact i dont even have start-local.sh . I ended up installing cygwin just so i can run start cluster bat
However running the start cluster bat is giving weird issues and exiting immediately.
$ ./start-cluster.sh
Starting cluster.
Starting standalonesession daemon on host DESKTOP**.
Starting taskexecutor daemon on host DESKTOP**.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Improperly specified VM option 'MaxMetaspaceSize=268435456
'
This is an open bug for sometime and is deferred to Flink 1.14 version.
https://issues.apache.org/jira/browse/FLINK-18438
https://issues.apache.org/jira/browse/FLINK-18792
Running Neo4j Desktop version 1.0.15. Trying to start DB causes the start fail:
Database failed to start:
DB [database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a] 'v3.3.1' exited
with status 'KILLED'. Check the logs
Major Log parts are below
2018-02-26 23:03:38.004+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, C:\Users\kiril\AppData\Roaming\Neo4j Desktop\Application\neo4jDatabases\database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a\installation-3.3.1\data\databases\graph.db
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.backup.OnlineBackupKernelExtension#c6e0f32' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Suppressed: org.neo4j.kernel.lifecycle.LifecycleException: Exception during graceful attempt to stop partially started component. Please use non suppressed exception to see original component failure.
Caused by: java.io.IOException: Unable to establish loopback connection
It might be your neo4j was still running.
I solved this problem by shutting down the database and restarting it.
Platform: Windows 10;
Neo4j Desktop version: 1.1.13
Open a commend-line window and go to the directory of your neo4j database.
run
bin\neo4j status
to check the status of your database.
If it is running, run
bin\neo4j stop
to shut down your database.
Then go back to the Neo4j Desktop, click the start button, and it could be symptom-free.
I had the same problem and the issue was resolved when I cloned the graph I was connecting. Thereafter, I could connect to the new graph without any problem.
We are using Camel-Quartz2 version 2.12.0 with clustering environment everything is working as excepted, but the issue was when I try to restart the bundle, camel routes are not starting, stating the below error.
org.quartz.impl.jdbcjobstore.JobStoreTX ClusterManager: detected 1
failed or restarted instances. org.quartz.impl.jdbcjobstore.JobStoreTX
ClusterManager: Scanning for instance "MACHINE-NAME"'s failed
in-progress jobs.
There is no exception in the log. Please advice to resolve this issue.
Quartz2 cron
quartz2://CNTR_TRIGGER/CNTR_UPDATE?job.name=containerUpdates&job.durability=true&deleteJob=true&stateful=true&cron=0/10+*+*+*+*+?
I am getting this error about mysql:
INFO: Shutting down log4j
09-ene-2014 9:57:21 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
GRAVE: A web application registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
09-ene-2014 9:57:21 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: A web application appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.
There're a lot information about it in others questions. I already updated my mysql lib to the version 5.1.28 (before, I was working with 5.0.8 which contains a bug about it) but it doesn't still work. I have checked that I have that lib in my war. Like a test, I deleted my mysql lib from WEB-INF/lib and I copied to TOMCAT/lib and I missed that error, why?. I don't want to copy that jar in TOMCAT/lib. I'm working with Tomcat6.
I'm having some problems restarting plesk on our server.
I increased the memory limit in our PHP.ini file and had stopped the server and was in the process of restarting when i've received the following error:
[root#server77-68-52-152 ~]# /etc/init.d/psa start
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
Starting Plesk... failed
Starting drwebd service... failed
I'll be honest I'm very new to the dedicated server side of things so need all the help I can get!
Turns out it was an earlier SSL upgrade that broke plesk...it hadn't come to light because plesk hadn't been restarted until the point I updated the PHP file!
You should always check the log files for the exact reason. It will help in fixing the issue faster. Below the log files path of plesk. Check the reason there why plesk is failing to start.
Error log: /var/log/sw-cp-server/error_log
Access log: /usr/local/psa/admin/logs/httpsd_access_log
Panel log: /usr/local/psa/admin/logs/panel.log