[
https://issues.apache.org/jira/browse/ARTEMIS-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267533#comment-17267533
]
Justin Bertram commented on ARTEMIS-3071:
-----------------------------------------
Did you add
{{org.apache.activemq.artemis.integration.bootstrap,org.apache.activemq.audit.base,org.apache.activemq.audit.message}}
to the {{loggers}} list at the top of your {{logging.properties}}? If so, you
should.
Here's the default {{logging.properties}} created with a broker instance. It
suppresses audit logging by default:
{noformat}
# Additional logger names to configure (root logger is always configured)
# Root logger option
loggers=org.eclipse.jetty,org.jboss.logging,org.apache.activemq.artemis.core.server,org.apache.activemq.artemis.utils,org.apache.activemq.artemis.journal,org.apache.activemq.artemis.jms.server,org.apache.activemq.artemis.integration.bootstrap,org.apache.activemq.audit.base,org.apache.activemq.audit.message
# Root logger level
logger.level=INFO
# ActiveMQ Artemis logger levels
logger.org.apache.activemq.artemis.core.server.level=INFO
logger.org.apache.activemq.artemis.journal.level=INFO
logger.org.apache.activemq.artemis.utils.level=INFO
logger.org.apache.activemq.artemis.jms.level=INFO
logger.org.apache.activemq.artemis.integration.bootstrap.level=INFO
logger.org.eclipse.jetty.level=WARN
# Root logger handlers
logger.handlers=FILE,CONSOLE
# to enable audit change the level to INFO
logger.org.apache.activemq.audit.base.level=ERROR
logger.org.apache.activemq.audit.base.handlers=AUDIT_FILE
logger.org.apache.activemq.audit.base.useParentHandlers=false
logger.org.apache.activemq.audit.message.level=ERROR
logger.org.apache.activemq.audit.message.handlers=AUDIT_FILE
logger.org.apache.activemq.audit.message.useParentHandlers=false
# Console handler configuration
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.properties=autoFlush
handler.CONSOLE.level=DEBUG
handler.CONSOLE.autoFlush=true
handler.CONSOLE.formatter=PATTERN
# File handler configuration
handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
handler.FILE.level=DEBUG
handler.FILE.properties=suffix,append,autoFlush,fileName
handler.FILE.suffix=.yyyy-MM-dd
handler.FILE.append=true
handler.FILE.autoFlush=true
handler.FILE.fileName=${artemis.instance}/log/artemis.log
handler.FILE.formatter=PATTERN
# Formatter pattern configuration
formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.PATTERN.properties=pattern
formatter.PATTERN.pattern=%d %-5p [%c] %s%E%n
#Audit logger
handler.AUDIT_FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
handler.AUDIT_FILE.level=INFO
handler.AUDIT_FILE.properties=suffix,append,autoFlush,fileName
handler.AUDIT_FILE.suffix=.yyyy-MM-dd
handler.AUDIT_FILE.append=true
handler.AUDIT_FILE.autoFlush=true
handler.AUDIT_FILE.fileName=${artemis.instance}/log/audit.log
handler.AUDIT_FILE.formatter=AUDIT_PATTERN
formatter.AUDIT_PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.AUDIT_PATTERN.properties=pattern
formatter.AUDIT_PATTERN.pattern=%d [AUDIT](%t) %s%E%n
{noformat}
Also, I've found another work-around. You can use the in-vm connector, but
you'll need to call {{InVMConnector.resetThreadPool()}} before you stop the
broker. As far as I can tell the underlying pools are kept around so all the
connections in a JVM using an in-vm connector can share them and so they don't
have to be destroyed and re-created along with connections that go up and down.
It looks like we're just not keeping track of how many connections exist as we
should probably call {{InVMConnector.resetThreadPool()}} when the last
connection is closed.
> Embedded server hangs on shutdown
> ---------------------------------
>
> Key: ARTEMIS-3071
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3071
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.16.0
> Environment: CentOS 7
> OpenJDK 11.0.9
> Reporter: Scott Ortel
> Priority: Major
> Attachments: log.txt, log2.txt
>
>
> I'm investigating switching to Artemis. I created a simple embedded broker
> and a VM connection to it. After completion, the VM hangs for 1 minute on
> exit.
> The following is the simple code:
> {code:java}
> EmbeddedActiveMQ server = new EmbeddedActiveMQ();
> server.setConfigResourcePath(xml);
> server.start();
> TransportConfiguration transportConfiguration = new
> TransportConfiguration(InVMConnectorFactory.class.getName());
> ConnectionFactory cf =
> ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF,
> transportConfiguration);
> Connection connection = cf.createConnection();
> connection.close();
> server.stop();
> {code}
> The configuration:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <configuration xmlns="urn:activemq"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="urn:activemq /tmp/artemis-configuration.xsd">
> <core xmlns="urn:activemq:core">
> <persistence-enabled>false</persistence-enabled>
> <security-enabled>false</security-enabled>
> <journal-type>NIO</journal-type>
> <journal-pool-files>1</journal-pool-files>
> <acceptors>
> <acceptor name="in-vm">vm://localhost</acceptor>
> </acceptors>
> </core>
> </configuration>
> {code}
> I have attached the log.
> Also, does anybody know why there is so much logging at {{INFO}}?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
