[
https://issues.apache.org/jira/browse/AMBARI-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203568#comment-14203568
]
Hadoop QA commented on AMBARI-8230:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680410/AMBARI-8230.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/565//console
This message is automatically generated.
> Error in persisting web client state at ambari server: Error 500 !hex:5c
> ------------------------------------------------------------------------
>
> Key: AMBARI-8230
> URL: https://issues.apache.org/jira/browse/AMBARI-8230
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8230.patch, AMBARI-8230_branch-1.7.0.patch
>
>
> I left my browser window up after cluster install was complete.
> When I clicked on "Complete" button to exit Install wizard, this error popped
> up.
> I believe this happened because the browser passed to the server a previously
> invalid HTTP session ID and the server responded with 500 (it would have
> responded with 403).
> It could be that there's a server-side/jetty bug when receiving a request
> with a session that it knew about but has been invalidated; I don't think
> this error happens if you restart ambari-server to wipe out the history of
> HTTP sessions but need to verify.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
