Symptom

After deploying V5.2SP1 to Oracle Application Server 10g (OracleAS 10g) v10.1.3.1 with an application name of anything other than "com.pega.PegaRULES," you receive the security exception:

Unable to create MBean server

while trying to register the bean with the System Management Application (prsysmgmt) .

Solution

Workaround

This security exception is due to a security proxy.

Oracle Application Server 10g (OracleAS 10g) documents that the domain of the bean being registered should be the same as the domain of the application and to use getDefaultDomain() to do this. But, getDefaultDomain() appears to return the context root and not the application name.

• If the application is deployed with the name "com.pega.PegaRULES," then Java Management Extensions (JMX) initializes and the beans get registered.
• If your Process Commander application is deployed with an application name of anything other than "com.pega.PegaRULES," you will be unable to register the bean.

You can disable this security proxy in a development system using -Doc4j.jmx.security.proxy.off=true. However, this should not be done in a production environment.

This is valid for all V5.2SP1 installs on OracleAS 10g Release 3 (v10.1.3.1).