Return-Path: 
 <users-return-42857-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4466018795
	for <apmail-activemq-users-archive@www.apache.org>;
 Fri, 28 Aug 2015 13:44:38 +0000 (UTC)
Received: (qmail 29931 invoked by uid 500); 28 Aug 2015 13:44:37 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 29897 invoked by uid 500); 28 Aug 2015 13:44:37 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Delivered-To: moderator for users@activemq.apache.org
Received: (qmail 39270 invoked by uid 99); 28 Aug 2015 04:08:58 -0000
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 4.445
X-Spam-Level: ****
X-Spam-Status: No, score=4.445 tagged_above=-999 required=6.31
	tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2,
	SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001, URI_HEX=1.313,
	URI_TRY_3LD=0.958] autolearn=disabled
Date: Thu, 27 Aug 2015 21:03:35 -0700 (PDT)
From: thundersmurf <keith.heasman@gmail.com>
To: users@activemq.apache.org
Message-ID: <1440734615767-4701481.post@n4.nabble.com>
Subject: NMS, default AMQ settings, connection not re-established after AMQ
 process stop/start
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Wee bit o' background: I've been a java guy for a long (long) time but due to
(family) circumstance took a role with a new company on the MS wagon.  Good
experience either way. :)

I'm having difficulties with a client re-connection with the default AMQ
connection values as stated at
http://activemq.apache.org/nms/activemq-uri-configuration.html.

Scenario:
- AMQ server is up. Webapp fires up and everything is good (I can send a
test message)
- I take the AMQ server down.  Webapp (with info from the Apache.NMS.ITrace
adapter) says there's a problem.  Houston we have a problem (as expected).
- I bring the AMQ server back up.  A subsequent test message just hangs like
forever.  No good.

I tried a few different things with transport.sendTimeout and
transport.timeout but to no avail.  I'm using failover because that helped
when the asp.net app went to 'sleep' (IMO: totally odd, like MS's decision
to thread-switch in asp.net).

Example URI connection: failover:(tcp://<server
ip>:61616?transport.sendTimeout=10&amp;transport.useLogging=true)?transport.startupMaxReconnectAttempts=2

I'm probably missing something small but I'm stuck right now.  Any help is
much appreciated.

Client:
asp, .net v4.5
Apache.NMS v1.7.0.3635
Apache.NMS.ActiveMQ v 1.7.0.3660

Server (same situation is occurring on client-site with Windows Server
something-or-other):
Lubuntu
AMQ v5.10.0





--
View this message in context: http://activemq.2283324.n4.nabble.com/NMS-default-AMQ-settings-connection-not-re-established-after-AMQ-process-stop-start-tp4701481.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.