ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <>
Subject [jira] [Created] (ACE-168) Check version validity before publishing to targets
Date Tue, 23 Aug 2011 17:18:29 GMT
Check version validity before publishing to targets

                 Key: ACE-168
             Project: Ace
          Issue Type: Improvement
    Affects Versions: 1.0.0
            Reporter: Bram de Kruijff

There is no sanity checking on artifacts (at least url) before publishing versions to targets.
Simple case is an artifact with an url that is not accessible. This will result in any target
it is associated to recieving a new version, polling for the deploymentpackage and getting
an error (DeploymentServlet catches the IOException) for ever and ever and ever.

I think URL attributes should at least be validated at creation and some way to prevent this
endless fail cycle on every thread that handles deployment package requests affecting all
targets would be nice. 

typical auditlog sample:

typical client log sample:
[2011-08-23 19:16:20] ERROR: Error installing update [org.apache.felix.framework]
org.osgi.service.deploymentadmin.DeploymentException: null
org.apache.felix.log.LogException: org.osgi.service.deploymentadmin.DeploymentException: null
        at org.apache.felix.deploymentadmin.DeploymentPackageManifest.<init>(
        at org.apache.felix.deploymentadmin.AbstractDeploymentPackage.<init>(
        at org.apache.felix.deploymentadmin.StreamDeploymentPackage.<init>(
        at org.apache.felix.deploymentadmin.DeploymentAdminImpl.installDeploymentPackage(
        at org.apache.ace.deployment.deploymentadmin.DeploymentAdminDeployer.install(
        at org.apache.ace.deployment.task.DeploymentTaskBase.installVersion(
        at java.util.TimerThread.mainLoop(

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message