Hey, thanks for the tips...
I was able to resolve the issue earlier...
I did have one question about the codeBase, though.
For other permission related issues, the <something> gave me a message
which pretty much spelled out what had to be added to the server.policy
file (including the codeBase). This exception isn't as helpful... I
have no idea which jar is trying to register the MBean.
Where should this usability bug get filed?
vbk
Kedar Mhaswade wrote:
> Well,
> it means you should read the application documentation more closely :)
>
> I think that your application is trying to register an MBean and
> (thankfully) it can't do that out of the box. You, as an administrator
> should grant that permission. The permission that you should add is
> MBeanPermission. Here is what I suggest:
> - start policytool.
> - open the server.policy for the default domain (assuming that's the
> target) as in <glassfish-image>/domains/domain1/config
> - identify the codebase. For starters *only*, I would suggest
> <install-dir>/domains/domain1/applications, if you have deployed the
> app using asadmin deploy command.
> - edit the file for the above codebase to have the said permission
> i.e. javax.management.MBeanPermission for registration.
>
> A relevant piece in server.policy looks like:
> grant {
> permission javax.management.MBeanTrustPermission "register" ;
> };
>
>
> Kedar
>
>