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: ActiveMq (JMS) API call Send hangs after certain number of sends.
Date Fri, 23 Feb 2007 05:48:38 GMT
I'm not sure - what does the current system state look like in JMX?
(How many consumers, what their status is etc)


On 2/20/07, suri009 <surya.nandigam@diagonal-consulting.com> wrote:
>
>
> My Server app is sending 1 to 2MB of data (as java object) every 2-10
> seconds to java swing clients using ActiveMq. I  have 10 java clients
> connected to activeMq broker. I am using 10Mbit network connection to send
> data to clients.
>
> Configuration:
>
> 1) I configured JVM size (Xmx) as 2048M and 1G user manager. My activeMq XMl
> as follows:
>
> <beans xmlns="http://activemq.org/config/1.0">
>
>   <!-- Allows us to use system properties as variables in this configuration
> file -->
>   <bean
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
>
>   <broker useJmx="true" persistent="false" >
>
>     <!--  Use the following to set the broker memory limit (in bytes) -->
>     <memoryManager>
>         <usageManager id="memory-manager" limit="1000000000"/>
>     </memoryManager>
>
>
>     <!-- Use the following to configure how ActiveMQ is exposed in JMX -->
>     <managementContext>
>        <managementContext connectorPort="1099"
> jmxDomainName="org.apache.activemq"/>
>     </managementContext>
>
>
>     <!-- In ActiveMQ 4, you can setup destination policies -->
>     <destinationPolicy>
>       <policyMap><policyEntries>
>
>           <policyEntry topic="FOO.>">
>             <dispatchPolicy>
>               <strictOrderDispatchPolicy />
>             </dispatchPolicy>
>             <subscriptionRecoveryPolicy>
>               <lastImageSubscriptionRecoveryPolicy />
>             </subscriptionRecoveryPolicy>
>           </policyEntry>
>
>       </policyEntries></policyMap>
>     </destinationPolicy>
>
>     <transportConnectors>
>        <transportConnector name="default"
> uri="tcp://192.168.15.1:61616?soTimeout=10000&amp;connectionTimeout=30000"
> discoveryUri="multicast://192.168.15.1"/>
>     </transportConnectors>
>
>   </broker>
> </beans>
>
> 2) Server App connects to ActiveMq broker using:
>
> TopicConnectionFactory connFactory = new
> ActiveMQConnectionFactory(ActiveMQConnection.DEFAULT_USER,
> ActiveMQConnection.DEFAULT_PASSWORD, "failover:(tcp://192.168.15.1:61616)?
> jms.useAsyncSend=true&amp;disableTimeStampsByDefault=true&amp;wireFormat.maxInactivityDuration=0");
>
> I am using non-persistent topic to send messages to broker.
>
>
> 3) Clients connect to ActiveMq broker using:
>
> TopicConnectionFactory connFactory = new
> ActiveMQConnectionFactory(ActiveMQConnection.DEFAULT_USER,
> ActiveMQConnection.DEFAULT_PASSWORD,
> "failover:(tcp://192.168.15.1:61616)?wireFormat.maxInactivityDuration=0");
>
> 4) Sending the data using the call:
>
> ObjectMessage objMsg = session.createObjectMessage(message);
> sender.send(objMsg, DeliveryMode.NON_PERSISTENT, 0, 0);
>
> Now, the problem is JMS API call send hangs after 8-10 hours and my clients
> are not able to receive any data from ActiveMq Broker.
>
> Could anybody help me, why JMS API call 'send' seems to be hanging after
> 8-10 hours?
>
>
>
>
>
>
> --
> View this message in context: http://www.nabble.com/ActiveMq-%28JMS%29-API-call-Send-hangs-after-certain-number-of-sends.-tf3261072s2354.html#a9063500
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

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

Mime
View raw message