btpoole
Channel Surfer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2016
05:41 PM
Task On 8089
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.
2 REPLIES 2
Veeta
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2016
06:34 AM
Re: Task On 8089
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
Channel Surfer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2016
12:37 PM
Re: Task On 8089
Ah, that explains it. Couldn't figure why this particular task was show up in 8089.
Thanks
Thanks