Thanks for the replies. I decided to slow down the producer and then it seems to work fine. I guess the producer was producing messages so fast that the consumer box couldn't handle them. May be the buffer was getting overwhelmed. it seems like a network or an OS issue.
So by slowing down the producer side I was able to keep the connection going for a pretty long time. I did have to restart my consumer application every so often to consume messages but the the connection between two brokers was stable. nmittler wrote: > > Is it possible you have multiple applications competing for the same port > on > the server box? Might be worth while to bring down the broker and verify > that nothing else is running on any of those ports: 61616, 61613, 61617. > > Also, you might want to disable the networkConnector until you've solved > this problem. Should help reduce the number of variables. > > Nate > > On 10/18/07, Timothy Bish <[EMAIL PROTECTED]> wrote: >> >> It helps if you also tell us what version of ActiveMQ-CPP you are using, >> but all the recent versions 2.0 and above should be fine with a v4.1.1 >> Broker. >> >> Are both clients C++ clients? >> What does you code do? >> Do you get any exceptions? >> Can you include a small sample? >> What platform / OS? >> >> Regards >> Tim. >> >> >> appi03 wrote: >> > If i am using the ActiveMQ-CPP library, does it matter what activemq >> broker >> > version do i use. Currently I am using the latest release, which is >> 4.1.1. I >> > pretty much grabbed the example from the website. Here is the >> configuration: >> > >> > <broker brokerName="localhost" useJmx="true" persistent="false" >> > xmlns="http://activemq.org/config/1.0";> >> > >> > <destinationPolicy> >> > <policyMap><policyEntries> >> > >> > <policyEntry topic="FOO.>"> >> > <dispatchPolicy> >> > <strictOrderDispatchPolicy /> >> > </dispatchPolicy> >> > <subscriptionRecoveryPolicy> >> > <lastImageSubscriptionRecoveryPolicy /> >> > </subscriptionRecoveryPolicy> >> > </policyEntry> >> > >> > </policyEntries></policyMap> >> > </destinationPolicy> >> > >> > persistenceAdapter> >> > <memoryPersistenceAdapter/> >> > <!-- <journaledJDBC journalLogFiles="5" >> > dataDirectory="${activemq.base}/activemq-data"/> --> >> > <!-- To use a different datasource, use the following syntax : >> --> >> > <!-- >> > <journaledJDBC journalLogFiles="5" >> dataDirectory="../activemq-data" >> > dataSource="#postgres-ds"/> >> > --> >> > </persistenceAdapter> >> > >> > <transportConnectors> >> > <transportConnector name="openwire" uri="tcp://localhost:61616" >> /> >> > <!-- discoveryUri="multicast://default"/> --> >> > <transportConnector name="ssl" uri="ssl://localhost:61617"/> >> > <transportConnector name="stomp" >> uri="stomp://localhost:61613"/> >> > </transportConnectors> >> > >> > <networkConnectors> >> > <!-- by default just auto discover the other brokers --> >> > <!-- <networkConnector name="default-nc" >> uri="multicast://default" >> > failover="false"/> --> >> > >> > <networkConnector name="host1" >> > uri="static://(tcp://157.185.37.184:61616)" failover="true" /> >> > <!-- >> > <networkConnector name="host1 and host2" >> > uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/> >> > --> >> > </networkConnectors> >> > >> > </broker> >> > The reason why I ask is I have a consumer and producer running on two >> > different computers connected via LAN and for some reason I keep >> loosing >> the >> > connection. Sometimes i successfully reconnects and I am able to >> receive >> the >> > messages but of the time it stops and the consumer is unable to receive >> any >> > messages. >> > >> > I feel like I am missing something here. >> > >> > I would appreciate any help. >> > >> > Thanks, >> > Arpit >> > >> >> > > -- View this message in context: http://www.nabble.com/connection-issues-tf4649649s2354.html#a13284353 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
