[ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10253: ------------------------------------------ I did test the hack pretty intensely and it pretty much solved the problems we were experiencing - at least for me. I did then dig further and found out that the bundles were activated lazily which is not valid for bundles that have services. Bundles with services have to be activated by default. I therefore removed the bundle activators and unchecked "Activate plug-in if one of its classes is loaded". Now things work fine for me even when the hack is commented. I committed my changes to TRUNK. @Rob: Please verify that things work fine for you, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10253: ------------------------------------------ the above changes did not solve the problem so I had to revert to the version before my changes. I tracked the client code down to several component and I'm pretty sure that the correct jars are loaded, so IMHO this is not an osgi issue per se. I then started tracking the authentication issues that you get if you start an as71 (after having started an as7) and found the following code in the as71 client: {code} public ManagementChannel getChannel() throws IOException { AccessController.doPrivileged(new PrivilegedAction<Object>() { public Object run() { if (Security.getProvider(saslProvider.getName()) == null) { Security.insertProviderAt(saslProvider, 1); } return null; } }); {code} This sets the provider for the whole JVM, no chance for plugin-separation. I then to set the sasl providers in each as7 management bundle, which should solve the auth issue, but I still have the issue. So I suspect that there are more similar approaches in the client jar. I am currently still talking to darran lofthouse in this matter. Rob now has a hack that solves the problem. IMHO this should be fine for m5, but we should elaborate on a real solution later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10253 at 11/28/11 4:01 PM: -------------------------------------------------------------------- the above changes did not solve the problem so I had to revert to the version before my changes. I tracked the client code down to several component and I'm pretty sure that the correct jars are loaded, so IMHO this is not an osgi issue per se. I then started tracking the authentication issues that you get if you start an as71 (after having started an as7) and found the following code in the as71 client: {code} ManagementClientChannelStrategy#Establishing#getChannel(): public ManagementChannel getChannel() throws IOException { AccessController.doPrivileged(new PrivilegedAction<Object>() { public Object run() { if (Security.getProvider(saslProvider.getName()) == null) { Security.insertProviderAt(saslProvider, 1); } return null; } }); {code} This sets the provider for the whole JVM, no chance for plugin-separation. I then to set the sasl providers in each as7 management bundle, which should solve the auth issue, but I still have the issue. So I suspect that there are more similar approaches in the client jar. I am currently still talking to darran lofthouse in this matter. Rob now has a hack that solves the problem. IMHO this should be fine for m5, but we should elaborate on a real solution later. was (Author: adietish): the above changes did not solve the problem so I had to revert to the version before my changes. I tracked the client code down to several component and I'm pretty sure that the correct jars are loaded, so IMHO this is not an osgi issue per se. I then started tracking the authentication issues that you get if you start an as71 (after having started an as7) and found the following code in the as71 client: ManagementClientChannelStrategy#Establishing#getChannel(): {code} public ManagementChannel getChannel() throws IOException { AccessController.doPrivileged(new PrivilegedAction<Object>() { public Object run() { if (Security.getProvider(saslProvider.getName()) == null) { Security.insertProviderAt(saslProvider, 1); } return null; } }); {code} This sets the provider for the whole JVM, no chance for plugin-separation. I then to set the sasl providers in each as7 management bundle, which should solve the auth issue, but I still have the issue. So I suspect that there are more similar approaches in the client jar. I am currently still talking to darran lofthouse in this matter. Rob now has a hack that solves the problem. IMHO this should be fine for m5, but we should elaborate on a real solution later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10253. -------------------------------------- Resolution: Done the management plugin has been committed to TRUNK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugi... ] Isaac Rooskov updated JBIDE-10253: ---------------------------------- Release Notes Docs Status: Not Required Writer: irooskov No release note is required for this issue as server compatibility will be discussed in the overview section of the document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira