[AMQ-210] Server reconnect is not detected with peer protocol (2 peer setup only)

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0, 2.1
• Fix Version/s: 3.0

Environment

Windows XP 2000

• Assignee: Unassigned
• Reporter: Igor Kaplansky
• Created: 09/Mar/05 01:01
• Updated: 13/Apr/05 11:17
• Resolved: 13/Apr/05 11:17

Description

Steps to reproduce:

2 instances of tomcat 5.0.30, jdk 1.4.2, call it tomcat1 and tomcat2
Each instance is running a webapp with the following config: brokerURL="peer://someService", embeddedBroker=(true or false, the behaviour is the same with either setting )

Kill tomcat1: tomcat2's webapp detects the disconnect and successfully removes the client.
Restart tomcat1: tomcat2's webapp DOES NOT detect the reconnect of tomcat1's webapp or any other peer but continues to hear its own messages. In activemq2.0 it's unable to hear even its own messages.

When there are at least 3 peers in a cluster this does not occur and peers seem to detect membership changes correctly.

If I am using the peer protocol incorrectly I would greatly appreciate if you let me know. All I am trying to have is
a network of peers, each with an embedded broker to achieve transparent failover. Thanks a lot.

Igor Kaplansky