Bug #155 (closed)
Opened 18 years ago
Closed 18 years ago
IAdmin has hard-coded values for jmx connection.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Cc: | |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
The values currently encoded into IAdmin for executing synchronizeLoginCache() are the values most likely when installing JBoss. However, they are not a must. This needs to be made configurable and thoroughly tested.
Change History (2)
comment:1 Changed 18 years ago by jmoore
- Keywords changed from jboss, jmx to jboss, jmx, iteration1, story114
- Milestone changed from Unscheduled to 3.0-M3
- Status changed from new to assigned
- Version changed from 3.0-M1 to 3.0-M2
comment:2 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from assigned to closed
r765 adds a check to synchronizeLoginCache so that if AdminImpl cannot find an MBeanServer it'll just log a warning. With this, I think this is done. (i.e. has passed all the client tests)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r760 fixes. At least, now the hard-coded values are defined by our code-base, namely jboss-service.xml. We were pointing to the wrong security manager anyway. Now rather than refreshing the "jmx-console" cache, whose name shouldn't have been hard-coded (it's an install-time thing), we refresh the dynamic login config which Omero uses, i.e. DB-backed.