falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FALCON-2266) Non-intuitive response while registering/unregistering/submitting extension via server
Date Wed, 01 Feb 2017 09:32:52 GMT

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

Pallavi Rao resolved FALCON-2266.
---------------------------------
       Resolution: Fixed
    Fix Version/s: trunk

> Non-intuitive response while registering/unregistering/submitting extension via server
> --------------------------------------------------------------------------------------
>
>                 Key: FALCON-2266
>                 URL: https://issues.apache.org/jira/browse/FALCON-2266
>             Project: Falcon
>          Issue Type: Bug
>          Components: extensions
>    Affects Versions: trunk
>            Reporter: Pragya Mittal
>            Assignee: Pracheer Agarwal
>             Fix For: trunk
>
>
> Registering extension via server throws the following error 
> {noformat}
> pragya.mittal@falcon1001:/mnt/falcon/server/bin$ ./falcon extension -register -extensionName
extension-example-1 -path hdfs://192.168.138.236:8020/tmp/extensions/extension-example
> Hadoop is installed, adding hadoop classpath to falcon classpath
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/mnt/falcon/server/client/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/usr/hdp/2.2.4.2-2/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Jan 31, 2017 7:12:57 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
> Jan 31, 2017 7:12:57 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.MimeMultipartProvider
>   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
>   com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Not Found;<html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
> <title>Error 404 Not Found</title>
> </head>
> <body><h2>HTTP ERROR 404</h2>
> <p>Problem accessing /api/extension/register/extension-example-1. Reason:
> <pre>    Not Found</pre></p><hr /><i><small>Powered
by Jetty://</small></i><br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> <br/>
> </body>
> </html>
> {noformat}
> It should say operation not permitted instead of showing the full stack trace which is
non intuitive in nature.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message