Details
-
Bug
-
Resolution: Done
-
Major
-
6.0.0.Alpha2
-
None
-
None
Description
When the CLI client runs the "cache ___defaultcache" command to select a cache, the first things that happens is that the "createSessionId" call is invoked via JMX on the server.
When the command is run for the first time, there is no previously selected cache. Therefore, the "active cache" parameter for the "createSessionId" command is null.
On the server side, in ResourceDMBean.invoke(), there is a debug log message that would log the class of the arguments received using args[i].getClass(). As args[i] is null for the "active cache" parameter, the call fails with a NullPointerException.
As a result, it is not possible to select a cache with the CLI client when debug logging is enabled in ResourceDMBean.
—
I have created a very small pull request for this on GitHub.