[
https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin....
]
Ian Springer updated JOPR-9:
----------------------------
Attachment: rhq-jmx-plugin-1.1.0.GA.jar
The attached rhq-jmx-plugin-1.1.0.GA.jar is a patched version of the 1.1.0.GA plugin,
which included EMS 1.2.6, instead of EMS 1.2.5. To update a RHQ 1.1.0.GA, Jopr 2.1.0.GA,
or JON 2.1.0.GA installation with this patched jmx plugin, do the following:
1) Overwrite
<rhq-server-dir>/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/rhq-jmx-plugin-1.1.0.GA.jar
with the patched jar.
2) If your Jopr Server is running, you should see a message informing you that it detected
the updated jmx plugin jar and deployed it. If not, start up your Server now.
3) Update all of your Agents to the new version of the jmx plugin jar. To do so, either
run the "plugins update" command from each Agent's prompt or execute the
"Update All Plugins" operation from the corresponding Agent Resource's
Operations tab. Note, if you have more than a handful of Agents, you may want to create a
Compatible Group containing all Agent Resources and then execute the "Update All
Plugins" operation on the Compatible Group.
The JNP credentials bug should no longer occur.
Cannot handle multiple JBossAS connections with different
credentials
---------------------------------------------------------------------
Key: JOPR-9
URL:
https://jira.jboss.org/jira/browse/JOPR-9
Project: Jopr
Issue Type: Bug
Affects Versions: 2.1
Reporter: Greg Hinkle
Assignee: Ian Springer
Fix For: 2.2
Attachments: rhq-jmx-plugin-1.1.0.GA.jar
Opened from RHQ-1030...
Basically, the JBoss JNP context factory is storing principal and credentials in
thread-locals so that we can have two stubs to different AS instances that require
different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded,
but that will only let you support different connections in different threads.
After some testing, it looks like we can just have EMS setup the SecurityAssociation
before every call into the stub. It should be fairly easy since EMS uses dynamic proxies
around the stubs.
SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-"));
SecurityAssociation.setCredential("-credentials-");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira