Hi Nick, i really "kill" it by "killall -9 java" so you normally can be sure, there is no JVM left. In my eyes, it isn't the Responder, who makes the mistake. For me it seems to be the component, who sends the ping... But I would be glad if you would send me your patch, maybe it fixes my trouble too..
Regards, Malte > Hi Malte, > > Are you embedding the controller in a JVM with other applications? > if so beware that the PingResponder is *not* shutdown when > Controller.shutdown(); is called. It just because you write > "killed" (quoted)... > > Also the SEQUOIA-981 issue has already been entered for this problem. > > Regards, > > Nick > > On Tue, 2007-11-13 at 10:39, [EMAIL PROTECTED] wrote: >> I test around with a few virtualdatabases and two Controllers, >> when I "killed" the one controller and startet it again, the two >> controllers begin to "ping" around. >> There is only pinging in the log, the whole time: >> 2007-11-13 10:30:04,838 DEBUG controller.core.Controller Received ping >> data from /10.96.xx.xx >> 2007-11-13 10:30:04,838 DEBUG controller.core.Controller Response to >> ping >> sent to /10.96.xx.xx >> >> My investigations showed, that the response seem to come from the >> PingResponder, but who sends the pings and why didn't he stop it, after >> a >> while? >> Can anyone give me a hint? >> >> Best regards, >> >> Malte >> >> _______________________________________________ >> Sequoia mailing list >> [email protected] >> https://forge.continuent.org/mailman/listinfo/sequoia > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia > _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
