Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62D831844C for ; Thu, 10 Dec 2015 07:03:11 +0000 (UTC) Received: (qmail 53248 invoked by uid 500); 10 Dec 2015 07:03:11 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 53143 invoked by uid 500); 10 Dec 2015 07:03:11 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 53121 invoked by uid 99); 10 Dec 2015 07:03:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 07:03:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EEE2A2C1F57 for ; Thu, 10 Dec 2015 07:03:10 +0000 (UTC) Date: Thu, 10 Dec 2015 07:03:10 +0000 (UTC) From: "Michal Toth (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ARTEMIS-318) Allow extra settings on command line (remote JMX & binding port already in use when stopping broker) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Michal Toth created ARTEMIS-318: ----------------------------------- Summary: Allow extra settings on command line (remote JMX & binding port already in use when stopping broker) Key: ARTEMIS-318 URL: https://issues.apache.org/jira/browse/ARTEMIS-318 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 1.1.0 Environment: all Reporter: Michal Toth I have been using remote JMX with Artemis for few weeks so far, but lately, I have noticed, that I am not able to shutdown the Artemis gracefully via 'artemis stop' nor 'artemis-service stop' when JMX is set up. Here is my scenario: 1) Add system properties to java (/etc/artemis.profile): JAVA_ARGS+="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false " 2) Start the broker 3) Do JMX "queries", send messages, everything works fine 4) bin/artemis stop Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 1099; nested exception is: java.net.BindException: Address already in use It does not matter what port number I use. Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 3099; nested exception is: java.net.BindException: Address already in use 5) I have kill the artemis process (SIGTERM is sufficient) to stop it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)