[
https://issues.apache.org/jira/browse/HADOOP-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843044#action_12843044
]
Steve Loughran commented on HADOOP-6624:
----------------------------------------
It may make sense to write the props to a buffer and then include a
content-length header, make it easier for things to detect breakage en-route,
proxy servers playing up, etc, etc.
> Hadoop conf/ servlet is serving up an invalid JSON file
> -------------------------------------------------------
>
> Key: HADOOP-6624
> URL: https://issues.apache.org/jira/browse/HADOOP-6624
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.22.0
> Environment: Suse, Java 6, virtual infrastructure.
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: jtconf.xml
>
>
> Seeing this on a machine hosting both the NN and JT. The NN's conf/ servlet
> works as both XML and JSON, but the JT's conf is only coming back as XML,
> when I ask for JSON I see
> {code}
> {"properties":[
> {code}
> To make sure nothing was interfering I connected to the box, did a direct
> telnet
> {code}
> masterc0-vif0:~ # telnet masterc0-vif0 50030
> Trying 10.144.175.2...
> Connected to masterc0-vif0.
> Escape character is '^]'.
> GET /conf?format=json HTTP/1.0
> HTTP/1.1 200 OK
> Content-Type: text/javascript; charset=utf-8
> Server: Jetty(6.1.14)
> {"properties":[Connection closed by foreign host.
> masterc0-vif0:~ #
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
