Skip to main content
RetoZigerlig
Level 2
Oct 16, 2015 2:28 AM UTC
Solved

Use JMX Bean from sourcecode org.apache.jackrabbit.oak: External Identity Synchronization Management

Hi

In CQ 5.5 we connected to the ldap jmx bean via: 

javax.management.MBeanServer.getClassLoaderFor("com.adobe.granite.ldap:host=localhost,port=10389,type=Tools")

e.g. for the operation syncAllExternalUsers(), which worked fine.

Now with AEM 6.1 I try to use the new JMX Bean via:

javax.management.MBeanServer.getClassLoaderFor("org.apache.jackrabbit.oak:handler=mySyncHandler,idp=ldap")

but I get the following exception:

javax.management.InstanceNotFoundException:org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean:handler=mySyncHandler,idp=ldap

If I run the syncAllExternalUsers() manually via AEM Web Console, the function works fine. I also tried to connect to the bean with org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean:handler=mySyncHandler,idp=ldap .

Does anyone have an idea, how I an call the new bean in AEM 6.1?

Thanks alot

Reto

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
awadheshvAccepted solution
Level 3
Oct 16, 2015 2:28 AM UTC

Try this:

connect to your cq jmx port via jconsole. (jconsole is located at $jdk_home/bin/jconsole). open jconsole. connect to your CQ instance from the available process. then in the Mbeans tab see if your MBean is registered there. it will also help determine if anything is wrong with the objectname string. whatever objectname is listed there is what should be provided in the code.

this should look something like that in the attached shreenshot.

View in thread

12 replies

RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

Hi awadheshv

Thanks alot for your hint with the jconsole. This solved my problem. I figured out that my objectname was wrong. I have to use the following objectname: org.apache.jackrabbit.oak:name=External Identity Synchronization Management,handler="mySyncHandler",type=UserManagement,idp="ldap"

Translate
awadheshvAccepted solution
Level 3
Oct 16, 2015 2:28 AM UTC

Try this:

connect to your cq jmx port via jconsole. (jconsole is located at $jdk_home/bin/jconsole). open jconsole. connect to your CQ instance from the available process. then in the Mbeans tab see if your MBean is registered there. it will also help determine if anything is wrong with the objectname string. whatever objectname is listed there is what should be provided in the code.

this should look something like that in the attached shreenshot.

Translate
RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

This is what I'm already doing, without luck:

final ObjectName targetObjectName = new ObjectName(ldapJmxObjectName);final ClassLoader tmpClassLoader = mBeanServer.getClassLoaderFor(targetObjectName);
Translate
awadheshv
Level 3
Oct 16, 2015 2:28 AM UTC

try this (not sure if this would work) -

javax.management.MBeanServer.getClassLoaderFor(new ObjectName("org.apache.jackrabbit.oak:handler=mySyncHandler,idp=ldap"));
Translate
RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

How does your MBeanServer.invoke() look like? My configuration is attached.

Translate
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
Oct 16, 2015 2:28 AM UTC

Interesting !! I did setup locally and it is working for me.. Do you mind sharing the screenshot of your configurations ?

Translate
RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

I'm using the default handler.

Translate
Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
Oct 16, 2015 2:28 AM UTC

are you using the default Handler or a custom handler ? if So can you share your handler ..

Translate
RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

Hi bsloki

Thank you for your quick response. Yes, I configured the the properties for 'Apache Jackrabbit Oak Default Sync Handler' in the configMgr, otherwise none of the LDAP function would work. I followed this instruction for the configuration: http://docs.adobe.com/docs/en/aem/6-1/administer/security/ldap-config.html. In fact that the LDAP function works fine, I think I'm doing something wrong in calling the JMX bean.

Translate
RetoZigerligAuthor
Level 2
Oct 16, 2015 2:28 AM UTC

Hi justin_at_adobe

I also tried it with MBeanServer.invoke() but I get the same exception.

Best regards,

Reto

Translate
Show more replies
Terms & ConditionsAccessibility statement

Loading footer...