incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Jaquith (JIRA)" <>
Subject [jira] Commented: (JSPWIKI-452) JMX implementation does not support More than one JSPWiki instance
Date Mon, 29 Dec 2008 22:57:44 GMT


Andrew Jaquith commented on JSPWIKI-452:

Harry -  I think we should use the JSPWiki application name, and throw an exception/print
an error if an MBean for a JSPWiki instance with the previous name had previously been registered.
We do want application names to be unique, right? This would be one clear way to detect more
than one webapp whose wikis had the same name. 

> JMX implementation does not support More than one JSPWiki instance
> ------------------------------------------------------------------
>                 Key: JSPWIKI-452
>                 URL:
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Core & storage
>    Affects Versions: 3.0
>         Environment: JSPWiki 3.0
>            Reporter: Harry Metske
>            Assignee: Harry Metske
>            Priority: Minor
> The current JMX implementation does not handle multiple JSPWiki instances per JVM very
> This is true for both the new LoggerMBeans as for the other Admin type MBeans.
> The problem is that the ObjectName does not make the MBeans unique.
> Example names:
> JSPWiki:component=Core,name=Core bean
> JSPWiki:component=Loggers,name=com.ecyrd.jspwiki.WikiEngine
> So, depending on the order of startup, JSPWikiA or JSPWwikiB gets the MBean. 
> This can be a bit dangerous, you think you reload the Search manager for A, but B gets
> But apparently we don't have that many users that use both multiple wiki's and the JMX.
> I think we need something that makes the MBean names unique. Question is what do we use
> 1. property jspwiki.applicationName ? (still no guarantee) 
> 2. context root of webapp (also no guarantee)
> 3. a random string appended, so this would make it like : JSPWiki-BGJSKIR:component=Core,name=Core
bean,  not very elegant
> 4. something perfect, any idea's ?
> The current AdminBeanManager also has a minor bug, saying it registers an MBean while
it didn't, I'll fix that soon.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message