Return-Path: Delivered-To: apmail-incubator-ace-dev-archive@minotaur.apache.org Received: (qmail 66581 invoked from network); 8 Nov 2010 20:49:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Nov 2010 20:49:02 -0000 Received: (qmail 74194 invoked by uid 500); 8 Nov 2010 20:49:34 -0000 Delivered-To: apmail-incubator-ace-dev-archive@incubator.apache.org Received: (qmail 74140 invoked by uid 500); 8 Nov 2010 20:49:33 -0000 Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ace-dev@incubator.apache.org Delivered-To: mailing list ace-dev@incubator.apache.org Received: (qmail 74132 invoked by uid 99); 8 Nov 2010 20:49:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 20:49:33 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of karlpauls@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-wy0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 20:49:26 +0000 Received: by wye20 with SMTP id 20so216884wye.6 for ; Mon, 08 Nov 2010 12:49:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=pmSb+zIFDsjwuHMk+ze1/wOXURhQAQN8j4lu5MRLATA=; b=UPgprnhWWrNgknJWXzuMbiuhdx+FaMszbBxdewPD4SKupGeF7oiSKzv3bvTFZF3A6l EX/zpAUw3JNqUclcHBqFyHi3ixsvLxJWjfuhKhoUTT5YLh1BKT0vm65IUxGWA4wgQb1c IyP2Y68/d0Htr1DYOfDXNaC8ciRIdXeWDWndA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=JNhriJyzOMqXonR1lAgfAfYFe4nAJ2DJ5hLnX1Bnwh9FaWOcQgaNExS3GGIQdvywf0 ZO3DXDosQXmOI7sAJqtOUD1hvVZP6L1JezfNMp80ySfJgKN0U8Ad7Se4/qcbPM8C+NI1 mIYhxLHk++iSSyAuwJGN2sU43QfBPXcdM9CJU= MIME-Version: 1.0 Received: by 10.227.141.201 with SMTP id n9mr5797177wbu.185.1289249345439; Mon, 08 Nov 2010 12:49:05 -0800 (PST) Received: by 10.216.64.68 with HTTP; Mon, 8 Nov 2010 12:49:05 -0800 (PST) In-Reply-To: <9C8F4F13-B3E0-4CDA-B485-F605975530DF@luminis.eu> References: <0AE91550-9F80-4DDD-A627-8690AD48A47B@luminis.eu> <9C8F4F13-B3E0-4CDA-B485-F605975530DF@luminis.eu> Date: Mon, 8 Nov 2010 21:49:05 +0100 Message-ID: Subject: Re: Gateway error when updating From: Karl Pauls To: ace-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org R3 doesn't require a symbolic-name. It was added in R4. regards, Karl On Mon, Nov 8, 2010 at 9:45 PM, Angelo van der Sijpt wrote: > Okay, good to hear you got it to work. The symbolic name is a required pr= operty for R4 bundles, I'm not sure for R3. Was it your intention to deploy= an R3 bundle? > > In the Deployment Admin specification (compendium 4.2, 114.3.4.7), we fin= d > "If the bundle resource has no Bundle-SymbolicName header, the given symb= olic name must be used to calculate the location of the bundle." > So, I agree that this is a bug in deployment admin. Can you file a bug wi= th Deployment Admin in the Felix project? > > I don't understand what you mean by 'uncommit' a distribution; do you mea= n removing _all_ bundles from the gateway? > > Angelo > > > On Nov 8, 2010, at 9:06 PM, Stephen Brady wrote: > >> I've figured out an immediate fix and maybe revealed a bug (don't know >> enough about ACE to call it a bug). =A0It seems it's failing at line 115= at >> org.apache.felix.deploymentadmin.abstractdeploymentpackage.getBundle >> because it's not gracefully handling null symbolic names. =A0I've filter= ed out >> the nulls, which at least allowed me to get ACE working. =A0I don't know >> Felix-ACE internals well enough to understand whether this fix is >> sustainable/reliable. =A0For example, not sure what happens if a given b= undle >> added to the repository has an improper manifest with no symbolic name. >> Perhaps someone can root cause what's going on here? =A0Does getBundle n= eed >> to handle these nulls more gracefully or should it not be getting any nu= lls >> to begin with further upstream? >> >> Angelo, to answer your questions. =A0What you see with the first six >> deployments in that readout is just earlier attempts to push different >> distributions. =A0When I would try and commit a new distribution, the Ga= teway >> would fail to pull down the associated bundles (the stack trace I sent >> earlier). =A0I would then "uncommit" that distribution, upping the versi= on >> number again, and the Gateway would then readout OK since no bundles nee= ded >> to be pulled down. >> >> >> >> On Fri, Nov 5, 2010 at 7:28 AM, Angelo van der Sijpt < >> angelo.vandersijpt@luminis.eu> wrote: >> >>> Hi Stephen, >>> >>> Without knowing what exactly runs in your framework, it's a bit hard to >>> know what exactly is happening. Still, it should be very well possible = to >>> use your own framework, and drop the right bundles and configuration in= to >>> it. >>> >>> Could you give a little more info on what you're doing? For instance, h= ow >>> were you possible to make the first six deployments? Have you included >>> specific new bundles in your latest deployment? >>> >>> Angelo >>> >>> >>> On Nov 4, 2010, at 11:02 PM, Stephen Brady wrote: >>> >>>> I get the following stack trace on the Gateway after committing a chan= ge >>> on >>>> the Server webui. >>>> >>>> Stepping back, I'm trying to deploy the Gateway bundles in my own Feli= x >>>> 2.0.5-based osgi framework (which is closely modeled off of Intalio's >>> Jetty >>>> embedded in Felix distro). =A0I've had no problems running the ACE gat= eway >>>> going the pax route. =A0However, I'm not terribly familiar with pax, s= o I'm >>>> not 100% clear what kind of setup/config it's doing. =A0But as far as = I can >>>> tell, I've made the appropriate configuration additions/changes in my >>> osgi >>>> framework to handle the ACE gateway so I'm at a loss now. >>>> >>>> Thanks for the help! =A0This is a great project. >>>> >>>> >>>> [Info ] [ =A0 ] Highest remote: 7.0.0 / Highest local: 6.0.0 >>>> [Info ] [ =A0 ] Installing version: 7.0.0 >>>> [Error] [ =A0 ] Error installing update >>>> java.lang.NullPointerException >>>> =A0 =A0 =A0 at >>>> >>> org.apache.felix.deploymentadmin.AbstractDeploymentPackage.getBundle(Ab= stractDeploymentPackage.java:115) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.felix.deploymentadmin.spi.UpdateCommand.execute(UpdateComman= d.java:70) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.felix.deploymentadmin.spi.DeploymentSessionImpl.call(Deploym= entSessionImpl.java:74) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.felix.deploymentadmin.DeploymentAdminImpl.installDeploymentP= ackage(DeploymentAdminImpl.java:215) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.ace.deployment.deploymentadmin.DeploymentAdminDeployer.insta= ll(DeploymentAdminDeployer.java:51) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.ace.deployment.task.DeploymentTaskBase.installVersion(Deploy= mentTaskBase.java:75) >>>> =A0 =A0 =A0 at >>>> >>> org.apache.ace.deployment.task.DeploymentUpdateTask.run(DeploymentUpdat= eTask.java:57) >>>> =A0 =A0 =A0 at org.apache.ace.scheduler.Executer.run(Executer.java:92) >>>> =A0 =A0 =A0 at java.util.TimerThread.mainLoop(Unknown Source) >>>> =A0 =A0 =A0 at java.util.TimerThread.run(Unknown Source) >>> >>> > > --=20 Karl Pauls karlpauls@gmail.com