Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14613

(7.1.z) MBean query in servlet init leads to messaging subsystem errors on server startup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.4.CR1, 7.1.4.GA
    • 7.1.1.GA
    • None
    • None
    • Hide

      Force servlet lazy init by not using load-on-startup

      Show
      Force servlet lazy init by not using load-on-startup
    • Hide

      1. Ensure EAP 7.1 server is stopped
      2. Build and deploy the following application https://github.com/jamesnetherton/examples/tree/master/eap/servlet-init-test
      3. Start EAP 7.1 with the 'full' profile: standalone.sh -c standalone-full.xml
      4. Observe errors output from the messaging subsystem

      Show
      1. Ensure EAP 7.1 server is stopped 2. Build and deploy the following application https://github.com/jamesnetherton/examples/tree/master/eap/servlet-init-test 3. Start EAP 7.1 with the 'full' profile: standalone.sh -c standalone-full.xml 4. Observe errors output from the messaging subsystem

    Description

      There are some Servlets which perform MBean queries during Servlet init where loadOnStartup is set.

      For example:

      @WebServlet(name = "HttpServiceServlet", urlPatterns = { "/*" }, loadOnStartup = 1)
public class MyServlet extends HttpServlet {

    @Override
    public void init() throws ServletException {
        super.init();
        MBeanServer mBeanServer = ManagementFactory.getPlatformMBeanServer();
        try {
            mBeanServer.queryNames(new ObjectName("*:type=security,area=jmx,*"), null);
        } catch (MalformedObjectNameException e) {
            e.printStackTrace();
        }
    }
}

      Full example here:

      https://github.com/jamesnetherton/examples/tree/master/eap/servlet-init-test

      When EAP is started with the 'full' profile, this leads to some errors being output from the messaging subsystem:

      09:07:36,518 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 69) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([
    ("subsystem" => "messaging-activemq"),
    ("server" => "default"),
    ("pooled-connection-factory" => "activemq-ra"),
    ("statistics" => "pool")
]) - failure description: "WFLYCTL0030: No resource definition is registered for address [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"pooled-connection-factory\" => \"activemq-ra\"),
    (\"statistics\" => \"pool\")
]"
09:07:36,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 69) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([
    ("subsystem" => "messaging-activemq"),
    ("server" => "default"),
    ("pooled-connection-factory" => "activemq-ra"),
    ("statistics" => "pool")
]) - failure description: "WFLYCTL0030: No resource definition is registered for address [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"pooled-connection-factory\" => \"activemq-ra\"),
    (\"statistics\" => \"pool\")
]"

      I tested on WildFly 12 and this issue does not occur.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9553 PooledConnectionFactoryAdd adds a resource with no registration

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9553 PooledConnectionFactoryAdd adds a resource with no registration

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9553 PooledConnectionFactoryAdd adds a resource with no registration

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              jondruse@redhat.com Jiri Ondrusek
              jnethert@redhat.com James Netherton
              Peter Mackay Peter Mackay
              Peter Mackay Peter Mackay
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: