Nice to hear that you found a full set of permissions that your scenario requires. My answer was only related to the stacktrace that you attached - to the FrameworkMBeanHandler class.
I'd be nice to have tooling that would help analyzing source code (or binaries) and detect where additional OSGi related permissions might potentailly be required. Just analyzing stacktraces, adding permissions, and trying again is somewhat painful. Bartek 2011/4/28 Gupte, Prajakta <[email protected]>: > Bartek, > Thanks for your response. The issue was resolved by adding the permissions > you mentioned and a few more. > --- > permission org.osgi.framework.AdminPermission "*", "*"; > permission org.osgi.framework.PackagePermission "*", "exportonly,import"; > permission org.osgi.framework.ServicePermission "*", "get,register"; > permission org.osgi.framework.BundlePermission "*", > "host,provide,fragment"; > permission org.osgi.service.cm.ConfigurationPermission "*", "configure"; > > //for starting bundles > permission org.osgi.framework.SystemPermission > "org.osgi.service.packageadmin.PackageAdmin", "get"; > permission org.osgi.framework.AdminPermission > "org.osgi.service.packageadmin.PackageAdmin", "resolve"; > > permission org.osgi.framework.ServicePermission > "org.osgi.service.startlevel.StartLevel", "register,get"; > permission org.osgi.framework.AdminPermission > "org.osgi.service.startlevel.StartLevel", "*"; > > -----Original Message----- > From: Bartosz Kowalewski [mailto:[email protected]] > Sent: Thursday, April 28, 2011 12:07 PM > To: [email protected] > Subject: Re: Service Reference Null while starting > org.apache.aries.jmx.core-0.3.jar > > Hi, > > Just a wild guess: > org.osgi.framework.ServicePermission for *, get > or > org.osgi.framework.ServicePermission for > org.osgi.service.packageadmin.PackageAdmin and > org.osgi.service.startlevel.StartLevel, get > > Not sure if this helps and if this is sufficient. > > Best regards, > Bartek > > 2011/4/27 Gupte, Prajakta <[email protected]>: >> Hello, >> >> I am trying to deploy Apache Sling to a Tomcat 5.5 container with security >> restrictions. >> >> While accessing the Sling application, I receive the following error related >> to org.apache.aries.jmx.core-0.3.jar. It appears that this is due to missing >> permissions. However, I am unable to identify the permission setting >> required to resolve the error. The application keeps throwing a 503 error in >> the browser. >> >> Can you please advise on how to resolve this? >> >> Thanks, Prajakta. >> >> -- >> >> 27.04.2011 10:24:01.325 *INFO* [FelixDispatchQueue] >> org.apache.aries.jmx.core BundleEvent RESOLVED >> >> 27.04.2011 10:24:01.333 *INFO* [FelixDispatchQueue] >> org.apache.aries.jmx.core BundleEvent STOPPED >> >> 27.04.2011 10:24:01.334 *ERROR* [FelixDispatchQueue] >> org.apache.aries.jmx.core FrameworkEvent ERROR >> (org.osgi.framework.BundleException: >> >> Activator start error in bundle org.apache.aries.jmx.core [44].) >> org.osgi.framework.BundleException: Activator start error in bundle org. >> >> apache.aries.jmx.core [44]. >> >> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882) >> >> at org.apache.felix.framework.Felix.startBundle(Felix.java:1752) >> >> at >> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156) >> >> at >> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) >> >> at java.lang.Thread.run(Thread.java:619) >> >> Caused by: java.lang.NullPointerException: Specified service reference >> cannot be null. >> >> at >> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:319) >> >> at >> org.apache.aries.jmx.framework.FrameworkMBeanHandler.open(FrameworkMBeanHandler.java:71) >> >> at >> org.apache.aries.jmx.agent.JMXAgentImpl.start(JMXAgentImpl.java:91) >> >> at org.apache.aries.jmx.Activator.start(Activator.java:50) >> >> at >> org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1243) >> >> at java.security.AccessController.doPrivileged(Native Method) >> >> at >> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:620) >> >> at org.apache.felix.framework.Felix.activateBundle(Felix.java:1835) >> >> ... 4 more >> >> ________________________________ >> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions >> or views contained herein are not intended to be, and do not constitute, >> advice within the meaning of Section 975 of the Dodd-Frank Wall Street >> Reform and Consumer Protection Act. If you have received this communication >> in error, please destroy all electronic and paper copies and notify the >> sender immediately. Mistransmission is not intended to waive confidentiality >> or privilege. Morgan Stanley reserves the right, to the extent permitted >> under applicable law, to monitor electronic communications. This message is >> subject to terms available at the following link: >> http://www.morganstanley.com/disclaimers. If you cannot access these links, >> please notify us by reply message and we will send the contents to you. By >> messaging with Morgan Stanley you consent to the foregoing. > > -------------------------------------------------------------------------- > NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions > or views contained herein are not intended to be, and do not constitute, > advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform > and Consumer Protection Act. If you have received this communication in > error, please destroy all electronic and paper copies and notify the sender > immediately. Mistransmission is not intended to waive confidentiality or > privilege. Morgan Stanley reserves the right, to the extent permitted under > applicable law, to monitor electronic communications. This message is subject > to terms available at the following link: > http://www.morganstanley.com/disclaimers. If you cannot access these links, > please notify us by reply message and we will send the contents to you. By > messaging with Morgan Stanley you consent to the foregoing. >
