Comment #8 on issue 2504 by brainslog: JDiameter: change disconnect-cause
http://code.google.com/p/mobicents/issues/detail?id=2504

Hi Bastien,

It's not a real problem, just seems a bit inadequate to provide a disconnect reason in destroy method (where stack should be stopped, thus not connected). The proper lifecycle methods should be invoked by it's order and not skipping steps such as calling destroy without stopping, for guaranteeing a graceful stop.

Reply via email to