You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by millea1 <am...@simplestar.com> on 2006/07/26 19:36:09 UTC
Re: [activemq-user] Re: ActiveMW 3.2-M1: total started threads
count go
Couldn't find where the linearly rising thread start count was addressed. Is
there a known explanation for this anyone would care to relate?
Thanks,
Allen
--
View this message in context: http://www.nabble.com/-activemq-user---ActiveMW-3.2-M1%3A-total-started-threads-count-goes-up%2C-up-and-away...-tf365471.html#a5507695
Sent from the ActiveMQ - User forum at Nabble.com.
Re: [activemq-user] Re: ActiveMW 3.2-M1: total started threads
count go
Posted by millea1 <am...@simplestar.com>.
I guess I don't know how not to produce it. It's a relatively straightforward
setup; Tomcat5.0, Spring 1.x, Java 1.4, vm transport implementation with
only one queue:
<beans xmlns="http://activemq.org/config/1.0">
<bean id="configurer1"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location" value="classpath:springXml.properties">
</property>
</bean>
<!-- ====================================================================
-->
<!-- ActiveMQ Broker Configuration -->
<!-- ====================================================================
-->
<broker useJmx="true" persistent="true"
brokerName="${psc.amq.broker.name}">
<destinationPolicy>
<policyMap><policyEntries>
<policyEntry queue="${psc.amq.email.in.queue.name}">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries></policyMap>
</destinationPolicy>
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="${psc.amq.data.directory}" dataSource="#mysql-ds">
</journaledJDBC>
</persistenceAdapter>
</broker>
<!-- ====================================================================
-->
<!-- JDBC DataSource Configurations -->
<!-- ====================================================================
-->
<!-- The MYSQL Datasource that will be used by the Broker -->
<bean id="mysql-ds"
class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName"
value="${psc.amq.db.driver.class.name}"/>
<property name="url" value="${psc.amq.db.url}"/>
<property name="username" value="${psc.amq.db.user}"/>
<property name="password" value="${psc.amq.db.password}"/>
<property name="poolPreparedStatements" value="true"/>
</bean>
</beans>
>From the spring config:
<bean id="jencks" class="org.jencks.JCAContainer" singleton="true">
<property name="bootstrapContext">
<bean class="org.jencks.factory.BootstrapContextFactoryBean">
<property name="threadPoolSize" value="25"/>
</bean>
</property>
<property name="resourceAdapter"><ref
local="jmsResourceAdapter"/></property>
</bean>
<bean id="jmsConnectionManager"
class="org.jencks.factory.ConnectionManagerFactoryBean">
<property name="transactionSupport"><ref
local="jmsTransactionSupport"/></property>
<property name="poolingSupport"><ref
local="jmsPoolingSupport"/></property>
</bean>
<bean id="jmsResourceAdapter"
class="org.apache.activemq.ra.ActiveMQResourceAdapter">
<property name="serverUrl" value="vm://beer"/>
<property
name="initialRedeliveryDelay"><value>30000</value></property>
<property name="maximumRedeliveries"><value>3</value></property>
<property
name="redeliveryBackOffMultiplier"><value>2</value></property>
<property
name="redeliveryUseExponentialBackOff"><value>true</value></property>
<property name="allPrefetchValues"><value>1</value></property>
</bean>
<bean id="jmsManagedConnectionFactory"
class="org.apache.activemq.ra.ActiveMQManagedConnectionFactory">
<property name="resourceAdapter"><ref
local="jmsResourceAdapter"/></property>
</bean>
<bean id="jmsOutConnectionFactory"
class="org.springframework.jca.support.LocalConnectionFactoryBean">
<property name="managedConnectionFactory"><ref
local="jmsManagedConnectionFactory"/></property>
<property name="connectionManager"><ref
local="jmsConnectionManager"/></property>
</bean>
--
View this message in context: http://www.nabble.com/-activemq-user---ActiveMW-3.2-M1%3A-total-started-threads-count-goes-up%2C-up-and-away...-tf365471.html#a5524147
Sent from the ActiveMQ - User forum at Nabble.com.
Re: [activemq-user] Re: ActiveMW 3.2-M1: total started threads count go
Posted by James Strachan <ja...@gmail.com>.
How do you reproduce it?
On 7/26/06, millea1 <am...@simplestar.com> wrote:
>
> hit that enter key too soon...we are on 4.0.1 and see the same behavior.
> --
> View this message in context: http://www.nabble.com/-activemq-user---ActiveMW-3.2-M1%3A-total-started-threads-count-goes-up%2C-up-and-away...-tf365471.html#a5507960
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: [activemq-user] Re: ActiveMW 3.2-M1: total started threads
count go
Posted by millea1 <am...@simplestar.com>.
hit that enter key too soon...we are on 4.0.1 and see the same behavior.
--
View this message in context: http://www.nabble.com/-activemq-user---ActiveMW-3.2-M1%3A-total-started-threads-count-goes-up%2C-up-and-away...-tf365471.html#a5507960
Sent from the ActiveMQ - User forum at Nabble.com.
Re: [activemq-user] Re: ActiveMW 3.2-M1: total started threads count go
Posted by Hiram Chirino <hi...@hiramchirino.com>.
ActiveMQ 3.2 is a bit old, I would recommend you upgrade to 4.0.1 which is
much more stable.
On 7/26/06, millea1 <am...@simplestar.com> wrote:
>
>
> Couldn't find where the linearly rising thread start count was addressed.
> Is
> there a known explanation for this anyone would care to relate?
>
> Thanks,
> Allen
> --
> View this message in context:
> http://www.nabble.com/-activemq-user---ActiveMW-3.2-M1%3A-total-started-threads-count-goes-up%2C-up-and-away...-tf365471.html#a5507695
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com