Error java.lang.OutOfMemoryError: unable to create new native thread:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2015 05:37 AM
Hi,
We are getting the below error after the dev instance is cloned. In the system log it is showing the below two different errors.
Uncaught exception in GlideServlet.process(): : java.lang.OutOfMemoryError: unable to create new native thread: java.lang.Thread.start0(Native Method)
java.lang.Thread.start(Thread.java:640)
java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(ThreadPoolExecutor.java:703)
java.util.concurrent.ThreadPoolExecutor.prestartAllCoreThreads(ThreadPoolExecutor.java:1392)
com.glide.sys.util.FixedQueueThreadPoolExecutor.execute(FixedQueueThreadPoolExecutor.java:75)
com.glide.sys.util.FixedQueueThreadPoolExecutor.queueTransaction(FixedQueueThreadPoolExecutor.java:60)
com.glide.ui.GlideServlet.doAsyncGlideServletTransaction(GlideServlet.java:448)
rrdb.update: org.jrobin.core.RrdException: Bad sample timestamp 1444820520. Last update time was 1444820520, at least one second step is required: no thrown error
Please let me know if anyone received similar error and found any root cause.
Thanks in advance
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2015 06:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2015 06:59 AM
Hello Kumaran,
Can you check if your dev instance has in sys_trigger table (System Scheduler -> Scheduled Jobs) a jobs with name "Stats: Servlet" with a System ID or Claimed By from production?
If you find records for that job that come from production instance, you need to delete them.
Regards,
Sergiu
