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

          People

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

            Dates

            • Created:
              Updated: