Bram de Kruijff resolved Bug AMDATUMNGMNT-14 as Won't Fix

First, please try and report concise issues of exact use cases and reproduction paths. It wont hurt you to do a little analysis and drill down to the issue before posting "it doesn't work". It really takes a lot of time and effort for us to diagnose your problems like this.

Having said so, it took a quick look and ran your populator against AMS 1.0.0-RC2 with the same result. Some observations:

1) Already on import a lot of errors show up in the AMS log

2012.05.23 18:33:10 WARNING - Bundle: org.apache.ace.client.rest - Failed to add entity of type: artifact - java.lang.IllegalArgumentException: Failed to add new object: entity already exists!
        at org.apache.ace.client.repository.impl.ObjectRepositoryImpl.create(ObjectRepositoryImpl.java:83)
        at org.apache.ace.client.rest.Workspace.addRepositoryObject(Workspace.java:252)
        at org.apache.ace.client.rest.RESTClientServlet.createRepositoryObject(RESTClientServlet.java:392)
        at org.apache.ace.client.rest.RESTClientServlet.doPost(RESTClientServlet.java:333)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.amdatu.web.dispatcher.handler.ServletHandler.handle(ServletHandler.java:89)
        at org.amdatu.web.dispatcher.dispatch.CustomFilterChain.doFilter(CustomFilterChain.java:56)
        at org.amdatu.web.dispatcher.dispatch.CustomFilterPipeline.dispatch(CustomFilterPipeline.java:59)
        at org.amdatu.web.dispatcher.dispatch.ExtenderFilterChain.doFilter(ExtenderFilterChain.java:53)
        at org.amdatu.web.dispatcher.dispatch.ExtenderFilterPipeline.dispatch(ExtenderFilterPipeline.java:44)
        at org.amdatu.web.dispatcher.service.DispatcherServiceImpl.dispatchRequest(DispatcherServiceImpl.java:203)
        at org.amdatu.web.dispatcher.filter.DispatchInterceptFilter.doFilter(DispatchInterceptFilter.java:68)
        at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:80)
        at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:68)
        at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
        at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
        at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
        at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
        at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

2) Your "core" feature looks shady

Why are you provisioning the managementagent to the management agent? Also fileinstall bundles are questionable.

3) Drilldown shows config files to blame

When reducing the problem to just the core feature and subsequently disconnecting the core config artifact. The agent start updating. Reconnecting the config to the feature shows the real issue.

2012.05.23 18:39:17 WARNING - Bundle: org.apache.ace.client.repository.impl - [org.apache.ace.client.repository.stateful.StatefulTargetRepository, org.osgi.service.event.EventHandler] - EventAdmin: Exception during event dispatch [org.osgi.
service.event.Event [topic=org/apache/ace/client/repository/public/Artifact2FeatureAssociation/ADDED] | [org.apache.ace.client.repository.stateful.StatefulTargetRepository, org.osgi.service.event.EventHandler] | Bundle(org.apache.ace.client
.repository.impl [26])] - java.lang.IllegalArgumentException: Neither the key nor the value should be null.
        at org.apache.ace.client.repository.impl.DeploymentArtifactImpl.addDirective(DeploymentArtifactImpl.java:98)
        at org.apache.ace.client.repository.impl.DeploymentVersionRepositoryImpl.createDeploymentArtifact(DeploymentVersionRepositoryImpl.java:119)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetRepositoryImpl.getNecessaryDeploymentArtifacts(StatefulTargetRepositoryImpl.java:582)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetRepositoryImpl.generateDeploymentVersion(StatefulTargetRepositoryImpl.java:665)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetRepositoryImpl.approve(StatefulTargetRepositoryImpl.java:478)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.approve(StatefulTargetObjectImpl.java:79)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.handleStatechangeAutomation(StatefulTargetObjectImpl.java:386)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.setStatus(StatefulTargetObjectImpl.java:377)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.setStoreState(StatefulTargetObjectImpl.java:367)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.determineStoreState(StatefulTargetObjectImpl.java:254)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetObjectImpl.determineStatus(StatefulTargetObjectImpl.java:223)
        at org.apache.ace.client.repository.stateful.impl.StatefulTargetRepositoryImpl.handleEvent(StatefulTargetRepositoryImpl.java:748)
        at org.apache.felix.eventadmin.impl.tasks.HandlerTaskImpl.execute(HandlerTaskImpl.java:87)
        at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:211)
        at org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:110)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:722)

4) Export shows config artifacts missing resourceProcessorPID

An export of the model you created looks like this

{
        "definition": "artifact-filename-amdatu-core-config.xml",
        "attributes": {
          "artifactName": "config amdatu-core-config",
          "mimetype": "application/xml:osgi-autoconf",
          "filename": "amdatu-core-config.xml",
          "url": "file:/C:/bramk/Amdatu/ivol/demo-ams-population-%20AMDATUMNGMNT-14/features/core/amdatu-core-config.xml"
        },
        "tags": {}
      },

and should look like...

{
        "attributes": {
          "artifactName": "amdatu-auth-node1.xml",
          "mimetype": "application/xml:osgi-autoconf",
          "filename": "amdatu-auth-node1.xml",
          "url": "file:///C:/bramk/Amdatu/ApacheConNA2011/conf/amdatu-auth-node1.xml",
          "artifactDescription": "",
          "processorPid": "org.osgi.deployment.rp.autoconf"
        },
        "tags": {
          "feature": "node1"
        }

Conclusion, you are creating the config artifact incorrectly or maybe you've spotted a bug in the client. Also ideas about better validation and feedback at specific points come to mind.

Change By: Bram de Kruijff (23/May/12 6:48 PM)
Status: Open Resolved
Assignee: Bram de Kruijff Ivo Ladage - van Doorn
Resolution: Won't Fix
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
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to