Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Tue, 4 Dec 2012 11:12:58 +0000 (UTC)
From: "Marcel Offermans (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <52719129.58391.1354619578666.JavaMail.jiratomcat@arcas>
In-Reply-To: <1748849719.39816.1354194779157.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (ACE-307) Misleading error when deployment fails
 due to OBR directory being out-of-sync
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcel Offermans resolved ACE-307.
----------------------------------

    Resolution: Fixed

Applied the patch.
                
> Misleading error when deployment fails due to OBR directory being out-of-sync
> -----------------------------------------------------------------------------
>
>                 Key: ACE-307
>                 URL: https://issues.apache.org/jira/browse/ACE-307
>             Project: ACE
>          Issue Type: Bug
>            Reporter: Tuomas Kiviaho
>            Assignee: Marcel Offermans
>
> I was getting a mysterious error when I manipulated store directory makes up the OBR
> {{noformat}}
> ERROR - Bundle: org.apache.ace.deployment.task - Error accessing resources - java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8082/deployment/org.example/versions/1.0.0
>         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
>         at org.apache.ace.deployment.service.impl.DeploymentServiceImpl.getContents(DeploymentServiceImpl.java:298)
>         at org.apache.ace.deployment.service.impl.DeploymentServiceImpl.installVersion(DeploymentServiceImpl.java:114)
>         at org.apache.ace.deployment.task.DeploymentUpdateTask.run(DeploymentUpdateTask.java:57)
>         at org.apache.ace.scheduler.Executer.run(Executer.java:92)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> {{noformat}}
> I had to plugin the debugger to figure this one out because the error code was a bit misleading (should have been 500). I managed to figure out that RepositoryBasedProvider was serving outdated urls to StreamGenerator which in turn gave out FileNotFounldException. Then the DeploymentServlet replaced the original exception without passing forward the original cause.

--
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: http://www.atlassian.com/software/jira