[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Change Request Debugging
- From: Kevin McIntire <kevin.mcintire@xxxxxxxxx>
- Date: Thu, 20 Jan 2011 08:43:50 -0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=skype.net; h=from:content-type :content-transfer-encoding:subject:date:message-id:to: mime-version; q=dns; s=mx; b=IHl2TUatyZQmSfdodB0ZZ9SRCRuhNUw6587 Os31PNY1pHXovvNAugvqvrL3c/I5ZXXPksnhPA5mSf3XX9sHybO4iCQlYtUQ1nHr HMHsICyMYptgE7Io1ItRSTDB6p51GPK04/ZyX87CRjRiLrZpdCPCxXYcsV0tQHFw g05cUypk=
We are continuing to build an app on a headless equinox container that provides p2 installation facilities over an http interface and are running into issues with installing certain bundles. We can install many features into the container and apply changes and start the bundles, but certain features are installing bundles that cause p2 to restart the already running servlets, and the http client never gets a response.
We've run across a generalized discussion of why this happens (http://dev.eclipse.org/mhonarc/lists/p2-dev/msg02006.html) but is there a good way to actually debug/diagnose this behaviour? Or, better yet, is there a way to exclude certain bundles from being considered as part of the installation plan? The servlet and it's supporting middle tier bundles are a bootstrap mechanism that we want running no matter what.