which version are you seeing this in ? - this certainly would cause
problems for durable subscribers
cheers,
Rob
On 20 Mar 2007, at 02:30, facboy wrote:
one other thing i noticed while debugging...the discovery agents
for the
network connectors don't seem to get their broker names set
correctly (not
sure if this is causing the problem, i suspect not). the discovery
agents
get instantiated when the bean definition is being parsed, at which
point
the network connectors have the default 'localhost' set for the
broker name.
later on the network connectors broker name is synchronized with
the name of
the broker they reside in, but this is never applied to the
discovery agent
within the network connector so it always has it's internal value
set to
'localhost'.
facboy wrote:
hi all,
running testing locally and i've got two instances of jboss
running, each
with a uniquely named broker and with openwire on different
ports. using
multicast discovery. i have 2 MDBs deployed on each server, each
listening to a different topic.
i get these messages constantly in the logs (and in the console):
INFO [DemandForwardingBridge] Network connection between vm://x1 and
tcp://localhost/127.0.0.1:63636(x2) has been established.
is this normal? do they more or less coincide with the MDBs
'polling' the
topic?
--
View this message in context: http://www.nabble.com/constant-%
27DemandForwardingBridge%27-Network-Connection-established-
messages--tf3430941s2354.html#a9565170
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
