[ 
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565832#action_12565832
 ] 

Rick Hillegas commented on DERBY-1387:
--------------------------------------

Thanks for the updated spec, John. I brought up a Derby server with the JMX 
beans enabled and I ran JConsole against it. Here are some initial reactions:

1) I was pleased that the Sun JMX properties worked with my Apple VM.

2) I brought up the server with authentication enabled but I didn't have to 
supply credentials in order to view the NetworkServer and System MBeans. That 
seems wrong to me. The Version MBean was also viewable but that seems ok to me.

3) I was able to change properties in the NetworkServer MBean--at least my 
changes were accepted on the screen. However, when I tried to change properties 
in the System MBean, I was slapped with an "access denied 
(java.util.PropertyPermission * read,write)" diagnostic.

4) Using the System MBean, it seemed that I was able to boot an existing 
database and then access its MBean. Again, without supplying credentials, this 
seemed wrong to me. Most of the properties were listed as "Unavailable".

5) Using the System MBean, I tried to boot a nonexistent database. This gave me 
the following diagnostic:

Problem invoking bootDatabase: java.rmi.UnmarshalException: Error unmarshaling 
return: nested exception is:
java.lang.ClassNotFoundException: org.apache.derby.impl.jdbc.EmbedSQLException 
(no security manager: RMI class loader disabled)

6) I saw the same diagnostic when I used the System MBean to boot an encrypted 
database.

7) I saw a similar diagnostic when I tried to create a user via the MBean for 
the existing database.

8) When I invoked the shutdown operation on the System MBean, I saw the 
following diagnostic:

Problem invoking shutdown: java.rmi.UnmarshalException: Error unmarshaling 
return header; nested exception is:
java.io.EOFException

9) However, after dismissing the diagnostic windows, the MBeans disappeared 
from the screen and I was presented with a blank JConsole window with only a 
"Connection" menu item in the menu bar.  However, I was unable to connect via 
that menu item.

For the record, this is the startup command which I used to boot the server:

java -Dderby.connection.requireAuthentication=true \
  -Dderby.authentication.provider=BUILTIN \
  -Dderby.user.\"rick\"=rickspassword \
  -Dderby.database.sqlAuthorization=true \
  -Dcom.sun.management.jmxremote.port=1528 \
  -Dcom.sun.management.jmxremote.authenticate=false \
  -Dcom.sun.management.jmxremote.ssl=false \
  -Dderby.system.jmx=true \
  org.apache.derby.drda.NetworkServerControl start -p 8246

and this is the command which I used to boot JConsole:

jconsole 1735

Thanks,
-Rick

> Add JMX extensions to Derby
> ---------------------------
>
>                 Key: DERBY-1387
>                 URL: https://issues.apache.org/jira/browse/DERBY-1387
>             Project: Derby
>          Issue Type: New Feature
>          Components: Services
>            Reporter: Sanket Sharma
>            Assignee: John H. Embretsen
>         Attachments: DERBY-1387-1.diff, DERBY-1387-1.stat, DERBY-1387-2.diff, 
> DERBY-1387-2.stat, DERBY-1387-3.diff, DERBY-1387-3.stat, DERBY-1387-4.diff, 
> DERBY-1387-4.stat, DERBY-1387-5.diff, DERBY-1387-5.stat, DERBY-1387-6.zip, 
> DERBY-1387-7.zip, DERBY-1387-8.zip, DERBY-1387-9.diff, DERBY-1387-9.stat, 
> derbyjmx.patch, jmx.diff, jmx.stat, jmxFuncspec.html, jmxFuncspec.html, 
> jmxFuncspec.html, Requirements for JMX Updated.html, Requirements for 
> JMX.html, Requirements for JMX.zip
>
>
> This is a draft requirement specification for adding monitoring and 
> management extensions to Apache Derby using JMX. The requirements document 
> has been uploaded on JIRA as well as the Derby Wiki page at 
> http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX
> Developers and Users are requested to please look at the document (feature 
> list in particular) and add their own rating to features by adding a coloumn 
> to the table.
> Comments are welcome.

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

Reply via email to