ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <>
Subject [jira] [Updated] (AMBARI-2024) Ambari Server becomes unresponsive after crashing on http reads on jersey.
Date Thu, 25 Apr 2013 19:42:15 GMT


Siddharth Wagle updated AMBARI-2024:

    Attachment: AMBARI-2024.patch
> Ambari Server becomes unresponsive after crashing on http reads on jersey.
> --------------------------------------------------------------------------
>                 Key: AMBARI-2024
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>         Attachments: AMBARI-2024.patch
> SEVERE: The exception contained within MappableContainerException could not be mapped
to a response, re-throwing to the HTTP container
> early EOF
>         at
>         at org.codehaus.jackson.impl.ByteSourceBootstrapper.ensureLoaded(
>         at org.codehaus.jackson.impl.ByteSourceBootstrapper.detectEncoding(
>         at org.codehaus.jackson.impl.ByteSourceBootstrapper.constructParser(
>         at org.codehaus.jackson.JsonFactory._createJsonParser(
>         at org.codehaus.jackson.JsonFactory.createJsonParser(
>         at org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(
>         at com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy.readFrom(
>         at com.sun.jersey.spi.container.ContainerRequest.getEntity(
> Notice the API's is being called all the time - meaning they probalby had a browser up
and running for a long time.
> There might be a possibilility that the browser might have some issues after running
for a long time. Something to keep in mind when this happens again. Easy way to check that
is to call AMbari server API's and also bring up a new browser window (new instance) and try
hitting the browser UI.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message