activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Activemq broker hangs when stomp client disconnects unexpectedly
Date Tue, 10 Nov 2009 14:49:48 GMT
have a look at http://activemq.apache.org/slow-consumer-handling.html

with persistence=false, no disk spooling will occur so all messages
will remain in memory unless you add some discard policy.
what is a little odd is that the broker still thinks there is a
consumer, you may need to configure some timeouts. What does netstat
or the console say about the connection from your client?

2009/11/10 SelvarajAM <selvarajam@hcl.in>:
>
> Hi,
>
> I am using embedded Activemq broker (5.3 Version), Flex client and STOMP
> protocol for the communication.
>
> The problem is,
>
> When unexpected error occurs in the Flex client, Activemq broker  memory
> usage increases gradually and then it hangs giving the following message in
> the log file
>
> Memory usage change from: 1% of available memory, to: 2% of available memory
> .
> .
> .
> Memory usage change from: 99% of available memory, to: 100% of available
> memory
>
> Usage Manager memory limit reached for topic://a. Producers will be
> throttled to the rate at which messages are removed from this destination to
> prevent flooding it. See
> http://activemq.apache.org/producer-flow-control.html for more info
>
> Below is the xml configuration we use
>
> <beans
>  xmlns="http://www.springframework.org/schema/beans"
>  xmlns:amq="http://activemq.apache.org/schema/core"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>  http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd">
>
>
>    <!--
>        The <broker> element is used to configure the ActiveMQ broker.
>    -->
>    <broker xmlns="http://activemq.apache.org/schema/core"
> persistent="false" useJmx="true"  brokerName="PRI" >
>        <transportConnectors>
>                        <transportConnector name="Stomp" uri="stomp://0.0.0.0:8084"/>
>                        <transportConnector name="Nio" uri="nio://0.0.0.0:8086"/>
>                        <transportConnector name="Tcp" uri="tcp://0.0.0.0:8087"/>
>        </transportConnectors>
>    </broker>
> </beans>
>
> We use NON-PERSISTENT messages and send to topic. The client listens to the
> topic and process the message.
>
> The jconsole shows the broker MemoryPercentUsage as 100% when activemq
> hangs.
>
> Why does an error in client crashes the Activemq server??? Do anyone face
> the same issue??
>
> Only restarting the broker helps.
> I haved changed a lot of modification in the xml configuration but could not
> find the root cause.
>
> Kindly help me on this as this is a production issue.
>
> --
> View this message in context: http://old.nabble.com/Activemq-broker-hangs-when-stomp-client-disconnects-unexpectedly-tp26283384p26283384.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Mime
View raw message