Developers

[btpoole]

Is there a reason a Task debug would be showing up on port 8089 instead of 8090, 8091, 8092 or 8093. I do have one Task that generates list for a label executed on 8090. I have a second task that kicks in later. It show entering the task and runs the task but all the debug info is on port 8089.  The task does not populate the contentnode as expected and never enters the callback. Just wondering if this is a common thing.

[Veeta]

The task init() function is run in the SG main thread, so you will see debug output from init() on port 8089.  Only the task thread function, set in 'functionName' will write to other ports when it is running.

[btpoole]

Ah, that explains it. Couldn't figure why this particular task was show up in 8089.
Thanks