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: the consumer cant't receive message from the activemq broker
Date Wed, 18 Oct 2006 10:55:33 GMT
Could you try use 4.0.2 and see if you can reproduce these issues -
some issues were fixed to do with consumers reconnecting causing
problems.

On 10/18/06, raxlee <800919@sohu.com> wrote:
>
> hello.all
>           i run a activemq on linux os,the version of activemq is v4.0.1.i
> use the queue form .and tcp for transaction
> i just start one broker supply the service to many producers and consumers.
>          when i run a activemq test programme.the process for producer and
> consumer is with high speed.
>          but when i run my server use the activemq.after the system running
> several days,i found that the
>          consumers receive the message from the activemq with low
> speed.however,the consumer can't receive any
>          message despite there is many message remain in the queue.the
> consumers can receive the message
>          again  when i restart the activemq server.
>          i found another question:after the producer sending many messages,i
> try to close the connection.and then i
>         reconnect the activemq broker,the consumer can't receive the remain
> message in the queue.why?
>
>          i don't konw what causes that.my server is not busy from the cpu
> info and the memory.
>          my activemq.xml  like the follow
>
>         <!-- START SNIPPET: example -->
> <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">
>
>     <!--  Use the following to set the broker memory limit (in bytes)-->
>     <memoryManager>
>         <usageManager id="memory-manager" limit="204800000"/>
>     </memoryManager>
>
>     <!-- Use the following to configure how ActiveMQ is exposed in JMX
>     <managementContext>
>        <managementContext connectorPort="1099"
> jmxDomainName="org.apache.activemq"/>
>     </managementContext>
>     -->
>     <plugins>
>       <!--  use JAAS to authenticate using the login.config file on the
> classpath to configure JAAS -->
>       <jaasAuthenticationPlugin configuration="activemq-domain" />
>
>       <!--  lets configure a destination based authorization mechanism -->
>       <authorizationPlugin>
>         <map>
>           <authorizationMap>
>             <authorizationEntries>
>               <authorizationEntry queue=">" read="admins" write="admins"
> admin="admins" />
>               <authorizationEntry queue="com.moloon.smschat.server.>"
> read="users" write="users" admin="users" />
>               <authorizationEntry queue="*" read="users" write="users"
> admin="users" />
>               <authorizationEntry topic=">" read="admins" write="admins"
> admin="admins" />
>               <authorizationEntry topic="com.moloon.smschat.server.>"
> read="users" write="users" admin="users" />
>               <authorizationEntry topic="*" read="users" write="users"
> admin="users" />
>
>               <authorizationEntry topic="ActiveMQ.Advisory.>"
> read="guests,users" write="guests,users" admin="guests,users"/>
>             </authorizationEntries>
>           </authorizationMap>
>         </map>
>       </authorizationPlugin>
>     </plugins>
>  <!-- In ActiveMQ 4, you can setup destination policies -->
>     <destinationPolicy>
>       <policyMap><policyEntries>
>
>           <policyEntry topic="FOO.>">
>             <dispatchPolicy>
>               <strictOrderDispatchPolicy />
>             </dispatchPolicy>
>             <subscriptionRecoveryPolicy>
>               <lastImageSubscriptionRecoveryPolicy />
>             </subscriptionRecoveryPolicy>
>           </policyEntry>
>
>       </policyEntries></policyMap>
>     </destinationPolicy>
>
>
>     <persistenceAdapter>
>      <journaledJDBC journalLogFiles="5"
> dataDirectory="${activemq.home}/activemq-data"/>
>       <!-- To use a different datasource, use th following syntax : -->
>       <!--<journaledJDBC journalLogFiles="5" dataSource="#oracle-ds"/>-->
>     </persistenceAdapter>
>
>     <transportConnectors>
>       <transportConnector name="default"
> uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=30000" />
>       <!--<transportConnector name="default"
> uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=60000"
> discoveryUri="multic
> ast://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>
>
>        my producer.java like follow
>
>
>
> many thanks
> --
> View this message in context: http://www.nabble.com/the-consumer-cant%27t-receive-message-from-the-activemq-broker-tf2465777.html#a6873607
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 

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

Mime
View raw message