glassfish
  1. glassfish
  2. GLASSFISH-12796

Problem reading AMX beans after Glassfish restart

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: not determined
    • Component/s: amx
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      12,796

      Description

      I'm accessing the jdbc resources in Glassfish via the AMX JMX beans, but I've
      having problems on a Glassfish restart
      If my war is deployed, and Glassfish is restarted, the war fails to deploy on
      the Glassfish restart - this is due to the bean amx:pp=/domain,type=resources
      not being present.
      The AMX service is only started if its required (eg if the admin console is
      loaded)
      I've tried manually starting the AMX service from my war:
      I've tried calling the method new
      AMXGlassfish(AMXGlassfish.DEFAULT_JMX_DOMAIN).bootAMX() from my war, but on
      restarting glassfish, the call to bootAMX() hangs indefinitely
      I've also tried connecting to the AMX JMX bean with the URL
      service:jmx:rmi://<local host>:8686/jndi/rmi://<local host>:8686/jmxrmi
      This works if I'm deploying after Glassfish has been started, and the admin
      console hasn't been loaded.
      If the war is deployed, and Glassfish is restarted, this fails as Glassfish
      cannot connect to the RMI JMX service.
      From looking at glassfish logs, the start up sequence seems to be that Glassfish
      does not launch JMX until after all existing war files have been deployed.
      Version of glassfish: v3

        Activity

        Hide
        sennen added a comment -

        Attachment as per my previous comment.

        Show
        sennen added a comment - Attachment as per my previous comment.
        Hide
        zlj added a comment - - edited

        I face nearly the same issue on GF 3.1.1.

        When I do not "boot" AMX manually, I can't request any AMX/MBean attributes for my web-applications. "boot" means executing bootAMX() in MBean "amx-support:type=boot-amx".

        Show
        zlj added a comment - - edited I face nearly the same issue on GF 3.1.1. When I do not "boot" AMX manually, I can't request any AMX/MBean attributes for my web-applications. "boot" means executing bootAMX() in MBean "amx-support:type=boot-amx".
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
        Hide
        Wasomumba added a comment - - edited

        The comments in this ticket address different issues. I'm talking about the problem, that the AMX Service is not available at startup, as described by sennen above.

        This is caused by the fact, that the amx service is started AFTER startup of the server.

        To fix this issue, i think the runlevel from "org.glassfish.admin.mbeanserver.JMXStartupService" and "org.glassfish.admin.mbeanserver.MBeanServerFactory" should be changed from "PostStartupRunLevel" to "InitRunLevel".

        What do you think?

        Show
        Wasomumba added a comment - - edited The comments in this ticket address different issues. I'm talking about the problem, that the AMX Service is not available at startup, as described by sennen above. This is caused by the fact, that the amx service is started AFTER startup of the server. To fix this issue, i think the runlevel from "org.glassfish.admin.mbeanserver.JMXStartupService" and "org.glassfish.admin.mbeanserver.MBeanServerFactory" should be changed from "PostStartupRunLevel" to "InitRunLevel". What do you think?
        Hide
        naman_mehta added a comment -

        hi peter,

        Assigning this issue to you. Let me know if you need any details from my side.

        Naman

        Show
        naman_mehta added a comment - hi peter, Assigning this issue to you. Let me know if you need any details from my side. Naman

          People

          • Assignee:
            Peter Bower
            Reporter:
            snobbles1
          • Votes:
            5 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated: