BrokerService leaks threads when scheduler or jmx are enabled
-------------------------------------------------------------
Key: AMQ-3033
URL: https://issues.apache.org/activemq/browse/AMQ-3033
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.1
Reporter: Benson Margulies
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).
{code}
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();
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
