airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2374) Create init scripts for airavata servers
Date Thu, 21 Feb 2019 22:06:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774538#comment-16774538
] 

Marcus Christie commented on AIRAVATA-2374:
-------------------------------------------

RegisterAPIServer fails to start with this error when RabbitMQ is down on startup:
{noformat}
2019-02-21 16:26:09,707 [Thread-4] ERROR o.a.a.r.a.s.RegistryAPIServer  - Failed to start
database event handlers, reason: RabbitMQ connection issue for exchange : db.event.exchange
org.apache.airavata.common.exception.AiravataException: RabbitMQ connection issue for exchange
: db.event.exchange
        at org.apache.airavata.messaging.core.impl.RabbitMQPublisher.connect(RabbitMQPublisher.java:74)
        at org.apache.airavata.messaging.core.impl.RabbitMQPublisher.<init>(RabbitMQPublisher.java:57)
        at org.apache.airavata.messaging.core.MessagingFactory.getDBEventPublisher(MessagingFactory.java:109)
        at org.apache.airavata.registry.api.service.messaging.RegistryServiceDBEventMessagingFactory.getDBEventPublisher(RegistryServiceDBEventMessagingFactory.java:57)
        at org.apache.airavata.registry.api.service.messaging.RegistryServiceDBEventMessagingFactory.registerRegistryServiceWithPublishers(RegistryServiceDBEventMessagingFactory.java:90)
        at org.apache.airavata.registry.api.service.RegistryAPIServer.startDatabaseEventHandlers(RegistryAPIServer.java:127)
        at org.apache.airavata.registry.api.service.RegistryAPIServer.access$300(RegistryAPIServer.java:45)
        at org.apache.airavata.registry.api.service.RegistryAPIServer$2.run(RegistryAPIServer.java:109)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at com.rabbitmq.client.impl.FrameHandlerFactory.create(FrameHandlerFactory.java:32)
        at com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:34)
        at com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:83)
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:595)
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:625)
        at org.apache.airavata.messaging.core.impl.RabbitMQPublisher.connect(RabbitMQPublisher.java:65)
        ... 7 common frames omitted
{noformat}

I think it would be better if RegistryAPIServer just waited until it can connect to RabbitMQ
before starting.

Also note that ServerMain justs waits forever for the RegisterAPIServer to start.

> Create init scripts for airavata servers
> ----------------------------------------
>
>                 Key: AIRAVATA-2374
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2374
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>             Fix For: 0.18
>
>




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

Mime
View raw message