There was another thing I noticed. I had submitted a Jira on this on an earlier release. I think it may even still be open.
In the hot deploy case, I’m on Windows so may just be a Windows thing, the “pseudo” bundles get create with version 0.0.0 that map to a folder in the deployment hierarchy. So for my application, the deployment hierarchy is at E:\BAM. It has 3 subfolders that contains bundles and/or .cfg files, I’ll call them F1, F2, and F3. For each subfolder, a bundle is created with the names, E_BAM_F1, E_BAM_F2, E_BAM_F3. Previous experience shows that these bundles can be uninstalled without problems but I believe the issue disappeared and has now come back. Thanks and regards, Scott From: Jean-Baptiste Onofre <j...@nanthrax.net> Sent: Monday, November 02, 2020 11:19 PM To: user@karaf.apache.org Subject: Re: Karaf 4.3.0: Bundles don't resolve because of unsatisfied java.* packages CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. ________________________________ Hi Scott, It’s very surprising as Karaf bundles themselves use java.io<https://urldefense.com/v3/__http:/java.io__;!!PoMpmxQzTok3!p5QOKC-0IGXdkzWH3NoHzAhyMBpPpKQbVq2z2no-VUOfn8tMibUcPp7k7TB8HGI$> (and other JDK packages). Let me try with a simple bundle dropped in deploy folder. Regards JB Le 2 nov. 2020 à 17:50, Leschke, Scott <slesc...@medline.com<mailto:slesc...@medline.com>> a écrit : Hi JB, Sorry for the confusion. The trace is a bit misleading. Yes, that is one of my bundles. I added the trace as an example (arbitrarily chosen) since Felix outputs the same trace for all bundles the fail to resolve. The bundle I’m referring to is a utilities library that sits at the top of the dependency tree so the other bundles that refer to that one also can’t resolve as a result. In the case of the medline.util bundle which I’m referring to, the bundle:diag shows a long list of unresolved java.* packages. 2020-11-01T18:47:06,499 | WARN | fileinstall-E:/BAM | fileinstall | 17 - org.apache.felix.fileinstall - 3.6.8 | Error while starting bundle: file:/E:/BAM/medline.util.jar org.osgi.framework.BundleException: Unable to resolve medline.util [163](R 163.0): missing requirement [medline.util [163](R 163.0)] osgi.wiring.package; (osgi.wiring.package=java.io<https://urldefense.com/v3/__http:/java.io/__;!!PoMpmxQzTok3!p5QOKC-0IGXdkzWH3NoHzAhyMBpPpKQbVq2z2no-VUOfn8tMibUcPp7kr8iQcZ0$>) Unresolved requirements: [[medline.util [163](R 163.0)] osgi.wiring.package; (osgi.wiring.package=java.io<https://urldefense.com/v3/__http:/java.io/__;!!PoMpmxQzTok3!p5QOKC-0IGXdkzWH3NoHzAhyMBpPpKQbVq2z2no-VUOfn8tMibUcPp7kr8iQcZ0$>)] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368) ~[?:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2281) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [!/:3.6.8] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [!/:3.6.8] at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [!/:3.6.8] at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [!/:3.6.8] at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [!/:3.6.8] at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [!/:3.6.8] Scott From: Jean-Baptiste Onofre <j...@nanthrax.net<mailto:j...@nanthrax.net>> Sent: Sunday, November 01, 2020 11:08 PM To: user@karaf.apache.org<mailto:user@karaf.apache.org> Subject: Re: Karaf 4.3.0: Bundles don't resolve because of unsatisfied java.* packages CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. ________________________________ Hi Scott, In the log, it seems that it’s the package com.medline.osgi which is not resolved. Is it one of your package ? Regards JB Le 2 nov. 2020 à 01:48, Leschke, Scott <slesc...@medline.com<mailto:slesc...@medline.com>> a écrit : Karaf 4.3.0 on Windows, JDK 14. All java.* packages, including java.lang, show as Unsatisfied Requriements in bundle:diag output. Setting karaf.framework=equinox yields similar results. org.osgi.framework.BundleException: Unable to resolve medline.bam.provider.jdbc [181](R 181.0): missing requirement [medline.bam.provider.jdbc [181](R 181.0)] osgi.wiring.package; (&(osgi.wiring.package=com.medline.osgi)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve medline.osgi [169](R 169.0): missing requirement [medline.osgi [169](R 169.0)] osgi.wiring.package; (&(osgi.wiring.package=com.medline.util.service)(version>=1.0.0)(!(version>=2.0.0))) [caused by: Unable to resolve medline.util [163](R 163.0): missing requirement [medline.util [163](R 163.0)] osgi.wiring.package; (osgi.wiring.package=java.io<https://urldefense.com/v3/__http:/java.io/__;!!PoMpmxQzTok3!v7JOYm60VJQSfZebzVzJUcZnPyswpRGqWRrVzf64Rvn6BasJ8h03hmiJK0e1vag$>)]] Unresolved requirements: [[medline.bam.provider.jdbc [181](R 181.0)] osgi.wiring.package; (&(osgi.wiring.package=com.medline.osgi)(version>=1.0.0)(!(version>=2.0.0)))] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368) ~[?:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2281) ~[?:?] …. Scott
