[jira] Updated: (AMQ-1234) Broker fails to dispatch messages

["Rob Davies (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-1234:
----------------------------

    Priority: Major  (was: Critical)

> Broker fails to dispatch messages
> ---------------------------------
>
>                 Key: AMQ-1234
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1234
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.0
>         Environment: OS: Redhat Linux 2.6.9-42.0.8.ELsmp
> Java 1.5.0.11
> ActiveMQ 4.1.1
>            Reporter: robert balahura
>             Fix For: 5.2.0
>
>
> We have a 5 server configuration where initially we were going to run
> the activemq broker on 2 machines and have the other 3 connect to
> those accordingly.
> We were using a connection url like the following:
> failover:tcp://brokerhost:61616
> The failover portion indicates to activemq to automatically reconnect
> should network interruptions occur.  All our producer / consumer
> objects extend a connection which remains constant throughout the
> operation.  If the network is interrupted the connection does indeed
> reconnect and continue when the network returns.
> We've configured the broker to only use an openwire connector (ssl and
> stomp are disabled)
> Description of problem:
> After several hours (between 7 and 12 hours), it seems as if the
> broker port disappears and messages produced just go nowhere.
> Consumers continue to run, however never consuming anything.  They
> indication the connection is find and they are waiting on the queue.
> No errors ever occur in either producer, consumer or broker.
> We have changed the config slightly with seeming success.  Instead of
> running two brokers, we now run 5.  One on every machine, with the
> multicast auto discovery system enabled. Every producer / consumer now
> connects to localhost instead.
> This is also very acceptable, however we would like to know why a
> sustained connection cannot be maintained to a local area network
> host.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.