Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EFD98200CBA for ; Mon, 3 Jul 2017 08:35:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EDE6E160BEC; Mon, 3 Jul 2017 06:35:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3F682160BE4 for ; Mon, 3 Jul 2017 08:35:36 +0200 (CEST) Received: (qmail 66129 invoked by uid 500); 3 Jul 2017 06:35:34 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 66118 invoked by uid 99); 3 Jul 2017 06:35:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jul 2017 06:35:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D7575C023D for ; Mon, 3 Jul 2017 06:35:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.487 X-Spam-Level: *** X-Spam-Status: No, score=3.487 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id KvdvIawwmmog for ; Mon, 3 Jul 2017 06:35:33 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6949F5F397 for ; Mon, 3 Jul 2017 06:35:32 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id A00804F702AC4 for ; Sun, 2 Jul 2017 23:35:31 -0700 (MST) Date: Sun, 2 Jul 2017 23:17:29 -0700 (PDT) From: jochenw To: users@activemq.apache.org Message-ID: <1499062649835-4728188.post@n4.nabble.com> Subject: PooledConnectionFactory: createConnection results in log entry "Successfully connected to ..." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 03 Jul 2017 06:35:37 -0000 Hello, I'm just starting using the PooledConnectionFactory. Before calling the start() method, the idleTimeout (30000 ms), the maxConnections (10) and the maximumActiveSessionPerConnection (500) are set. I would have expected that on startup, 10 connections are opened to the broker (tcp://0.0.0.0:61616), and these 10 connections are used when I start sending messages. However, on each pooledConnectionFactory.createConnection(), there is another entry in the log "Successfully connected to tcp://0.0.0.0:61616". It this log entry also appearing when creating a connection to a connection pool although no new broker connection is opened? Or does this mean that a new connection is set up to the broker - indicating that I did something wrong when using the connection pool? Regards, Jochen -- View this message in context: http://activemq.2283324.n4.nabble.com/PooledConnectionFactory-createConnection-results-in-log-entry-Successfully-connected-to-tp4728188.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.