falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shwetha GS <shwetha...@inmobi.com>
Subject Re: Not able to start falcon in distributed mode
Date Sat, 28 Sep 2013 14:01:32 GMT
Do you see any error in logs/application.log?



> On 27-Sep-2013, at 11:08 pm, Raghav Kumar Gautam <raghavgautam@gmail.com> wrote:
>
> I am starting out with falcon's distributed mode. I am using the falcon's
> master branch and am getting the following error (this was working with
> 0.3-incubating).
>
> bin/falcon entity -type cluster -submit -file ~/primary-cluster.xml
> Sep 27, 2013 10:25:34 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Sep 27, 2013 10:25:34 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.APIResult,
> and Java type class org.apache.falcon.resource.APIResult, and MIME media
> type text/html; charset=iso-8859-1 was not found
>
>
>
> Jetty is actually up at 15000 (telent connects).
> Content of logs/falcon.out.2013092710241380302689:
>
> nohup: appending output to `nohup.out'
> Sep 27, 2013 10:24:54 AM
> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17
> PM'
> Sep 27, 2013 10:24:55 AM
> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.8 06/24/2011 12:17
> PM'
>
> I am following steps from
> http://falcon.incubator.apache.org/docs/InstallationSteps.html. Am I
> missing something ?
>
> Thanks,
> Raghav.

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Mime
View raw message