[OAK-3802] SessionMBean not getting registered due to MalformedObjectNameException

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.11
• Fix Version/s: 1.3.13, 1.4
• Component/s: core
• Labels: regresion
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 17/Dec/15 04:29
• Updated: 02/Mar/16 15:11
• Resolved: 17/Dec/15 05:56

Description

Due to changes done in OAK-3477 SessionMBean is not getting registered as it contains ',' in the ObjectName. Unfortunately the exception thrown gets lost and this did not got detected so far

javax.management.MalformedObjectNameException: Invalid character in value: `,'
	at javax.management.ObjectName.checkValue(ObjectName.java:1009)
	at javax.management.ObjectName.construct(ObjectName.java:725)
	at javax.management.ObjectName.<init>(ObjectName.java:1425)
	at org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:79)
	at org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:68)
	at org.apache.jackrabbit.oak.jcr.repository.RepositoryImpl$RegistrationTask.run(RepositoryImpl.java:523)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

The name passed for ObjectName is

{name=admin@session-11@Dec 17, 2015 9:57:11 AM, type=SessionStatistics}

Issue Links

• is broken by: OAK-3477 Make JMX Bean names predictable so they can be used in configurations.