activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: AMQ 4.0.1 Memory Leak/Hang
Date Tue, 04 Jul 2006 10:50:12 GMT
BTW this use case is a very inefficient use of JMS...

http://incubator.apache.org/activemq/how-do-i-use-jms-efficiently.html

Which version of ActiveMQ are you using and can we see your Java code?
Are you using networks or temporary destinations or just reusing the
same destination? Using queues/topics/persistence - what
acknoweldgement/transacted mode etc?


On 7/4/06, Dave cawthorn <dave.cawthorn@empired.com> wrote:
>
> Hi,
>
> I have a simple test case that is failing at the moment. It goes like this
>
> 1 create a connection/session/producer
> 2 create a connection/session/consumer
> 3 create a message and send
> 4 readnext message on the consumer
> 5 close every thing
> 6 loop from 1 again
>
> I've tried to configure amq to use persistence so I wont run into memory
> problems (and can support failover with a replicated message store) but when
> i run the test it just consumes memory (amq jvm) till it hangs the client
> when trying to create a session.
>
> here is my config - any ideas?
>
>
> <!-- START SNIPPET: xbean -->
> <beans xmlns="http://activemq.org/config/1.0">
>
>   <broker persistent="true" useJmx="false">
>
>
>         <memoryManager>
>                 <usageManager id="memory-manager" limit="100000000"/>
>         </memoryManager>
>
>
>
>         <managementContext>
>            <managementContext connectorPort="1199"
> jmxDomainName="org.apache.activemq"/>
>         </managementContext>
>
>
>         <!-- In ActiveMQ 4, you can setup destination policies -->
>     <destinationPolicy>
>       <policyMap><policyEntries>
>           <policyEntry topic=">" memoryLimit="50000000"/>
>           <policyEntry queue=">" memoryLimit="50000000"/>
>       </policyEntries></policyMap>
>     </destinationPolicy>
>
>
>     <persistenceAdapter>
>      <jdbcPersistenceAdapter dataSource="#sequoia-ds" />
>     </persistenceAdapter>
>
>
>
>     <transportConnectors>
>        <transportConnector name="default" uri="tcp://localhost:61616"
> discoveryUri="multicast://default"/>
>        <transportConnector name="stomp"   uri="stomp://localhost:61613"/>
>     </transportConnectors>
>
>     <networkConnectors>
>       <!-- by default just auto discover the other brokers
>       <networkConnector name="default" uri="multicast://default"/> -->
>       <!--
>       <networkConnector name="host1 and host2"
> uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/>
>       -->
>     </networkConnectors>
>
>   </broker>
>
>   <!--  This xbean configuration file supports all the standard spring xml
> configuration options -->
>
>   <!-- Postgres DataSource Sample Setup -->
>
>
>
>
>
>
> <bean id="sequoia-ds" class="com.mchange.v2.c3p0.ComboPooledDataSource"
> destroy-method="close">
>     <property name="driverClass"
> value="org.continuent.sequoia.driver.Driver" />
>     <property name="jdbcUrl" value="jdbc:sequoia://192.168.100.9/vieo_ccs"
> />
>     <property name="user" value="postgres" />
>     <property name="password" value="postgres" />
>     <property name="minPoolSize" value ="6" />
>     <property name="maxPoolSize" value="18" />
>     <property name="acquireIncrement" value="3" />
>   </bean>
>
>
> </beans>
>
> --
> View this message in context: http://www.nabble.com/AMQ-4.0.1-Memory-Leak-Hang-tf1889180.html#a5165212
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message