Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 78065 invoked from network); 4 Jan 2008 21:10:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jan 2008 21:10:11 -0000 Received: (qmail 30162 invoked by uid 500); 4 Jan 2008 21:09:59 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 30139 invoked by uid 500); 4 Jan 2008 21:09:59 -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 30130 invoked by uid 99); 4 Jan 2008 21:09:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 13:09:59 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 72.14.252.159 as permitted sender) Received: from [72.14.252.159] (HELO po-out-1718.google.com) (72.14.252.159) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 21:09:34 +0000 Received: by po-out-1718.google.com with SMTP id c31so5667649poi.1 for ; Fri, 04 Jan 2008 13:09:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=ETs/c2Pn+HLueZSuF2MugQYGBnG2qr8Ssoga5BY2WQQ=; b=WgKFDoMwKGWiOxlBmK8iEUDlEIXiOY1RKs2wOH8Ww+0NTAFNlwY4uHimJkd8d45aOhEQNwdj7Li+Ulxr0RnmnF6wXSeDVVCw0TDtFd4dIUxvhGtLA0mumWIQ7rTsbpEhEmwBSuj3EPN9rluOl7AL40oKR1VJp7+8YiXjQHfjBRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=oiZ0sk4fUWbirhfYBVj1GlDU90K6SlAVYs6yEqdbyK28jHYym6/1nx7MNhrois7Gr+jHNVzuofTlrwHm8d0zz0Vp7z4II8IRDSgJAP/EEWZZKZ8CHpRvExTX28armdKLX1Diz+nK4aJcXk5ltYNWErwY2ivd3mKwkBxMgfPJZPQ= Received: by 10.114.125.2 with SMTP id x2mr359183wac.119.1199480979090; Fri, 04 Jan 2008 13:09:39 -0800 (PST) Received: by 10.114.160.2 with HTTP; Fri, 4 Jan 2008 13:09:39 -0800 (PST) Message-ID: Date: Fri, 4 Jan 2008 16:09:39 -0500 From: "Hiram Chirino" Sender: chirino@gmail.com To: users@activemq.apache.org Subject: Re: ActiveMQ Slave loops for lock, preventing JBoss to continue deployment In-Reply-To: <14604762.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <14604762.post@talk.nabble.com> X-Google-Sender-Auth: 85ab1323c0ecfdc6 X-Virus-Checked: Checked by ClamAV on apache.org Yep we have an issue open about it already: http://issues.apache.org/activemq/browse/AMQ-1519 On Jan 3, 2008 3:41 PM, aarvee wrote: > > I have embedded ActiveMQ 5.0.0 (with Master-Slave Shared File System config.) > in JBoss using the suggested RAR approach. > > I am using two JBoss instances in a JBoss HA Cluster. > The first JBoss instance (with ActiveMQ Master) comes up fine. > > However on start, the second JBoss instance does not complete deployment > because the ActiveMQ Slave is forever looping to get the Shared File System > lock. > > "org.apache.activemq.store.journal.JournalPersistenceAdapterFactory - > Journal is locked... waiting 10 seconds for the journal to be unlocked" > > Is there a way this looping check be in a background thread, so that other > Jboss deployed components like EJBs, MBeans, Servlets etc. can come up ? > > In our configuration, only the JMS Q is HA Master-Slave; the other > components are Active-Active. > > Thanks for any help ! > > P.S. The Message Groups feature is awesome. Thanks ! > > > > > > > -- > View this message in context: http://www.nabble.com/ActiveMQ-Slave-loops-for-lock%2C-preventing-JBoss-to-continue-deployment-tp14604762s2354p14604762.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com