[ 
https://issues.apache.org/jira/browse/ARTEMIS-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267454#comment-17267454
 ] 

Scott Ortel edited comment on ARTEMIS-3071 at 1/18/21, 6:28 PM:
----------------------------------------------------------------

Thanks for looking at this [~jbertram] .  I'm glad that you were able to 
reproduce the error.  I changed the URL and connection method as you indicated. 
 The tcp connection worked and did not hang.

I'll continue to help troubleshoot the InVMConnector.  So far it seems nothing 
shutsdown the threadPoolExecutor.

 

On a side note, logging is still odd.  I still get INFO audit logging using the 
example logging.properties from the Logging documentation.  The following are 
my settings.

main:
{code:java}
System.setProperty("java.util.logging.manager","org.jboss.logmanager.LogManager");
System.setProperty("logging.configuration", "file:///tmp/logging.properties");
{code}
/tmp/logging.properties (contains Logging docs example, +plus+ the following to 
try to prevent INFO audit messages but still had no effect):
{code:java}
logger.org.apache.activemq.audit.base.level=ERROR
logger.org.apache.activemq.audit.resource.level=ERROR
logger.org.apache.activemq.audit.message.level=ERROR{code}
 


was (Author: sortel):
Thanks for look at this [~jbertram] .  I'm glad that you were able to reproduce 
the error.  I changed the URL and connection method as you indicated.  The tcp 
connection worked and did not hang.

I'll continue to help troubleshoot the InVMConnector.  So far it seems nothing 
shutsdown the threadPoolExecutor.

 

On a side note, logging is still odd.  I still get INFO audit logging using the 
example logging.properties from the Logging documentation.  The following are 
my settings.

main:
{code:java}
System.setProperty("java.util.logging.manager","org.jboss.logmanager.LogManager");
System.setProperty("logging.configuration", "file:///tmp/logging.properties");
{code}
/tmp/logging.properties (contains Logging docs example, +plus+ the following to 
try to prevent INFO audit messages but still had no effect):
{code:java}
logger.org.apache.activemq.audit.base.level=ERROR
logger.org.apache.activemq.audit.resource.level=ERROR
logger.org.apache.activemq.audit.message.level=ERROR{code}
 

> 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)

Reply via email to