[jira] [Updated] (AIRAVATA-3030) Add project entity sharing details to sharing button
[
https://issues.apache.org/jira/browse/AIRAVATA-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-3030:
--
Description:
Sharing details cascade from the project so those should be displayed when
creating a new experiment. Also, the project owner can't be removed and that
should be displayed. See the PGA for details.
h5. TODO
- [x] add {{parent-entity-id}} property to ShareButton. Load parent entity
information and display as read-only details
- [x] display project owner as an OWNER but read-only
- [ ] portal allows changing the project if the experiment is editable. If the
project changes, the experiment entity should be updated with the new parent
and INDIRECT_CASCADING permissions should be removed and re-added for the new
parent
- [ ] included inherited parent permissions in ShareButton count and tooltip
for new entities. Include the parent owner in the count and tooltip for
existing entities when the parent owner is not the user.
was:
Sharing details cascade from the project so those should be displayed when
creating a new experiment. Also, the project owner can't be removed and that
should be displayed. See the PGA for details.
h5. TODO
- [ ] add {{parent-entity-id}} property to ShareButton. Load parent entity
information and display as read-only details
- [ ] display project owner as an OWNER but read-only
- [ ] portal allows changing the project if the experiment is editable. If the
project changes, the experiment entity should be updated with the new parent
and INDIRECT_CASCADING permissions should be removed and re-added for the new
parent.
> Add project entity sharing details to sharing button
>
>
> Key: AIRAVATA-3030
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3030
> Project: Airavata
> Issue Type: Sub-task
> Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.19
>
>
> Sharing details cascade from the project so those should be displayed when
> creating a new experiment. Also, the project owner can't be removed and that
> should be displayed. See the PGA for details.
> h5. TODO
> - [x] add {{parent-entity-id}} property to ShareButton. Load parent entity
> information and display as read-only details
> - [x] display project owner as an OWNER but read-only
> - [ ] portal allows changing the project if the experiment is editable. If
> the project changes, the experiment entity should be updated with the new
> parent and INDIRECT_CASCADING permissions should be removed and re-added for
> the new parent
> - [ ] included inherited parent permissions in ShareButton count and tooltip
> for new entities. Include the parent owner in the count and tooltip for
> existing entities when the parent owner is not the user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-3018) Project sharing button
[ https://issues.apache.org/jira/browse/AIRAVATA-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832769#comment-16832769 ] ASF subversion and git services commented on AIRAVATA-3018: --- Commit df0d479a1ee6ac7cb2feb49ae2838633ddbc3042 in airavata-django-portal's branch refs/heads/master from Marcus Christie [ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=df0d479 ] AIRAVATA-3018 Clarifying why we can assume only one OWNER The OWNER permission, like all others, can cascade but getAllAccessibleUsers only returns DIRECT type sharings. > Project sharing button > -- > > Key: AIRAVATA-3018 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3018 > Project: Airavata > Issue Type: Sub-task > Components: Django Portal >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > Add the Share button to the Project view/edit page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2829) Job and experiment both completed as expected but STDOUT is not available as an output in the gateway
[ https://issues.apache.org/jira/browse/AIRAVATA-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832664#comment-16832664 ] Dimuthu Upeksha commented on AIRAVATA-2829: --- [~eroma_a] can you verify this with latest changes? > Job and experiment both completed as expected but STDOUT is not available as > an output in the gateway > - > > Key: AIRAVATA-2829 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2829 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.seagrid.org/ >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # Stopped pre WM (I dont think this has any link to the issue) and launched > experiments. > # After experiments are launched started pre WM. > # all the jobs got launched in the remote clusters and jobs got completed > successfully as well as the experiments. > # In slurm machine comet, stdout is not available as an output. > # But its available and its in the ARCHIVE directory. > # This is a configured output and it should be available as an output in > experiment summary > ## exp ID: SLM001-Gaussian-Comet0_3d801bf7-02d4-4205-a2f8-65b3dda9d6fc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AIRAVATA-2807) Helix: use groupResourceProfileId on ProcessModel
[ https://issues.apache.org/jira/browse/AIRAVATA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2807. - Resolution: Fixed > Helix: use groupResourceProfileId on ProcessModel > - > > Key: AIRAVATA-2807 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2807 > Project: Airavata > Issue Type: Story >Reporter: Marcus Christie >Assignee: Dimuthu Upeksha >Priority: Major > > See AIRAVATA-2696 for details and pull request that added support to GFac. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2749) Experiment status not updated, but job is COMPLETED and outputs are staged.
[ https://issues.apache.org/jira/browse/AIRAVATA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832643#comment-16832643 ] Dimuthu Upeksha commented on AIRAVATA-2749: --- Fixed in latest improvements. Please reopen if necessary. > Experiment status not updated, but job is COMPLETED and outputs are staged. > --- > > Key: AIRAVATA-2749 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2749 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # Experiment launched and job submitted and completed sucesfully. > # Output files are also staged and available in the gateway portal as well. > # Experiment status not changed to COMPLETED, in EXECUTING > # No errors in the participant or controller logs. > |SLM001-Gaussian-Carbonate_8473f6fc-5d24-4101-84db-1b05c46ba882 > > | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AIRAVATA-2749) Experiment status not updated, but job is COMPLETED and outputs are staged.
[ https://issues.apache.org/jira/browse/AIRAVATA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2749. - Resolution: Fixed > Experiment status not updated, but job is COMPLETED and outputs are staged. > --- > > Key: AIRAVATA-2749 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2749 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # Experiment launched and job submitted and completed sucesfully. > # Output files are also staged and available in the gateway portal as well. > # Experiment status not changed to COMPLETED, in EXECUTING > # No errors in the participant or controller logs. > |SLM001-Gaussian-Carbonate_8473f6fc-5d24-4101-84db-1b05c46ba882 > > | -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AIRAVATA-2955) Helix controller does not get stopped when server is stopped. Had to kill the process to stop the server
[ https://issues.apache.org/jira/browse/AIRAVATA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2955. - Resolution: Fixed > Helix controller does not get stopped when server is stopped. Had to kill the > process to stop the server > > > Key: AIRAVATA-2955 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2955 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > The experiments were not moving forward from EXECUTING, no tasks were > executed and hence no job was submitted. Then the controller was stopped but > when checked the process was running, did not get stopped correctly. > > Then had to do a kill -9 with process ID to stop and started the server. > Why the server needed a restart was not very clear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2955) Helix controller does not get stopped when server is stopped. Had to kill the process to stop the server
[ https://issues.apache.org/jira/browse/AIRAVATA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832639#comment-16832639 ] ASF subversion and git services commented on AIRAVATA-2955: --- Commit 8183162556fcfb1ce81257d60f989d4cbbadd911 in airavata's branch refs/heads/master from Dimuthu Wannipurage [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=8183162 ] Fixing AIRAVATA-2955: Forcefully killing unresponsive processes > Helix controller does not get stopped when server is stopped. Had to kill the > process to stop the server > > > Key: AIRAVATA-2955 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2955 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > The experiments were not moving forward from EXECUTING, no tasks were > executed and hence no job was submitted. Then the controller was stopped but > when checked the process was running, did not get stopped correctly. > > Then had to do a kill -9 with process ID to stop and started the server. > Why the server needed a restart was not very clear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2955) Helix controller does not get stopped when server is stopped. Had to kill the process to stop the server
[ https://issues.apache.org/jira/browse/AIRAVATA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832641#comment-16832641 ] Dimuthu Upeksha commented on AIRAVATA-2955: --- Fixed in [https://github.com/apache/airavata/commit/8183162556fcfb1ce81257d60f989d4cbbadd911] > Helix controller does not get stopped when server is stopped. Had to kill the > process to stop the server > > > Key: AIRAVATA-2955 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2955 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > The experiments were not moving forward from EXECUTING, no tasks were > executed and hence no job was submitted. Then the controller was stopped but > when checked the process was running, did not get stopped correctly. > > Then had to do a kill -9 with process ID to stop and started the server. > Why the server needed a restart was not very clear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (AIRAVATA-3022) When an experiment is launched twice (user clicks Launch button twice) the experiment is tagged as FAILED where as the job submission proceeds.
[ https://issues.apache.org/jira/browse/AIRAVATA-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-3022. - Resolution: Fixed > When an experiment is launched twice (user clicks Launch button twice) the > experiment is tagged as FAILED where as the job submission proceeds. > --- > > Key: AIRAVATA-3022 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3022 > Project: Airavata > Issue Type: Bug > Components: Airavata API, PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: seagrid.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # User clones an experiment and launches it using the Launch button. The user > clicks on the Launch button again which tries to launch the already launched > experiment again, > # This scenario is currently handled by tagging the experiment with FAILED. > # What is required is graceful handling of the situation and not to tag the > already launched experiment as FAILED, but to leave it in LAUNCHED > # Although the experiment is tagged as FAILED at the second LAUNCH attempt, > the job has got submitted since the experiment was already LAUNCHED. > # The errors in the api log > # 2019-04-17 14:40:55,414 [pool-9-thread-93] ERROR > o.a.thrift.ProcessFunction - Internal error processing updateExperiment > org.apache.airavata.model.error.AiravataSystemException: Error while updating > experiment. Update experiment is only valid for experiments with status > CREATED, VALIDATED, CANCELLED, FAILED and UNKNOWN. Make sure the given > experiment is in one of above statuses... > at > org.apache.airavata.registry.api.service.handler.RegistryServerHandler.updateExperiment(RegistryServerHandler.java:3159) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12745) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12729) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > 2019-04-17 14:40:55,414 [pool-24-thread-51] ERROR > o.a.a.a.s.h.AiravataServerHandler - > Clone_of_Pinacyanol_3472ac7b-1900-4ed6-95e4-7f7443d65701 > org.apache.thrift.TApplicationException: Internal error processing > updateExperiment > at > org.apache.thrift.TApplicationException.read(TApplicationException.java:111) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79) > at > org.apache.airavata.registry.api.RegistryService$Client.recv_updateExperiment(RegistryService.java:3577) > at > org.apache.airavata.registry.api.RegistryService$Client.updateExperiment(RegistryService.java:3563) > at > org.apache.airavata.api.server.handler.AiravataServerHandler.updateExperiment(AiravataServerHandler.java:1568) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.CGLIB$updateExperiment$144() > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04$$FastClassByGuice$$85becf93.invoke() > at > com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > org.apache.airavata.service.security.interceptor.SecurityInterceptor.invoke(SecurityInterceptor.java:57) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:55) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.updateExperiment() > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17637) > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17621) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) > at >
[jira] [Commented] (AIRAVATA-3022) When an experiment is launched twice (user clicks Launch button twice) the experiment is tagged as FAILED where as the job submission proceeds.
[ https://issues.apache.org/jira/browse/AIRAVATA-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832591#comment-16832591 ] Dimuthu Upeksha commented on AIRAVATA-3022: --- Fixed in [https://github.com/apache/airavata/commit/88b8047b2dca73fea3b01bfc01f642537f15f1cc] > When an experiment is launched twice (user clicks Launch button twice) the > experiment is tagged as FAILED where as the job submission proceeds. > --- > > Key: AIRAVATA-3022 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3022 > Project: Airavata > Issue Type: Bug > Components: Airavata API, PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: seagrid.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # User clones an experiment and launches it using the Launch button. The user > clicks on the Launch button again which tries to launch the already launched > experiment again, > # This scenario is currently handled by tagging the experiment with FAILED. > # What is required is graceful handling of the situation and not to tag the > already launched experiment as FAILED, but to leave it in LAUNCHED > # Although the experiment is tagged as FAILED at the second LAUNCH attempt, > the job has got submitted since the experiment was already LAUNCHED. > # The errors in the api log > # 2019-04-17 14:40:55,414 [pool-9-thread-93] ERROR > o.a.thrift.ProcessFunction - Internal error processing updateExperiment > org.apache.airavata.model.error.AiravataSystemException: Error while updating > experiment. Update experiment is only valid for experiments with status > CREATED, VALIDATED, CANCELLED, FAILED and UNKNOWN. Make sure the given > experiment is in one of above statuses... > at > org.apache.airavata.registry.api.service.handler.RegistryServerHandler.updateExperiment(RegistryServerHandler.java:3159) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12745) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12729) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > 2019-04-17 14:40:55,414 [pool-24-thread-51] ERROR > o.a.a.a.s.h.AiravataServerHandler - > Clone_of_Pinacyanol_3472ac7b-1900-4ed6-95e4-7f7443d65701 > org.apache.thrift.TApplicationException: Internal error processing > updateExperiment > at > org.apache.thrift.TApplicationException.read(TApplicationException.java:111) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79) > at > org.apache.airavata.registry.api.RegistryService$Client.recv_updateExperiment(RegistryService.java:3577) > at > org.apache.airavata.registry.api.RegistryService$Client.updateExperiment(RegistryService.java:3563) > at > org.apache.airavata.api.server.handler.AiravataServerHandler.updateExperiment(AiravataServerHandler.java:1568) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.CGLIB$updateExperiment$144() > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04$$FastClassByGuice$$85becf93.invoke() > at > com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > org.apache.airavata.service.security.interceptor.SecurityInterceptor.invoke(SecurityInterceptor.java:57) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:55) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.updateExperiment() > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17637) > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17621) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at >
[jira] [Commented] (AIRAVATA-3022) When an experiment is launched twice (user clicks Launch button twice) the experiment is tagged as FAILED where as the job submission proceeds.
[ https://issues.apache.org/jira/browse/AIRAVATA-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832584#comment-16832584 ] ASF subversion and git services commented on AIRAVATA-3022: --- Commit 88b8047b2dca73fea3b01bfc01f642537f15f1cc in airavata's branch refs/heads/master from Dimuthu Wannipurage [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=88b8047 ] Fixing AIRAVATA-3022: Gracefully handling multiple launch requests > When an experiment is launched twice (user clicks Launch button twice) the > experiment is tagged as FAILED where as the job submission proceeds. > --- > > Key: AIRAVATA-3022 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3022 > Project: Airavata > Issue Type: Bug > Components: Airavata API, PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: seagrid.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # User clones an experiment and launches it using the Launch button. The user > clicks on the Launch button again which tries to launch the already launched > experiment again, > # This scenario is currently handled by tagging the experiment with FAILED. > # What is required is graceful handling of the situation and not to tag the > already launched experiment as FAILED, but to leave it in LAUNCHED > # Although the experiment is tagged as FAILED at the second LAUNCH attempt, > the job has got submitted since the experiment was already LAUNCHED. > # The errors in the api log > # 2019-04-17 14:40:55,414 [pool-9-thread-93] ERROR > o.a.thrift.ProcessFunction - Internal error processing updateExperiment > org.apache.airavata.model.error.AiravataSystemException: Error while updating > experiment. Update experiment is only valid for experiments with status > CREATED, VALIDATED, CANCELLED, FAILED and UNKNOWN. Make sure the given > experiment is in one of above statuses... > at > org.apache.airavata.registry.api.service.handler.RegistryServerHandler.updateExperiment(RegistryServerHandler.java:3159) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12745) > at > org.apache.airavata.registry.api.RegistryService$Processor$updateExperiment.getResult(RegistryService.java:12729) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > 2019-04-17 14:40:55,414 [pool-24-thread-51] ERROR > o.a.a.a.s.h.AiravataServerHandler - > Clone_of_Pinacyanol_3472ac7b-1900-4ed6-95e4-7f7443d65701 > org.apache.thrift.TApplicationException: Internal error processing > updateExperiment > at > org.apache.thrift.TApplicationException.read(TApplicationException.java:111) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79) > at > org.apache.airavata.registry.api.RegistryService$Client.recv_updateExperiment(RegistryService.java:3577) > at > org.apache.airavata.registry.api.RegistryService$Client.updateExperiment(RegistryService.java:3563) > at > org.apache.airavata.api.server.handler.AiravataServerHandler.updateExperiment(AiravataServerHandler.java:1568) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.CGLIB$updateExperiment$144() > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04$$FastClassByGuice$$85becf93.invoke() > at > com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > org.apache.airavata.service.security.interceptor.SecurityInterceptor.invoke(SecurityInterceptor.java:57) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:55) > at > org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$a6c02c04.updateExperiment() > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17637) > at > org.apache.airavata.api.Airavata$Processor$updateExperiment.getResult(Airavata.java:17621) > at
