Symptom
- Job Scheduler doesn't work
- Try stopping/starting job scheduler with command below, command always hang and can't be killed:
use sybmgmtdb
go
exec sp_sjobcontrol @name=NULL,@option="stop_js"
go
exec sp_sjobcontrol @name=NULL,@option="start_js"
go - JSAGENT log not updated for stop/start attempts, and was last updated with messages like:
jamain Message number: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
jamain Message String: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
jamain OS Error: Socket connect failed - errno 111 Connection refused
jamain ct_connect() failed.
jamain jsj_AddConxs: jsd_MakeConnection() failed for user jstask to server SID
jamain jsj_AddConxs() failed. jsj_ReleaseConx() failed to replace dead connection. Connection pool size decremented.
jamain jsj__ReplaceConx() failed
jamain All JS task connections have been lost.
jamain JS Agent aborting. Cancel all running jobs. - In OS level jsagent process has been running for a quite long time, the start time of the process not updated though ASE server had been restarted, command to check:
ps -ef | grep jsagent
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0 SP04 PL02
- Linux on x86_64 64bit
Product
SAP Adaptive Server Enterprise 16.0
Keywords
sybase, jobscheduler, JS, schedule, DB13, cockpit, working , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.