Announcement Announcement Module
Collapse
No announcement yet.
dm-server 2.0.0.M4 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • dm-server 2.0.0.M4

    I downloaded a fresh copy of version M4 of the server. Then I started it with startup.bat -clean. In serviceability\logs\dm-server, log.txt shows the following:

    [2009-10-20 18:35:40.773] server-dm-13 Unable to register system information Operating System for management
    [2009-10-20 18:35:40.792] server-dm-13 Unable to register system information Runtime for management
    [2009-10-20 18:35:40.798] server-dm-13 Unable to register system information Copy for management
    [2009-10-20 18:35:40.805] server-dm-13 Unable to register system information MarkSweepCompact for management
    [2009-10-20 18:35:40.813] server-dm-13 Unable to register system information Code Cache for management
    [2009-10-20 18:35:40.818] server-dm-13 Unable to register system information Eden Space for management
    [2009-10-20 18:35:40.832] server-dm-13 Unable to register system information Survivor Space for management
    [2009-10-20 18:35:40.837] server-dm-13 Unable to register system information Tenured Gen for management
    [2009-10-20 18:35:40.844] server-dm-13 Unable to register system information Perm Gen for management
    [2009-10-20 18:35:40.848] server-dm-13 Unable to register system information Perm Gen [shared-ro] for management
    [2009-10-20 18:35:40.853] server-dm-13 Unable to register system information Perm Gen [shared-rw] for management
    [2009-10-20 18:35:40.869] server-dm-13 Unable to register system information Memory for management
    [2009-10-20 18:35:40.876] server-dm-13 Unable to register system information Threading for management
    [2009-10-20 18:35:40.882] server-dm-13 Unable to register system information Class Loading for management
    [2009-10-20 18:35:42.483] server-dm-10 No global naming context defined for server

    Is it common to see errors like this on a fresh copy of the server?

  • #2
    Firstly, please note that 2.0.0.M5 is now out, so you may wish to skip M4.

    Secondly, those messages look like they emanate from the JVM. They are mostly related to the JVM's Garbage Collector. Which JVM are you using? You should make sure you are using the Sun Java 6 JRE or JDK/SDK when running dm Server v2.

    Comment


    • #3
      Thanks. I was using jdk 1.6.

      Comment


      • #4
        I am not sure which vendor produced your jdk 1.6, but if it was Sun, then those messages are not normal and you should probably look into your Java environment carefully. The messages do not seem to be provoked by dm Server.

        Comment


        • #5
          I am using Sun's sdk. I didn't encounter this problem in M5.
          I ran M4 on two machines - Windows XP and Windows Vista using Sun's sdk. Both exhibited similar behavior.

          Comment


          • #6
            M4 logs some of the JVM's MBean events, but M5 doesn't do that. So the JVM is probably functioning normally and the diagnostics in M4 are simply misleading.

            Comment

            Working...
            X