[Progress Communities] [Progress OpenEdge ABL] Forum Post: An unusual pasoe error in agent log: SYSTEM ERROR: Context already bound to thread ##

Status
Not open for further replies.
D

dbeavon

Guest
I was using the agent shutdown command in OEE. When I clicked the button to stop the agent, the dialog box disappeared. However the underlying process ID was *not* stopped. And in the agent log I see all this stuff: [19/06/04@11:29:04.052-0400] P-001672 T-003680 1 AS-Listener MSAS Agent Shutting Down. Status: 4020 [19/06/04@11:29:04.052-0400] P-001672 T-001084 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 15, Status: 0 [19/06/04@11:29:07.037-0400] P-001672 T-001932 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:07.037-0400] P-001672 T-001932 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 4, Status: -15 [19/06/04@11:29:08.037-0400] P-001672 T-005620 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:08.037-0400] P-001672 T-005620 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 10, Status: -15 [19/06/04@11:29:09.038-0400] P-001672 T-004988 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:09.038-0400] P-001672 T-004988 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 9, Status: -15 [19/06/04@11:29:10.042-0400] P-001672 T-002836 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:10.042-0400] P-001672 T-002836 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 6, Status: -15 [19/06/04@11:29:11.043-0400] P-001672 T-002032 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:11.043-0400] P-001672 T-002032 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 11, Status: -15 [19/06/04@11:29:12.044-0400] P-001672 T-004884 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:12.044-0400] P-001672 T-004884 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 5, Status: -15 [19/06/04@11:29:13.044-0400] P-001672 T-005916 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:13.044-0400] P-001672 T-005916 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 7, Status: -15 [19/06/04@11:29:14.045-0400] P-001672 T-002216 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:14.045-0400] P-001672 T-002216 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 16, Status: -15 [19/06/04@11:29:15.046-0400] P-001672 T-004408 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:15.046-0400] P-001672 T-004408 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 8, Status: -15 [19/06/04@11:29:16.046-0400] P-001672 T-005724 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:16.046-0400] P-001672 T-005724 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 13, Status: -15 [19/06/04@11:29:17.046-0400] P-001672 T-004332 1 AS-Aux-0 MSAS SYSTEM ERROR: Context already bound to thread 14. [19/06/04@11:29:17.046-0400] P-001672 T-004332 1 AS-Aux-0 MSAS Worker Thread exiting. Number: 12, Status: -15 I don't know of anything else that is amiss with this ABL application, other than the fact that the agent didn't want to stop when I told it to. I wasn't stopping it for any reason in particular, just to pick up new r-code and re-initialize ABL sessions. Has anyone ever seen that message (Context already bound to thread)? I'm running OE 11.7.4 on windows. The agent process is not stopping . And the OEE console that lists agents will no longer refresh (I get the spinner, and then it disappears without showing the related process). So I think the entire instance is unhappy (or at least this ABL application). I suppose the next step is to use the trusty task manager. That rarely fails to kill an agent process.

Continue reading...
 
Status
Not open for further replies.
Top