[
https://issues.apache.org/jira/browse/AIRAVATA-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-3510:
--------------------------------------
Description:
We get several spurious error emails relating to failure to load an application
interface. This sort of error email message is typical:
{code}
AiravataSystemException
AiravataSystemException(airavataErrorType=2, message='Error while retrieving
application interface. More info : getApplicationInterface failed: unknown
result')
Django Version: 2.2.23
Exception Type: AiravataSystemException
Exception Value:
AiravataSystemException(airavataErrorType=2, message='Error while retrieving
application interface. More info : getApplicationInterface failed: unknown
result')
Exception Location:
/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/airavata/api/Airavata.py
in recv_getApplicationInterface, line 7247
Python Executable: /var/www/portals/django-seagrid/venv/bin/python
Python Version: 3.6.8
Python Path:
['/usr/lib64/python36.zip',
'/usr/lib64/python3.6',
'/usr/lib64/python3.6/lib-dynload',
'/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages',
'/var/www/portals/django-seagrid/airavata-django-portal',
'/var/www/portals/django-seagrid/venv/lib/python3.6/site-packages',
'/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/IPython/extensions']
Server time: Tue, 14 Sep 2021 13:34:38 +0000
{code}
This is because the application no longer exists but an experiment still
references it. The REST API and error messaging could be cleaned up by first
checking if the interface exists and then returning a proper 404 when an
interface no longer exists.
was:
We get several spurious error emails relating to failure to load an application
interface. This sort of error email message is typical:
```
AiravataSystemException
AiravataSystemException(airavataErrorType=2, message='Error while retrieving
application interface. More info : getApplicationInterface failed: unknown
result')
Django Version: 2.2.23
Exception Type: AiravataSystemException
Exception Value:
AiravataSystemException(airavataErrorType=2, message='Error while retrieving
application interface. More info : getApplicationInterface failed: unknown
result')
Exception Location:
/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/airavata/api/Airavata.py
in recv_getApplicationInterface, line 7247
Python Executable: /var/www/portals/django-seagrid/venv/bin/python
Python Version: 3.6.8
Python Path:
['/usr/lib64/python36.zip',
'/usr/lib64/python3.6',
'/usr/lib64/python3.6/lib-dynload',
'/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages',
'/var/www/portals/django-seagrid/airavata-django-portal',
'/var/www/portals/django-seagrid/venv/lib/python3.6/site-packages',
'/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/IPython/extensions']
Server time: Tue, 14 Sep 2021 13:34:38 +0000
```
This is because the application no longer exists but an experiment still
references it. The REST API and error messaging could be cleaned up by first
checking if the interface exists and then returning a proper 404 when an
interface no longer exists.
> Django REST API: return a 404 when unable to load application interface
> because it doesn't exist
> ------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-3510
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3510
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> We get several spurious error emails relating to failure to load an
> application interface. This sort of error email message is typical:
> {code}
> AiravataSystemException
> AiravataSystemException(airavataErrorType=2, message='Error while retrieving
> application interface. More info : getApplicationInterface failed: unknown
> result')
> Django Version: 2.2.23
> Exception Type: AiravataSystemException
> Exception Value:
> AiravataSystemException(airavataErrorType=2, message='Error while retrieving
> application interface. More info : getApplicationInterface failed: unknown
> result')
> Exception Location:
> /var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/airavata/api/Airavata.py
> in recv_getApplicationInterface, line 7247
> Python Executable: /var/www/portals/django-seagrid/venv/bin/python
> Python Version: 3.6.8
> Python Path:
> ['/usr/lib64/python36.zip',
> '/usr/lib64/python3.6',
> '/usr/lib64/python3.6/lib-dynload',
> '/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages',
> '/var/www/portals/django-seagrid/airavata-django-portal',
> '/var/www/portals/django-seagrid/venv/lib/python3.6/site-packages',
>
> '/var/www/portals/django-seagrid/venv/lib64/python3.6/site-packages/IPython/extensions']
> Server time: Tue, 14 Sep 2021 13:34:38 +0000
> {code}
> This is because the application no longer exists but an experiment still
> references it. The REST API and error messaging could be cleaned up by first
> checking if the interface exists and then returning a proper 404 when an
> interface no longer exists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
