[
https://issues.apache.org/jira/browse/AIRAVATA-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947165#comment-15947165
]
Marcus Christie commented on AIRAVATA-2352:
-------------------------------------------
I'll also add that I think this happened with GFac the other day too. It wasn't
picking up process_launch messages until we restarted it.
Point is, this is probably not an Orchestator specific problem and any solution
developed hopefully can be applied to all Airavata RabbitMQ subscribers.
> Orchestrator sometimes stops processing messages from experiment_launch queue
> -----------------------------------------------------------------------------
>
> Key: AIRAVATA-2352
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2352
> Project: Airavata
> Issue Type: Bug
> Affects Versions: 0.17
> Reporter: Marcus Christie
> Priority: Critical
>
> This was observed on 3/29 9am for gw153.iu.xsede.org.
> *Workaround*: restart the api-orch server. Once that is done the orchestrator
> starts picking up events from experiment_launch again.
> I'm not seeing anything in the logs to indicate why the orchestrator stopped
> processing experiment_launch events.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
