falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Assigned] (FALCON-248) Improve the error message when falcon is not fully operational
Date Thu, 09 Jan 2014 06:56:07 GMT

     [ https://issues.apache.org/jira/browse/FALCON-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Baptiste Onofré reassigned FALCON-248:
-------------------------------------------

    Assignee: Jean-Baptiste Onofré

> Improve the error message when falcon is not fully operational
> --------------------------------------------------------------
>
>                 Key: FALCON-248
>                 URL: https://issues.apache.org/jira/browse/FALCON-248
>             Project: Falcon
>          Issue Type: Improvement
>          Components: general
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Using an external ActiveMQ (with export FALCON_OPTS="-Dfalcon.embeddedmq=false" in conf/falcon-env.sh),
when the ActiveMQ broker is not started, falcon starts fine.
> However, when performing a simple:
> bin/falcon entity -type cluster -list
> we get the following error message:
> Jan 08, 2014 11:52:59 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class org.apache.falcon.resource.EntityList, and
Java type class org.apache.falcon.resource.EntityList, and MIME media type text/html; charset=iso-8859-1
was not found
> Jan 08, 2014 11:52:59 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media type are:
> */* ->
>   com.sun.jersey.core.impl.provider.entity.FormProvider
>   com.sun.jersey.core.impl.provider.entity.StringProvider
>   com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
>   com.sun.jersey.core.impl.provider.entity.FileProvider
>   com.sun.jersey.core.impl.provider.entity.InputStreamProvider
>   com.sun.jersey.core.impl.provider.entity.DataSourceProvider
>   com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
>   com.sun.jersey.core.impl.provider.entity.ReaderProvider
>   com.sun.jersey.core.impl.provider.entity.DocumentProvider
>   com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
>   com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
>   com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
>   com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
>   com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
>   com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
>   com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
>   com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
>   com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
>   com.sun.jersey.core.impl.provider.entity.EntityHolderReader
>   com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
>   com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> Unable to connect to Falcon server, please check if the URL is correct and Falcon server
is up and running
> A message body reader for Java class org.apache.falcon.resource.EntityList, and Java
type class org.apache.falcon.resource.EntityList, and MIME media type text/html; charset=iso-8859-1
was not found
> The logs/falcon.application.log clearly indicates that the ActiveMQ broker is not there,
but it could be helpful to display a simpler and more straight forward message.
> I'm working on it to propose a patch.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message