tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Tomcat wait to start
Date Tue, 20 Oct 2009 18:00:30 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

NabiL,

On 10/20/2009 7:57 AM, NabiL wrote:
> I use Tomcat 6.x running on server A (Linux redhat 5). i deployed a AMQ war
> file. This application is waiting to acquire a lock because i run
> successfully the same application on another server B (Linux + Tomcat 6).
> Now if i try to restart tomcat A, it can't start because attempts to acquire
> lock, with this situation all application deployed on this tomcat server is
> impacted. 
> 
> How can i avoid this situation and tomcat A continue to start ?

One solution is to use "lazy" or "delayed" initialization of this
resource. That allows your webapp to start up completely even when the
required resource isn't available. Whenever you need that resource, you
go ahead and connect to it. If it's not available, you throw an error
and try again next time.

This greatly reduces problems with bi-directional dependencies between
web applications (or any other components for that matter).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrd+r4ACgkQ9CaO5/Lv0PDH0ACeKAiyLtGgpRjoH4f5vCTL19TQ
4swAniC9KhTfq6jgSJauq/X0x4pm7arC
=9fh7
-----END PGP SIGNATURE-----

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


Mime
View raw message