[AMQ-3033] BrokerService leaks threads when scheduler or jmx are enabled

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.1
• Fix Version/s: 5.5.0
• Component/s: Broker
• Assignee: Gary Tully
• Reporter: Benson Margulies
• Created: 12/Nov/10 19:15
• Updated: 14/Dec/10 14:28
• Resolved: 14/Dec/10 14:28

Description

If I launch the broker with the below, without the first two lines, and call brokerService.stop(), I have 13 more threads after than I had when I started. This in spite of the code I see in the BrokerService class that claims to shut down the scheduler (and the scheduler is one of the threads).

           brokerService.setSchedulerSupport(false);
            brokerService.setUseJmx(false);
            brokerService.setPersistenceAdapter(new MemoryPersistenceAdapter());
            brokerService.setPersistent(false);
            brokerService.setUseShutdownHook(true);
            brokerService.setUseLoggingForShutdownErrors(false);
            brokerService.setSchedulerSupport(false);
            bindAddress = "tcp://localhost:" + getBrokerPort();
            tcpTransport = brokerService.addConnector(bindAddress);
            brokerService.setDataDirectory(dataDirectory.getAbsolutePath());
            brokerService.start();