On 29/01/2016 12:57, Keiichi Fujino wrote: > 2016-01-29 21:42 GMT+09:00 Mark Thomas <ma...@apache.org>: > >> On 29/01/2016 12:15, Mark Thomas wrote: >>> On 25/11/2015 08:40, kfuj...@apache.org wrote: >>>> Author: kfujino >>>> Date: Wed Nov 25 08:40:23 2015 >>>> New Revision: 1716327 >>>> >>>> URL: http://svn.apache.org/viewvc?rev=1716327&view=rev >>>> Log: >>>> Add null check for mapMember. >>> >>> This appears to create problems when the BackupManager membership is >>> configured using static membership. The static members are not visible >>> to the Channel (they are managed by the Interceptor) so this test always >>> fails and the logs fill with warnings very quickly. >> >> My analysis isn't right. The static members are visible. >> >> I've traced the problem back as far as the unique IDs not matching but I >> am still working on finding the root cause. It could be a config error >> on my part. >> >> > > I fixed this problems at r1720074. (see r1720074, r1714920 and r1714919) > Actually, this warning log output does not result in much of a problem, > because map can build the appropriate membership by the ping. > However, in order to avoid this warning log is to define the local member > and make the start-up notification on startup.
Thanks. I was getting there... I needed to update my configuration to identify the local members. Once I did that, everything was fine. Now I can look at the question that prompted me to turn on my clustering test system in the first place... Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
