• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • DSO:L2,Failover
  • etsai
  • Reporter: hhuynh
  • June 03, 2008
  • 0
  • Watchers: 0
  • July 27, 2012
  • June 03, 2008

Description

set up a cluster NAP, follow this sequence

1) Start L2A 2) Start L1 3) Kill L2A 4) Start L2A 5) Start L2B 6) Kill L2A

Will lead to this error:

2008-05-22 13:40:39,937 INFO - Unable to find communications stack. ConnectionID(0.6c11148a5b4a4387b450eaf493498be0) not found. This is usually caused by a client from a prior run trying to illegally reconnect to the server. While that client is being rejected, everything else should proceed as normal.

Logs/tc-config.xml are attached.

Comments

Fiona OShea 2008-06-03

Erh-Yuan Tsai - 29/May/08 04:54 PM Merge fix to new 2.6 branch, rev8676. Merged 8617, 8623 from trunk.