airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimuthu Upeksha (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRAVATA-2748) API server throws OOM exception when multiple connections are made through credentials client
Date Wed, 11 Apr 2018 18:17:00 GMT
Dimuthu Upeksha created AIRAVATA-2748:
-----------------------------------------

             Summary: API server throws OOM exception when multiple connections are made through
credentials client
                 Key: AIRAVATA-2748
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2748
             Project: Airavata
          Issue Type: Bug
          Components: helix implementation
            Reporter: Dimuthu Upeksha
         Attachments: airavata.log.api.oom, threaddump-oom-api.log

nt received for status INPUT_DATA_STAGING
2018-04-11 16:06:35,051 [pool-29-thread-24] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-NEK5000-BR2_c68b007b-7528-44cd-bc79-d1cce0d7302c, processId: PROCESS_fa3e80d7-4035-4454-8f19-1a5bc3b38b89
:- Process status changed event received for status OUTPUT_DATA_STAGING
2018-04-11 16:06:35,079 [pool-29-thread-22] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-NEK5000-BR2_37287290-9787-482d-95c4-e2aa7fe0f75e, processId: PROCESS_840dcb73-a677-4bf0-b0d1-fc8c5550507d
:- Process status changed event received for status OUTPUT_DATA_STAGING
2018-04-11 16:06:35,184 [pool-29-thread-21] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-NEK5000-BR2_0140e068-dd03-4c67-a582-7f484892ce30, processId: PROCESS_9dd82e7b-ad54-45a2-955e-c6a364365825
:- Process status changed event received for status OUTPUT_DATA_STAGING
2018-04-11 16:06:35,201 [pool-29-thread-27] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-NEK5000-BR2_1b916b14-eedc-4759-8bc1-bf0403a4758b, processId: PROCESS_53e54541-9ea9-4b6d-816a-965bbb67655e
:- Process status changed event received for status INPUT_DATA_STAGING
2018-04-11 16:06:35,304 [pool-29-thread-29] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-NEK5000-BR2_db0cdf34-261b-4b47-b9e3-00c4c5d09dd8, processId: PROCESS_dca095de-ddab-4703-89dc-9cc13b2b9545
:- Process status changed event received for status EXECUTING
2018-04-11 16:06:35,554 [pool-29-thread-30] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-AmSan-BR2::18/04/11_11:35:56_e7e391bf-d139-4786-ace0-3f3f51859a7c, processId: PROCESS_a7f10b04-0752-4897-82ee-04c8c4fd7ba0
:- Process status changed event received for status INPUT_DATA_STAGING
2018-04-11 16:06:35,618 [pool-29-thread-25] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-AmSan-BR2::18/04/11_10:58:41_cc49bbf8-df7d-41e7-90d6-f9c9e23de677, processId: PROCESS_cf7bd796-945a-4fb4-b252-3b114587c9d6
:- Process status changed event received for status OUTPUT_DATA_STAGING
2018-04-11 16:06:35,699 [Thread-15] ERROR o.a.t.server.TThreadPoolServer - ExecutorService
threw error: java.lang.OutOfMemoryError: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
 at java.lang.Thread.start0(Native Method)
 at java.lang.Thread.start(Thread.java:717)
 at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368)
 at org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:169)
 at org.apache.airavata.credential.store.server.CredentialStoreServer$1.run(CredentialStoreServer.java:80)
2018-04-11 16:06:35,761 [pool-29-thread-20] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-AmSan-BR2::18/04/11_11:36:53_bc2ce94e-4df3-4d7c-bda2-966c5aa79ad3, processId: PROCESS_519177d3-b233-40c1-92df-f8f72698d89a
:- Process status changed event received for status INPUT_DATA_STAGING
2018-04-11 16:06:35,943 [Thread-11] ERROR o.a.t.server.TThreadPoolServer - ExecutorService
threw error: java.lang.OutOfMemoryError: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
 at java.lang.Thread.start0(Native Method)
 at java.lang.Thread.start(Thread.java:717)
 at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368)
 at org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:169)
 at org.apache.airavata.registry.api.service.RegistryAPIServer$1.run(RegistryAPIServer.java:88)
2018-04-11 16:06:36,420 [pool-29-thread-28] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-AmSan-BR2::18/04/11_11:24:22_4c897426-4b4a-40df-8b55-70a6013273fe, processId: PROCESS_8d0df36b-8a89-4767-9368-7bbc20c7235f
:- Process status changed event received for status INPUT_DATA_STAGING
2018-04-11 16:06:36,420 [pool-29-thread-28] INFO o.a.a.o.s.OrchestratorServerHandler - expId:
SLM001-AmSan-BR2::18/04/11_10:57:48_fc9b2913-1d0f-43c6-b18e-f23688b0ff42, processId: PROCESS_f2a9515c-946b-46c4-8339-ff94d297acea
:- Process status changed event received for status OUTPUT_DATA_STAGING



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message