Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of straightflush@gmail.com
 designates 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=p1CntYMJNYEThkV4qUQ9O9epUmKpYTdwmgQdp+6dCfkhsSpzyVdacAUBalk/Lr3jLz
         coDOG1RdIswmhxk9cC+nUmLcpZWjKx5S/BrOXlVFD8Je5mXfo7qDLXUncQl99f9IS3lB
         bWMwOaKD6Dn6zVIGlI4Uk8vKr9w/tAGScqTxc=
MIME-Version: 1.0
In-Reply-To: <49852D99.4030105@mustardgrain.com>
References: <d9cab5bb0901312053s7b24d7dey4f2690928ae93903@mail.gmail.com>
	 <49852D99.4030105@mustardgrain.com>
Date: Sun, 1 Feb 2009 00:08:58 -0500
Message-ID: <d9cab5bb0901312108m3978017ah91eb5acd7d90d07b@mail.gmail.com>
Subject: Re: failed ActiveMQ hangs tomcat
From: AD <straightflush@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

actually i think i did notice failover() with only 1 address in
non-prod.  I think the reason that was there was some config
templating issue.

Are you saying if you remove the failover and just go straight in this
might resolve it?

Will give it a shot

Adam

On Sun, Feb 1, 2009 at 12:05 AM, Kirk True <kirk@mustardgrain.com> wrote:
> Hi Adam,
>
> AD wrote:
>>
>> hello,
>>
>>  i am running into a situation where if our JMS server is down
>> (activemq) the tomcat application does not respond at all.  Not sure
>> why tomcat is relying so heavily on this connection , any ideas as to
>> why this would be ?
>>
>>
>
> Does your ActiveMQ connection URL include the failover:// prefix? I've seen
> applications hang near-indefinitely trying to fail over to the same (downed)
> ActiveMQ server over and over again.
>
> One way to see where the actual hang is would be to get a thread dump. The
> standard 'kill -3 <pid>' of the Tomcat process (on Linux/UNIX) would do the
> trick.
>
> This sounds more like a web application issue than an issue with Tomcat.
> Also, if you have integration tests that connect to a live JMS server you
> could experiment with 'pulling the cord' and see where it hangs. This would
> then remove Tomcat from the equation.
>
> Kirk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org