airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2335) Deploy 0.17-SNAPSHOT on Jetstream for testing
Date Tue, 07 Mar 2017 19:51:38 GMT


Marcus Christie commented on AIRAVATA-2335:

Sent following email to [~scnakandala]

I’m installing Airavata on Jetstream and ran into a problem when the sharing registry gets
initialized.  I’m getting this exception in the logs

2017-03-06 22:11:43 \[main] ERROR o.a.a.a.s.h.AiravataServerHandler - Error occured while
reading airavata-server proper
org.apache.thrift.TApplicationException: getDomain failed: unknown result
       at org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.recv_getDomain(SharingRegistr
       at org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.getDomain(SharingRegistryServ
       at org.apache.airavata.api.server.handler.AiravataServerHandler.initSharingRegistry(
       at org.apache.airavata.api.server.handler.AiravataServerHandler.<init>(

I think the problem is that the domain default gateway domain doesn’t exist and getDomain
returns null, but Thrift doesn’t support null returning methods. This explains why I get
a thrift exception but there is no logged exception from the sharing registry itself.

The problem starts at this line \[1].

What would be the best way to go about fixing this?  My first thought was to add a method
like ‘doesDomainExist’ to the sharing registry.  Another, probably quicker idea would
be to use getDomains() and check if it is empty or doesn’t contain the default gateway domain.




> Deploy 0.17-SNAPSHOT on Jetstream for testing
> ---------------------------------------------
>                 Key: AIRAVATA-2335
>                 URL:
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
> Use Ansible to deploy Airavata version 0.17-SNAPSHOT for testing before 0.17 is released.

This message was sent by Atlassian JIRA

View raw message