TQ
> 4swAniC9KhTfq6jgSJauq/X0x4pm7arC
> =9fh7
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@to
-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
2009/10/20 NabiL :
> There is no bug tomcat side. ActiveMQ is configured with Master/Slave.
> Tomca's logs indicates that ActiveMQ attempts to acquire the lock, this is
> why tomcat can't start after ActiveMQ start.
Then I would ask on an ActiveMQ list - I doubt anyone here will be
able to help yo
bscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Tomcat-wait-to-start-tp25973792p25979102.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
2009/10/20 NabiL :
> I use ActiveMQ5.3 with shared database Mysql. 2 instances shared the same
> DB.
OK. Do you have a stack trace, or otherwise know which part of whose
code is waiting to acquire the lock? There could be at least four
places:
1) Tomcat;
2) MySQL;
3) ActiveMQ;
4) Your code.
Wh
roblem rather than a Tomcat one?
>
> - Peter
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
--
View this message in context:
ssage in context:
http://www.nabble.com/Tomcat-wait-to-start-tp25973792p25976315.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
2009/10/20 NabiL :
> 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).
We will need more information in order to solve this.
Wh
quire
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 ?
Thanks in advance.
--
View this message in context:
http://www.nabble.com/Tomcat-wait-to-start-tp25973792p25973792.html
Sent from the T
