BTW you can try the latest 4.0.2 RC here http://hiramchirino.com/~chirino/incubator-activemq-4.0.2-RC6/maven1/incubator-activemq/distributions/
On 10/24/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
When the servers are back up.. I would recommend trying the latest release candidate of 4.0.2 On 10/22/06, Matthew Xie <[EMAIL PROTECTED]> wrote: > > > My problem is look like same to you. i run many producers and one consumer > to > transport messages on one queue. > after 4 or 5 days working, the consumers can't receive any messages. and > the > queue remains some messages. actually i can't send more messages to the mq > server. if i do it , it will suspend for a long time to connect or send > the > message out.(i am not sure). > here i am using activemq 4.0.1. anyone could do a favor? > > Thanks! > Matt. > > > raxlee 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#a6947375 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com
-- James ------- http://radio.weblogs.com/0112098/
