Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <22983405.post@talk.nabble.com>
Date: Thu, 9 Apr 2009 22:40:46 -0700 (PDT)
From: Raj_New <rsr_123@yahoo.co.in>
To: users@activemq.apache.org
Subject: Re: Embedded Broker shuts down automatically AMQ5.2
In-Reply-To: <3a73c17c0904090540h2e223713n6dc6fda476ad96c2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <22965564.post@talk.nabble.com> <22967169.post@talk.nabble.com>
 <36e91d9d0904090450u3f679438s5f44fa8d72354174@mail.gmail.com>
 <3a73c17c0904090540h2e223713n6dc6fda476ad96c2@mail.gmail.com>


Thanks Dejan and Gary for your quick responses.... For stale connection
problem as suggested by Gary I set minimum connection for data source as
zero and purge policy as entire pool. Hope this will resolve my problem but
I have to wait for some days. 

I am not sure about Dejan's suggestion how to implement amq persistance
instead of database as we have some audit utilities which fetches data from
database.


Also I just want to know that the below problem is coming by stale
connections or any thing else ?


4/8/09 0:04:15:030 CDT] 00000029 SystemOut     O  WARN [Journal checkpoint
worker] (org.apache.activemq.store.jdbc.TransactionContext:close:138) -
Close failed: Already closed.
java.sql.SQLException: Already closed.


Gary Tully wrote:
> 
> also, check if there are timeout options on the
>  com.ibm.db2.jcc.DB2Driver w.r.t connections or if there is a keepalive
> option in commons pooling that will discard an expired connection.
> 
> My assumption is that the database connections in the pool are getting
> stale
> in some way.
> 
> 
> 2009/4/9 Dejan Bosanac <dejan@nighttale.net>
> 
>> Hi,
>>
>> there is a lot of db2 specific exceptions in your log, so it looks like
>> the
>> broker loses the connection to the database (and/or cannot obtain the
>> lock).
>> If your connection to the database is unstable, maybe you can consider
>> amq
>> persistance store instead?
>>
>> Cheers
>> --
>> Dejan Bosanac
>>
>> Open Source Integration - http://fusesource.com/
>> ActiveMQ in Action - http://www.manning.com/snyder/
>> Blog - http://www.nighttale.net
>>
>>
>> On Thu, Apr 9, 2009 at 11:13 AM, Raj_New <rsr_123@yahoo.co.in> wrote:
>>
>> >
>> > I know my above message is really lenthy....Sorry but I need answer for
>> > this
>> > behaviour of AMQ...why its work fine for couple of days and then
>> suddenly
>> > breaks down.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://www.nabble.com/Embedded-Broker-shuts-down-automatically-AMQ5.2-tp22965564p22967169.html
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >
>> >
>>
> 
> 
> 
> -- 
> http://blog.garytully.com
> 
> Open Source SOA
> http://FUSESource.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Embedded-Broker-shuts-down-automatically-AMQ5.2-tp22965564p22983405.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.