Thanks, that works, as I guess I’d expect it to. I’ve just never needed to do that before nor does my production machine have that specified.
This started out of the blue fairly recently but I can’t say exactly when because unlike the production machine, the test machine doesn’t run continuously so I don’t know exactly when things starting going weird. It was fairly obvious that some of the security related stuff has changed so I can only assume it’s somehow related to that. From: Leschke, Scott <[email protected]> Sent: Tuesday, June 02, 2020 8:07 PM To: [email protected] Subject: RE: javax.mail bundle won't resolve under Java 8 I’ve never had to do that before but I’ll give it a try. Thanks so much. Any other suggestions / thoughts? From: Davi Baldin Tavares <[email protected]<mailto:[email protected]>> Sent: Tuesday, June 02, 2020 6:08 PM To: [email protected]<mailto:[email protected]> Subject: Re: javax.mail bundle won't resolve under Java 8 Hí, In my case I have to add javax.activation in config.properties to get mail working, just like this: Edit etc/config.properties and add javax.activation in the org.osgi.framework.system.packages.extra <<Looks like>> # # Extra packages appended after standard packages # org.osgi.framework.system.packages.extra = \ org.apache.karaf.branding, \ javax.activation, \ sun.misc, \ Em ter., 2 de jun. de 2020 às 16:55, Leschke, Scott <[email protected]<mailto:[email protected]>> escreveu: Question. What change in my environment could cause a bundle to fail to resolve? I’ve been using bundle javax.mail-1.5.6.jar for many months with Karaf 4.2.8 and OpenJDK 8. It would appear that something was changed in my VM (Win 2016), some security settings at a minimum, some weeks ago and now I’m seeing various odd behavior, one of which is that the mail bundle no longer resolves but appears to fail looking for javax.activation. I’m hoping somebody might help me narrow the scope of what may be causing this so that I can get the security guys to undo whatever it is they may have done. This is dev/test box, my production VM is running the same setup without issues which is why I’m fairly certain that it’s an environment change. 2020-06-02T13:47:42,753 | ERROR | FelixStartLevel | Felix | 5 - org.ops4j.pax.logging.pax-logging-api - 1.11.4 | Bundle com.sun.mail.javax.mail [44] Error starting file:/E:/Karaf/apache-karaf-4.2.8/deploy/javax.mail-1.5.6.jar (org.osgi.framework.BundleException: Unable to resolve com.sun.mail.javax.mail [44](R 44.0): missing requirement [com.sun.mail.javax.mail [44](R 44.0)] osgi.wiring.package; (osgi.wiring.package=javax.activation) Unresolved requirements: [[com.sun.mail.javax.mail [44](R 44.0)] osgi.wiring.package; (osgi.wiring.package=javax.activation)]) org.osgi.framework.BundleException: Unable to resolve com.sun.mail.javax.mail [44](R 44.0): missing requirement [com.sun.mail.javax.mail [44](R 44.0)] osgi.wiring.package; (osgi.wiring.package=javax.activation) Unresolved requirements: [[com.sun.mail.javax.mail [44](R 44.0)] osgi.wiring.package; (osgi.wiring.package=javax.activation)] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149) ~[org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2119) ~[org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) [org.apache.felix.framework-5.6.12.jar:?] Regards, Scott -- Davi Baldin Tavares (Consultoria e Serviços em T.I.) Fone: (19) 9-9757-5166 E-mail: [email protected]<mailto:[email protected]>
