Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 83BD710D00 for ; Mon, 31 Mar 2014 14:51:20 +0000 (UTC) Received: (qmail 6592 invoked by uid 500); 31 Mar 2014 14:51:17 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 6524 invoked by uid 500); 31 Mar 2014 14:51:16 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 6488 invoked by uid 99); 31 Mar 2014 14:51:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2014 14:51:15 +0000 Date: Mon, 31 Mar 2014 14:51:15 +0000 (UTC) From: "Lahiru Gunathilake (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AIRAVATA-825) Airavata Client error in case workflow scheduling context is not right MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-825. ----------------------------------------- Resolution: Invalid This is an obsolete issue. > Airavata Client error in case workflow scheduling context is not right > ---------------------------------------------------------------------- > > Key: AIRAVATA-825 > URL: https://issues.apache.org/jira/browse/AIRAVATA-825 > Project: Airavata > Issue Type: Bug > Affects Versions: 0.8 > Reporter: Raminderjeet Singh > Assignee: Lahiru Gunathilake > Fix For: 0.12 > > > I am trying to set the hostname to run the application but if the hostname is not correct or registered, there is a null pointer error but the API does not return anything to client and its not possible to report this error to use. We need to improve the error message also. -- This message was sent by Atlassian JIRA (v6.2#6252)