activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From grudi <>
Subject Re: Oracle Persistant Journal
Date Thu, 31 Aug 2006 13:31:48 GMT

We also are running the journal on Oracle and the number of Oracle processes
(which translates into connections) getting created is very high (up to
1000, our limit). We use AMQ 3.2. We discoverd, that the processes were
created when subscribing to a Topic out of a GUI Application. Each instance
of the  Application subscribes to approx 20 Topics. When you are closing one
instance of the GUI Application, the Oracle processes (connections) are not
getting released. Is each subscription to one Topic creating one Oracle
connection? How can this be avoided and are the connections getting released
automatically when unsubsricbing to a Topic?

James.Strachan wrote:
> On 8/21/06, osian <> wrote:
>> Is the JDBC pool something that is set on the BasicDataSource?
> Yes
>> Also, I'm unsure about what you mean by the nr or connections required
>> depends on the nr of connections I have.
> The number of JDBC connections required when not using the journal is
> dependent on the number of connections to the broker - unless you cap
> the limit on the number of JDBC connections used which effectively
> causes contention in the broker waiting for available JDBC
> connections. i.e. it reduces the concurrency of the broker and its
> throughput.
> If you use the high performance journal then you'll use less JDBC
> connections, since JDBC is mostly only used by a background checkpoint
> thread.
> -- 
> James
> -------

View this message in context:
Sent from the ActiveMQ - User forum at

View raw message