Softpedia >Windows >Others >Scheduling >Job Scheduler >  Changelog

Job Scheduler Changelog

What's new in Job Scheduler 1.12.9

Apr 16, 2019
  • LTS Maintenance Release 1.12.9

New in Job Scheduler 1.12.7 (Oct 24, 2018)

  • Fixed:
  • Order steps should be considered successful if a task's exit code is handled by <on_return_code> configuration 23/Oct/18
  • Universal Agent should not eat inotify user_instances 23/Oct/18
  • Web service ./api/order?return=JocOrderStatistics should also work for distributed orders with PostgreSQL

New in Job Scheduler 1.12.6 (Oct 5, 2018)

  • Feature:
  • [JS-1796] - Order's state_text should be deleted when Order is reinitialized
  • [JS-1798] - Provide a script for administrators to purge the Audit Log
  • [JS-1799] - Provide MariaDB JDBC Driver version 2.2.6 with JobScheduler Master and JOC Cockpit
  • Fix:
  • [JS-1785] - Change to a holidays file that is included in a schedule triggers an infinite loop
  • [JS-1786] - Environment variables should be substituted when used with include file references
  • [JS-1788] - idletimeout=0 should create a new task for each job start.
  • [JS-1791] - Plugin threads should use new EventPublisher to publish CustomEvent
  • [JS-1792] - Web service /api/order?return=JocOrderStatistics fixed

New in Job Scheduler 1.12.5 (Aug 14, 2018)

  • Fix:
  • [JS-1772] - JobScheduler should not crash if all nodes of a nested job chain are skipped
  • [JS-1776] - The value of the java_class_path attribute should be prepended to the existing class_path
  • [JS-1780] - Error SOS-1270 should not log as error with PostgreSQL while a new order history id is created
  • [JS-1782] - No order will be executed before idle_timeout is reached when job chain has a process class
  • [JS-1783] - JobScheduler hangs with error SCHEDULER-188 Order.setback() and Order.state= cannot be combined

New in Job Scheduler 1.12.4 (Jun 26, 2018)

  • Fix:
  • [JS-1779] - After a longer JobScheduler Master Pause orders take a long time to start

New in Job Scheduler 1.12.3 (May 19, 2018)

  • Fix:
  • JobScheduler and Agent Web Services for Unix operational with Java 9 and 10
  • JobScheduler engine requires wrong version GLIBC_2.14

New in Job Scheduler 1.12.2 (Mar 28, 2018)

  • JobScheduler Master, Agent and JOC Cockpit are operational with Java 1.9Job Chain node parameters can be specified for nodes on a Universal Agent with state/param

New in Job Scheduler 1.12.1 (Feb 21, 2018)

  • Feature:
  • JOC Cockpit Session Management for active clustering with load balancers
  • PowerShell CLI for PowerShell Core 6.0 with Windows and Linux
  • Fix:
  • Agent should consider -job-java-options command line option

New in Job Scheduler 1.12.0 (Dec 28, 2017)

  • Deprecation:
  • [JS-1333] - Retirement of JobScheduler built-in HTTP Server
  • [JS-1346] - Retirement of built-in HTTP authentication
  • [JS-1347] - Retirement of asynchronous JobScheduler Web Services
  • [JS-1349] - Retirement of plain TCP interface
  • [JS-1384] - Enabling and disabling of jobs is deprecated
  • [JS-1562] - Retirement of custom history fields
  • [JS-1603] - Use of the Windows Script Engine languages such as VBScript and JScript with JobScheduler Master is deprecated
  • [JS-1679] - Retirement of XML Interface
  • [JS-1740] - Retirement of Apache Xerces for JobScheduler Master
  • [JS-1752] - Custom Documentation Stylesheet is discontinued
  • [JS-1754] - Schedules are replaced by Calendars
  • Feature:
  • [JS-429] - Environment variables for date and time with jobs on Agents
  • [JS-861] - Agent should start a process for a specific Windows account
  • [JS-928] - Regular expressions should support UTF-8 encoding
  • [JS-940] - Internal jobs Web_service_forwarder and Test_web_service without xercesImpl
  • [JS-1343] - Job chain with job node process classes
  • [JS-1348] - Plugin for synchronous JobScheduler Web Services
  • [JS-1359] - Enable job nodes to specify conditions for execution based on order parameters
  • [JS-1375] - New e-mail management
  • [JS-1388] - Add e-mail as a monitor service for the JobScheduler Monitoring Interface
  • [JS-1414] - Prevent secure information from being logged
  • [JS-1445] - JobScheduler Monitoring Interface should send a notification for directory missing from <file_order_source>
  • [JS-1518] - Handling of Agent tasks in case of failure and connection loss
  • [JS-1594] - JobScheduler Master supports PowerShell scripting language for jobs and monitors
  • [JS-1601] - JobScheduler Master integrates Task Server
  • [JS-1612] - Java Time replaces Joda Time
  • [JS-1624] - JobScheduler Master is buildable with tests under Solaris
  • [JS-1634] - JobScheduler Agent supports jobs and monitors implemented with .NET C# language
  • [JS-1703] - A timeout should be introduced which ends the endless reconnect to unreachable Agents
  • [JS-1707] - JobScheduler should work with MS JDBC 6.0 and SQL Server 2016
  • [JS-1715] - System Monitor plugin scripts for active checks should use the JOC Cockpit REST web service including authentication
  • [JS-1722] - options for http and https for indicating which network interfaces the JobScheduler should listen to are supported
  • [JS-1725] - Agent (Running jobs as a different user) - retrieving the environment variables for the target user
  • [JS-1726] - JobTaskQueueChanged Event should be sent
  • [JS-1727] - OrderAdded and OrderRemoved Events should be sent
  • [JS-1728] - JobScheduler should use XSLT2 to transform e-mail stylesheets
  • [JS-1746] - JobScheduler Agent PowerShell Jobs should support profiles
  • [JS-1747] - Agent (Running jobs as a different user) - setting the JobScheduler/Agent specific environment variables for the target user
  • [JS-1748] - Different JAVA options in sos.ini for JobScheduler process and other process
  • [JS-1749] - Multiple <date> for the same day are merged
  • [JS-1750] - Master start script should consider Java options when calling -send-cmd
  • [JS-1751] - Agent start script should consider -job-java-options command line option
  • [JS-1753] - Remove Custom Documentation stylesheets
  • [JS-1756] - Update Joda Time to a current release and build Joda Time with current timezones
  • [JS-1759] - Provide environment variable for current order state (node name)
  • [JS-1761] - Performance improvement - JobSchedulerJobAdapter should reduce API calls
  • Fix:
  • [JS-1683] - idle_timeout for task termination should be considered for use on Agents with an Open Source License
  • [JS-1693] - Substitution of environment variables in order parameters should work
  • [JS-1699] - The documentation of spooler.uri is missing
  • [JS-1705] - The answer of a <show_state> command should include the attribute configuration_directory
  • [JS-1709] - Run-time with a single_start and absolute_repeat in a single frequency does not work
  • [JS-1710] - HikariPool$PoolInitializationException if JocOrderStatistics is called
  • [JS-1712] - syntax error at or near "not" is raised if JocOrderStatistics is called
  • [JS-1713] - Orders with a specific end node should always be terminated at this node even if the job of this node raises an error
  • [JS-1716] - JobScheduler should consider that a parameter can have a hex_value attribute
  • [JS-1719] - Blacklisted orders are sometimes reported twice
  • [JS-1720] - Exception when executing a powershell job on a Windows machine with default Ansi Code Page=UTF
  • [JS-1721] - HeartBeat-Watchdog-Thread in a cluster configuration doesn't work if the database server is very slow (takes more than 1 minute to respond)
  • [JS-1723] - The mail caused by warn_if_longer|shorter_than attribute should consider the mail setting in a job too
  • [JS-1730] - A reconnect to SQL Server group cluster should work after the SQL Server node has changed
  • [JS-1732] - Universal Agent Cannot Find or Load Main Class ... AgentMain
  • [JS-1734] - Error handling for jobs with job chains on Agents should work
  • [JS-1735] - JobScheduler should consider exit codes from PowerShell jobs
  • [JS-1736] - JobScheduler should consider command errors from PowerShell jobs
  • [JS-1742] - Powershell interface raises COM-80020009 exception when JobScheduler Master does not set the scheduler.variable_name_prefix parameter
  • [JS-1757] - Exit code set by spooler_task.exit_code should be evaluated by job chain on_return_code
  • [JS-1758] - Agent merges job and order variables case-insensitive

New in Job Scheduler 1.11.5 (Nov 11, 2017)

  • Feature:
  • [JS-1700] - Master should create an event for unstopping jobs
  • [JS-1725] - Agent (Running jobs as a different user) - retrieving the environment variables for the target user
  • [JS-1726] - JobTaskQueueChanged Event should be sent
  • [JS-1727] - OrderAdded and OrderRemoved Events should be sent
  • [JS-1746] - JobScheduler Agent Powershell should support profiles
  • [JS-1747] - Agent (Running jobs as a different user) - setting the JobScheduler/Agent specific environment variables for the target user
  • [JS-1748] - Different JAVA options in sos.ini for JobScheduler process and other process
  • [JS-1750] - Master start script should consider Java options when calling -send-cmd
  • [JS-1751] - Agent start script should consider -job-java-options command line option
  • Fix:
  • [JS-1716] - JobScheduler should consider that a parameter can have a hex_value attribute
  • [JS-1721] - HeartBeat-Watchdog-Thread in a cluster configuration doesn't work if the database server is very slow (takes more than 1 minute to respond)
  • [JS-1730] - A reconnect to SQL Server group cluster should work after the SQL Server node has changed
  • [JS-1731] - Multiple <file_order_source> reprocess non-deleted files
  • [JS-1733] - Internal scheduler_file_order_sink job should not stop in case of error
  • [JS-1734] - Error handling for jobs with job chains on Agents should work
  • [JS-1735] - JobScheduler should consider exit codes from PowerShell jobs
  • [JS-1736] - JobScheduler should consider command errors from PowerShell jobs
  • [JS-1738] - Performance improvements
  • [JS-1742] - Powershell interface raises COM-80020009 exception when JobScheduler Master does not set the scheduler.variable_name_prefix parameter
  • [JS-1743] - JobScheduler Master using PostgreSQL should not freeze after a longer pause

New in Job Scheduler 1.11.4 (Aug 11, 2017)

  • Feature:
  • Agent should start a process for a specific Windows account
  • JobScheduler Master is buildable with tests under Solaris
  • JobScheduler Agent supports jobs and monitors implemented with .NET C# language
  • System Monitor plugin scripts for active checks should use the JOC Cockpit REST web service including authentication
  • options for http and https for indicating which network interfaces the JobScheduler should listen to are supported
  • Fix:
  • Z-REMOTE-118 when running two JobScheduler instances on the same machine
  • JobScheduler gets correct file timestamps after Windows 10 update
  • Blacklisted orders are sometimes reported twice
  • Exception when executing a powershell job on a Windows machine with default Ansi Code Page=UTF
  • The mail caused by warn_if_longer|shorter_than attribute should consider the mail setting in a job too

New in Job Scheduler 1.11.3 (Jun 10, 2017)

  • Feature:
  • Support for stacktrace logging of Java jobs
  • Fix:
  • The answer of a <show_state> command should include the attribute configuration_directory
  • Run-time with a single_start and absolute_repeat in a single frequency does not work

New in Job Scheduler 1.11.2 (Jun 2, 2017)

  • Feature:
  • [JS-1707] - JobScheduler should work with MS JDBC 6.0 and SQL Server 2016
  • Fix:
  • [JS-1693] - Substitution of environment variables in order parameters should work
  • [JS-1699] - The documentation of spooler.uri is missing
  • [JS-1710] - HikariPool$PoolInitializationException if JocOrderStatistics is called
  • [JS-1712] - syntax error at or near "not" is raised if JocOrderStatistics is called
  • [JS-1713] - Orders with a specific end node should always be terminated at this node even if the job of this node raises an error
  • [JS-1714] - All ID fields in history tables should have the length of 10

New in Job Scheduler 1.11.1 (Apr 6, 2017)

  • Feature:
  • [JS-1696] - The http/https port of JobScheduler and its Supervisor should be available in the JobScheduler API
  • Fix:
  • [JS-1694] - Updated schedules should be considered when using remote configuration
  • [JS-1697] - valid_from and valid_to attributes of schedule should consider in the time zone of the job or order to decide which schedule is active

New in Job Scheduler 1.10.6 (Nov 7, 2016)

  • Feature:
  • [JS-1660] - Improve handling of output to PowerShell channels
  • [JS-1663] - Universal Agent should have configurable keystore_path and keystore_passphrase
  • [JS-1665] - Universal Agent flushs stdout and stderr at every order step
  • Fix:
  • [JS-1654] - An command for a job chain node should work for the same job chain
  • [JS-1656] - If an Order ID contains german umlauts it is not possible to delete or resume the order when using the built-in web server
  • [JS-1669] - JobScheduler CppLogger class outputs database password to log file

New in Job Scheduler 1.10.5 (Jul 8, 2016)

  • Feature:
  • [JS-419] - JobScheduler should auto load changes to a holiday file
  • [JS-779] - If task is terminated due to timeout or a kill task command, then that should be written in the error element of the history entry
  • [JS-1320] - Remove support for element
  • [JS-1339] - Conversion of all Windows start scripts and event script to PowerShell
  • [JS-1589] - Agent applies token based authentication for REST web service interface
  • [JS-1590] - Master supports token based authentication for Agent
  • [JS-1592] - Agent responds to HTTPS requests with SSL Client Certificate
  • [JS-1595] - JobScheduler Agent supports PowerShell scripting language for jobs and monitors
  • [JS-1602] - .NET / PowerShell Adapter for Windows
  • [JS-1619] - The working directory of the JobScheduler Agent is used to store temporary files
  • [JS-1620] - JobScheduler start script offers option for bulk removal of ad hoc orders
  • [JS-1621] - Universal Agent sends stdout lines in batches to Master
  • [JS-1623] - Agent should support scripting languages for Windows Script Host (VBScript)
  • [JS-1628] - HTTPS for Universal Agent, command line option -ip-address= replaced
  • [JS-1630] - PowerShell Command Line Interface
  • [JS-1631] - Agent restricts access to authenticated users
  • [JS-1632] - JobScheduler Master authenticates itself to Universal Agent
  • [JS-1633] - Agent gets a data directory for configuration and working files
  • Fix:
  • [JS-781] - "SCHEDULER-451 Database check failed, database is not useable" for Postgres if the parameter "standard_conforming_strings" is turned on
  • [JS-935] - JobScheduler does not end with an exit_code > 0 if -configuration-directory is not present
  • [JS-1138] - SCHEDULER-970 should not be a warning if caused by SCHEDULER-271
  • [JS-1626] - Universal Agent should stop if requested by the Windows service
  • [JS-1627] - scheduler_file_order_sink returns empty set_state
  • [JS-1629] - SSH job should not raise an error when exporting environment variables in the remote script
  • [JS-1635] - warn_if_longer_than should work for shell jobs
  • [JS-1641] - JOC does not show folder view when runnig with oracle in a cluster with more than 1000 distributed job chains
  • [JS-1644] - Call of spooler_log() api after spooler.log().start_new_file() triggers scheduler.log rotate

New in Job Scheduler 1.10.4 (Apr 23, 2016)

  • Feature:
  • [JS-1572] - Agent provides master job path and task ID
  • [JS-1574] - Agent crash kill script hands over masters's task ID and job path
  • [JS-1575] - Agent stdout and stderr named with master's job name and task ID
  • [JS-1578] - XML Editor should support .NET Framework 4.0, 4.5
  • [JS-1580] - Add Agent identification to JobScheduler History
  • [JS-1588] - Add Agent identification to Reporting database
  • [JS-1596] - Provide PowerShell adapter class for 32bit and 64bit systems with JobScheduler Master
  • [JS-1600] - Monitoring Interface is capable of routing Return Codes
  • [JS-1609] - JobScheduler Master is buildable and runnable under Solaris
  • [JS-1614] - libsosperlscript.so is buildable for Unix systems
  • [JS-1617] - Idle timeout is set for HTTP connections between Master and Agent
  • Fix:
  • [JS-1387] - JobScheduler command provides no response for orders
  • [JS-1577] - Improvements of the Universal Agent start script to work on a Bourne shell
  • [JS-1579] - XML responses should be sanitized to provide valid XML
  • [JS-1581] - Agent shows error "Text file busy" when starting tasks
  • [JS-1582] - Shell jobs with min_tasks attribute are endlessly repeated
  • [JS-1584] - reduce dependencies for engine-job-api to other engine artifacts
  • [JS-1586] - In Agent included OS-specific kill script gets variable name
  • [JS-1598] - Resuming an order in a distributed job chain with should continue that order
  • [JS-1607] - spooler_task.exit_code() is always 0 if the task has run on an Agent
  • [JS-1608] - The state of a job chain node (pending, skipped, stopped) is changed automatically in a special configuration
  • [JS-1615] - Fixed error "STILL_ACTIVE" when using (JS-1329)

New in Job Scheduler 1.10.3 (Jan 15, 2016)

  • Feature:
  • [JS-1549] - Tasks should terminate in case of JobScheduler Master crash
  • [JS-1550] - Tasks should terminate in case of JobScheduler Agent crash
  • [JS-1551] - JobScheduler Agent maintains a list of running tasks
  • [JS-1552] - Agent start script executes a shell script to kill running tasks in case of a JobScheduler Agent crash
  • [JS-1554] - JobScheduler Master supports Fixed Priority Scheduling and Round-Robin Scheduling for Tasks with Agents
  • [JS-1558] - Agent includes OS-specific kill scripts
  • [JS-1561] - Publish artifacts of JobScheduler releases to Maven Central Repository
  • [JS-1566] - Performance improvement for Job Chains (JS-1221)
  • [JS-1569] - Add commands to start script to pause and continue JobScheduler Master
  • [JS-1571] - JobScheduler Active Cluster produces large logs files
  • Fix:
  • [JS-1547] - JobScheduler should return the processes that run with a process class in the the element
  • [JS-1555] - Java Process started by an Agent should not use the parameter -DLOGFILE for logging alike the Agent start
  • [JS-1557] - Tasks for standalone jobs running on an Agent should log the same as tasks for order jobs running on an Agent
  • [JS-1559] - Mail should not include event xml files
  • [JS-1564] - JobScheduler Active Cluster enqueued tasks are not started once limit is reached
  • [JS-1567] - Agent should not kill a quiet task being this task the only one running

New in Job Scheduler 1.10.2 (Dec 9, 2015)

  • Feature:
  • [JS-1521] - Universal Agent stores transient log files
  • [JS-1522] - Master starts in paused mode after failure
  • [JS-1524] - Universal Agent supports reconciliation after connection loss
  • [JS-1526] - Master start script supports paused start after failure
  • [JS-1527] - The working directory of jobs started by the Universal Agent should be configurable
  • [JS-1528] - XML Editor includes migration utility for YADE .ini settings files to XML configuration files
  • [JS-1530] - A template for an instance script is added to the JobScheduler Universal Agent
  • [JS-1531] - JobScheduler Universal Agent start script should forward log directory setting to Agent
  • Fix:
  • [JS-1516] - Enqueued tasks are not started when a process class with a limit is assigned to more than one job
  • [JS-1517] - Agent should consider changes to environment variable name prefix for parameters
  • [JS-1519] - Rolling order log should be supported
  • [JS-1523] - Universal Agent kills task if connection to Master gets lost
  • [JS-1525] - The monitor plugin should list files recursively
  • [JS-1529] - It should be possible to set the state text for jobs

New in Job Scheduler 1.10.1 (Oct 20, 2015)

  • Feature:
  • [JS-1412] - JobScheduler Universal Agent shows more information about running jobs
  • [JS-1506] - Keep-alive for JobScheduler Master
  • [JS-1508] - Publish binary files of JobScheduler releases to Maven Central Repository
  • [JS-1509] - JobScheduler Universal Agent should raise an error when contacted by Master released before 1.10
  • [JS-1510] - Java options in JobScheduler Universal Agent start script
  • [JS-1511] - Pause command should postpone task starts
  • [JS-1513] - JobScheduler exposes a unique id for an order run
  • Fix:
  • [JS-1330] - A shell job, running under an agent, and stopping due to non-zero exit code, should not change the order's state
  • [JS-1398] - Blacklisted file orders should be removed when corresponding file has been removed
  • [JS-1473] - The attribute warn_if_longer_than should result in a warning message email instead of an error email
  • [JS-1481] - An idle task ends itself to release process class slots for waiting tasks of a dynamically assigned process class
  • [JS-1492] - JobScheduler hangs if an order job has an end time in its current run time period and the task of the job needs more time
  • [JS-1504] - JobScheduler should provide job and task_id in event.xml when sending e-mail
  • [JS-1505] - JobScheduler should not crash if an order with a run time is added to a job chain that does not exist
  • [JS-1507] - JobScheduler should not crash if an order with an invalid run time is added
  • [JS-1514] - JobSchedulern should write the file scheduler.out into the logs directory

New in Job Scheduler 1.10.0 (Sep 16, 2015)

  • Deprecation:
  • [JS-736] - heart beat settings for cluster should be applied
  • [JS-1173] - element in a job configuration is deprecated
  • [JS-1295] - is deprecated
  • [JS-1306] - Use of SpiderMonkey Javascript language
  • [JS-1314] - Calling Enterprise Java Beans from a job
  • [JS-1315] - Running Java Managed Beans from a job
  • [JS-1316] - Communicate with JobScheduler from PHP scripts
  • [JS-1318] - JobScheduler allows individual start time function in element
  • [JS-1333] - Retirement of JobScheduler built-in HTTP Server
  • [JS-1346] - Retirement of built-in HTTP authentication
  • [JS-1347] - Retirement of asynchronous JobScheduler Web Services
  • [JS-1349] - Retirement of plain TCP interface
  • [JS-1373] - JobScheduler allows to fallback to CSV files in case of a database failure
  • [JS-1384] - Enabling and disabling of jobs is deprecated
  • [JS-1402] - based orders on the JobScheduler Universal Agent do not set the created attribute
  • [JS-1423] - JobScheduler detailed answers to XML commands
  • [JS-1425] - C++ JobScheduler Agent is replaced by JobScheduler Universal Agent
  • [JS-1428] - Deprecation of attribute remote_scheduler for file_order_source
  • Feature:
  • [JS-553] - The JobScheduler should provide the complete URL to a job documentation file in the XML answer of the command
  • [JS-557] - API job_chain object provides a method to retrieve an order
  • [JS-562] - job.statistics/task.statistics consider hidden jobs (visible="never" attribute)
  • [JS-578] - API order object provides a method to start an order
  • [JS-590] - If a process is interrupted by a signal (e.g. ulimit -f), this should be handled by Job Scheduler
  • [JS-633] - Implementing a XML command and answer for querying the current memory allocation on Unix
  • [JS-684] - System Monitor (Nagios, op5) should notify if a JobScheduler Universal Agent is not available
  • [JS-713] - Log file scheduler.log should be more concise
  • [JS-737] - JobScheduler should log the JVM path before it is loaded
  • [JS-779] - If task is terminated due to timeout or a kill task command, then that should be written in the error element of the history entry
  • [JS-785] - Publish JobScheduler sources to publicly available repository
  • [JS-809] - Umstellung des scheduler builds auf maven 3
  • [JS-825] - Enable SSL access via Jetty
  • [JS-878] - API job_chain object should provide methods to retrieve orders
  • [JS-981] - The scheduler.pid file should be world readable
  • [JS-1074] - JobScheduler should create an info message if an order is started for a job chain with max_orders="0"
  • [JS-1144] - PID file should not be overwritten if JobScheduler is started twice
  • [JS-1182] - JobScheduler should not load job documentations on start-up but on demand
  • [JS-1194] - JobScheduler should put its stdout/stderr in a separate file on Windows platforms
  • [JS-1247] - Plugin for individual runtime calculations to execute a process every n days
  • [JS-1248] - Old polling job-microscheduling switched off
  • [JS-1291] - JobScheduler Universal Agent
  • [JS-1300] - on JobScheduler Universal Agent
  • [JS-1319] - Remove support for start time function
  • [JS-1321] - In case of System crash, Database errors or unorderly shutdown JobScheduler should update database with status and log for running tasks/orders
  • [JS-1325] - Windows Service Interface for JobScheduler Universal Agent
  • [JS-1329] - Check stderr for errors in shell script execution
  • [JS-1338] - JobScheduler log should be less verbose
  • [JS-1393] - Identify output channel in JobScheduler logs
  • [JS-1399] - Process classes for and on JobScheduler Universal Agent
  • [JS-1400] - Web service command to terminate JobScheduler Universal Agent
  • [JS-1401] - Add commands to start script to terminate JobScheduler Universal Agent
  • [JS-1410] - JobScheduler Universal Agent web services return information about current state
  • [JS-1416] - JobScheduler Universal Agent client for the command line
  • [JS-1419] - Add command to start script to run JobScheduler Universal Agent inside a Docker container
  • [JS-1420] - SIGTERM on shell task on classic agent over tcp
  • [JS-1422] - on JobScheduler Universal Agent
  • [JS-1426] - Status command for Universal Agent start script shows status information from overview web service call
  • [JS-1430] - Provide schema-aware XML Editor for JobScheduler and JADE configuration files
  • [JS-1442] - Restrict network interface for JobScheduler Universal Agent listener
  • [JS-1443] - Add network interfaces configuration to the start script for the Universal Agent
  • [JS-1450] - A process_class defined at job level has precedence before job chain level
  • [JS-1454] - Keep-alive for classic JobScheduler Agent
  • [JS-1456] - Keep-Alive for JobScheduler Universal Agent
  • [JS-1461] - SCHEDULER_ID should be provided as Environment Variable by JobScheduler
  • [JS-1464] - Allow jobs to run in different process classes
  • [JS-1467] - Enable Agent to run behind different Proxy URLs
  • [JS-1468] - OS-specific kill for JobScheduler Universal Agent Tasks without monitor
  • [JS-1477] - XML Editor exports compatible JADE .ini files from XML configuration files
  • [JS-1480] - JobScheduler Universal Agent web services
  • [JS-1482] - JobScheduler Universal Agent limits the number jobs that are executed without license key
  • [JS-1483] - If a job cannot be started due to licensing issues, this information is shown in the state text
  • [JS-1493] - JobScheduler start script writes number of enqueued tasks to output
  • [JS-1495] - Integrate task kill features into JobScheduler Universal Agent start script
  • Fix:
  • [JS-589] - The command should work if there are UNICODE characters in the order ID
  • [JS-598] - Using Postgres JBDC drivers more recent than 8.1-415 doesn't work
  • [JS-732] - command returns no 'source'-element
  • [JS-733] - has wrong counts in the order subsystem
  • [JS-781] - "SCHEDULER-451 Database check failed, database is not useable" for Postgres if the parameter "standard_conforming_strings" is turned on
  • [JS-935] - JobScheduler does not end with an exit_code > 0 if -configuration-directory is not present
  • [JS-951] - Strange behavior while JobScheduler tries to reconnect to the database
  • [JS-969] - start_when_directory_changed should work after the job was stopped
  • [JS-1059] - "alert_when_directory_missing" of should send a notification
  • [JS-1126] - Orders for job chains with the same job should not wait endlessly in the order queue
  • [JS-1138] - SCHEDULER-970 should not be a warning if caused by SCHEDULER-271
  • [JS-1169] - The status disabled for a job should be persistent also when disabling a job with modify_job command.
  • [JS-1331] - Missing message SCHEDULER-846, when running under agent
  • [JS-1368] - Verify JDBC URLs created by the installer 1.9.1
  • [JS-1370] - sos.spooler.Job.delay_order_after_setback does not accept floating point values when used under Unix
  • [JS-1381] - Avoid unneccessary creation of new ids for table scheduler_history when using a distributed job chain
  • [JS-1387] - JobScheduler command provides no response for orders
  • [JS-1390] - should not fall asleep after the first files
  • [JS-1391] - Resumption of "Avoid unneccessary creation of new ids for table scheduler_history when using a non-distributed job chain"
  • [JS-1392] - JobScheduler Monitoring Interface should provide the correct node name and error message
  • [JS-1394] - "skip node" option in a nested job chain should work
  • [JS-1403] - Fix for JS-1251/JS-1285: Handling of duplicate order key in database failed if order log contains some lines
  • [JS-1404] - High CPU load for two minutes under Windows after a HTTP request to an Agent or the Supervisor
  • [JS-1411] - Allow JobSchedulerLog4JAppender to only log for SOS classes
  • [JS-1413] - JobScheduler email should have consistent timezone information in email header, body and attachments
  • [JS-1418] - Big Task log should not hang or crash JobScheduler in case of mail_on_error=yes
  • [JS-1421] - The command on a shell task without monitor on classic Agent kills all children of the shell task
  • [JS-1435] - API call job_chain.add_job() fails
  • [JS-1441] - Provide working sample configuration for JobScheduler Monitoring Interface
  • [JS-1447] - Sometimes the jobscheduler_event.cmd doesn't store the event into the csv file even though the connection failed
  • [JS-1453] - JobScheduler crashes if a nesting job chain containing a permanent order is changed
  • [JS-1455] - API method spooler_log.start_new_file() deactivates the log category {scheduler}
  • [JS-1457] - Classic Agent may deadlock when starting multiple shell tasks at once
  • [JS-1460] - Add documentation for JobScheduler active checks with Nagios
  • [JS-1462] - CreateProcess fails with MSWIN-00000020 The process cannot access the file because it is being used by another process
  • [JS-1463] - job timeout on a JobScheduler Master kills a shell task after the specified timeout
  • [JS-1470] - It should be possible to call the method .start in the job object without the optional parameter variable_set
  • [JS-1471] - The job chain node attribute on_error="suspend" should suspend an order when a job without monitor exits with error
  • [JS-1472] - GlobalMonitor plugin does not work with the cache folder as the live folder
  • [JS-1473] - The attribute warn_if_longer_than should result in only one warning message email
  • [JS-1475] - When a global monitor is in the cache folder and in the live folder then it should be added just once
  • [JS-1476] - If all nodes of an member of a nested job chain are skipped the order should proceed with the next job chain
  • [JS-1479] - For last Job node in a Job Chain does not work
  • [JS-1496] - SIGTERM on shell task with monitor is forwarded to shell process, in Universal Agent
  • Test Case:
  • [JS-1353] - JobScheduler Universal Agent: API Tests
  • Sub-task:
  • [JS-1259] - Check nested job chains, max_orders, process class and new job-microscheduling
  • [JS-1345] - Evaluate logging technologies
  • [JS-1352] - JobScheduler Universal Agent: Java jobs
  • [JS-1371] - JobScheduler Universal Agent: Local proxy implementations for JobScheduler API
  • [JS-1372] - JobScheduler Universal Agent: JavaScript jobs
  • [JS-1377] - Extend JOC to support attribute "alert_when_directory_missing"
  • [JS-1382] - JobScheduler Universal Agent: kill a running task (including child processes)
  • [JS-1383] - JobScheduler Universal Agent: API jobs with monitors
  • [JS-1385] - Configure -stdout and -stderr options for Windows start script
  • [JS-1386] - JobScheduler Universal Agent: HTTP tunnel replaces RPC TCP connections
  • [JS-1396] - Prove the readiness of the SAX parser for JITL job implementation
  • [JS-1409] - Verify JDBC URLs created by the installer 1.10
  • [JS-1431] - Support scroll right/left by mouse
  • [JS-1432] - Enable to store an XML file after schema assignment
  • [JS-1433] - Operation "Expand/Collapse root node" should be "Expand/Collapse selected node"
  • [JS-1434] - After unsuccessful drag & drop operation the expand/collapse operation should work
  • [JS-1436] - Show reference values as list items
  • [JS-1437] - Enable boolean element values to be displayed as select lists
  • [JS-1438] - Copy & Paste XML nodes between XML configuration files
  • [JS-1439] - Import and export XML configuration
  • [JS-1440] - Provide XML Editor for use with JobScheduler Monitoring Interface configuration files
  • [JS-1452] - Uncouple the 'Add child Remove' bar from the rest of the right hand panel
  • [JS-1469] - Approve issue for the relase 1.10
  • [JS-1484] - Consider change of boolean default values in parameters
  • [JS-1485] - URI schema assignment
  • [JS-1486] - Suggest .ini file name when exporting
  • [JS-1487] - Remove option for temporary file removal
  • [JS-1488] - Consider exporting parameters without prefix
  • [JS-1489] - Rename operations for schema assignment
  • [JS-1490] - Enable Plugin-supported operations to be listed in the context menu
  • [JS-1491] - Separate Collapse/Expand operations
  • [JS-1494] - Allow auto-convert mode when saving XML files

New in Job Scheduler 1.9.5 (Sep 2, 2015)

  • [JS-1453] - JobScheduler crashes if a nesting job chain containing a permanent order is changed
  • [JS-1462] - CreateProcess fails with MSWIN-00000020 The process cannot access the file because it is being used by another process
  • [JS-1463] - job timeout on a JobScheduler Master kills a shell task after the specified timeout
  • [JS-1472] - GlobalMonitor plugin does not work with the cache folder as the live folder

New in Job Scheduler 1.9.4 (Aug 5, 2015)

  • Feature:
  • [JS-1454] - Keep-alive for classic JobScheduler Agent
  • Fix:
  • [JS-1421] - The command on a shell task without monitor on classic Agent kills all children of the shell task
  • [JS-1435] - API call job_chain.add_job() fails
  • [JS-1455] - API method spooler_log.start_new_file() deactivates the log category {scheduler}
  • [JS-1457] - Classic Agent may deadlock when starting multiple shell tasks at once

New in Job Scheduler 1.9.3 (Jul 13, 2015)

  • Fix:
  • [JS-1364] - confusing log line: ...unknown parameter java_options=
  • [JS-1387] - JobScheduler command provides no response for orders
  • [JS-1429] - PostgreSQL driver should be 8.1-404.jdbc3.jar
  • [JS-1441] - Provide working sample configuration for JobScheduler Monitoring Interface
  • [JS-1447] - Sometimes the jobscheduler_event.cmd doesn't store the event into the csv file even though the connection failed

New in Job Scheduler 1.9.1 (Jun 9, 2015)

  • Fix:
  • should not fall asleep after the first files
  • Resumption of "Avoid unneccessary creation of new ids for table scheduler_history when using a non-distributed job chain"
  • JobScheduler Monitoring Interface should provide the correct node name and error message
  • Fix for JS-1251/JS-1285: Handling of duplicate order key in database failed if order log contains some lines
  • High CPU load for two minutes under Windows after a HTTP request to an Agent or the Supervisor
  • Sub-task:
  • Verify JDBC URLs created by the installer 1.9.1

New in Job Scheduler 1.9.0 RC 1 (Apr 18, 2015)

  • Deprecation:
  • [JS-736] - heart beat settings for cluster should be applied
  • [JS-1173] - element in a job configuration is deprecated
  • [JS-1295] - is deprecated
  • [JS-1306] - Use of SpiderMonkey Javascript language
  • [JS-1314] - Calling Enterprise Java Beans from a job
  • [JS-1315] - Running Java Managed Beans from a job
  • [JS-1316] - Communicate with JobScheduler from PHP scripts
  • [JS-1318] - JobScheduler allows individual start time function in element
  • Feature:
  • [JS-534] - Allow relative paths for jobs that use
  • [JS-705] - Incomprehensible error message when an order is started and all job chain nodes are skipped
  • [JS-1145] - Provide named monitors
  • [JS-1163] - with SIGTERM before SIGKILL
  • [JS-1177] - A JobScheduler cluster member can access the task logs for distributed orders from the task history of other cluster members
  • [JS-1190] - Control the workflow of a job chain by exit codes
  • [JS-1193] - Start of an order should be possible depending on the result of a task of a job chain node
  • [JS-1195] - Plugin-specific XML configuration extensions
  • [JS-1260] - JobScheduler should not log the errors from inside a history.entry element
  • [JS-1283] - The delay of the second database reconnect should be reduced
  • [JS-1291] - Java based JobScheduler Agent
  • [JS-1301] - Job chain with default process class (default agent)
  • [JS-1302] - JobScheduler Reporting Interface
  • [JS-1307] - SIGTERM on shell task with monitor is forwarded to shell process
  • [JS-1322] - Plugin interface for loading jobs
  • [JS-1323] - Plugin for global pre- and postprocessing
  • [JS-1324] - Configuration elements for global pre- and post-processing
  • [JS-1336] - Restrict scope of environment variables in Windows event script
  • [JS-1341] - Up-to-date bug fix versions of external libraries
  • Fix:
  • [JS-427] - A persistent order with a run_time and a state and an end_state is not repeated
  • [JS-726] - Postprocessing will not be executed when API Job returns false and Job runs in a job chain
  • [JS-864] - Orders of a job chain disappear when all job chain nodes are skipped
  • [JS-1139] - Job Scheduler seems to end too many tasks to free the process class
  • [JS-1252] - JobScheduler should check the scripting language compatibility at run-time
  • [JS-1298] - "Start order now" should work when running in a distributed cluster
  • [JS-1303] - In a distributed job chain triggered by file orders some files create conflicts between cluster members
  • [JS-1332] - C++ Agent crashes when used via HTTP (what is not recommended)
  • [JS-1337] - The Security Server does no longer support JobNet
  • [JS-1350] - JobScheduler command line option -V returns an error
  • [JS-1354] - Avoid unneccessary creation of new ids for table scheduler_history
  • Sub-task:
  • [JS-1313] - Verify approval of port availability

New in Job Scheduler 1.8 RC 1 (Dec 20, 2014)

  • Updated recently:
  • Fileorders will not be handled when the first job in job chain has a period
  • force attribute of start_job is not documented in the english version
  • process_class can reference multiple remote_scheduler

New in Job Scheduler 1.6.4131 (May 19, 2014)

  • Bug:
  • [JS-994] - A naming itself in delegate=".." aborts JobScheduler
  • [JS-995] - A job referencing a name should log SCHEDULER-161 as warning, not error, when read from disk before the schedule
  • [JS-1013] - Setting for tmp in [spooler] factory.ini does have no effect.
  • [JS-1120] - When scheduler.order.keep_order_content_on_reschedule="false" previous set parameters exist after JobScheduler-Restart
  • [JS-1122] - In a distributed orders cluster skipped nodes are executed if they are the first node in a job chain.
  • [JS-1133] - JobScheduler Service doesn´t work under Windows with Java8
  • [JS-1150] - release 1.6.4131 doesn't contain jade job
  • Bug With Workaround:
  • [JS-1108] - Java Threads do not terminate on agent
  • Improvement:
  • [JS-472] - Api does not have the job_chain path in job_chain.name
  • New Feature:
  • [JS-1104] - API function "states" of object "job_chain"
  • Task:
  • [JS-1115] - Getter and Setter for order setbacks should have the same name

New in Job Scheduler 1.6.4043 (Feb 13, 2014)

  • JobScheduler engine requires at least Java 7 instead Java 6
  • Fixed:
  • Orders cannot be changed after they did run and a new next start time has been calculated
  • JobScheduler crashes when a command is called for a suspended order in a distributed job chain

New in Job Scheduler 1.5.3192 (Jul 13, 2013)

  • Bug With Workaround:
  • [JS-972] - A commercial license is not stored in the license file during the setup on windows or linux
  • Improvement:
  • [JS-952] - JobScheduler should support mariadb as JDBC driver for MySQL
  • New Feature:
  • [JS-948] - Wake job when in period
  • Task:
  • [JS-974] - JOC: the function 'set run time' doesn't change the configuration file. Changes only valid until the next JobScheduler restart.
  • [JS-979] - The 'mysql' package is not longer provided in the package selection of the setup.

New in Job Scheduler 1.3.12.3142 (Jul 13, 2013)

  • Bug:
  • [JS-502] - Changing of Orderung of Pre/Postprocessing does not open the save button
  • [JS-618] - When creating an order with command on exit no parameters are set.
  • [JS-629] - File order sources with files greater than 2GB under Linux do not work (ERRNO-75)
  • [JS-774] - Spooler_program does not work with String-Argument
  • [JS-824] - Z-REMOTE-118 fires an unspecific ERRNO-0
  • [JS-866] - command "kill" for a remote job does not work properly
  • [JS-934] - Duplicate scheduler id in connection string in case of reopen the database
  • [JS-954] - Orders sometimes have next_start=never when restarting JobScheduler
  • [JS-956] - The answer of contains sometimes no source element
  • [JS-957] - When you abort and restart the JobScheduler then (almost all) orders with a repeat interval start only for one time.
  • [JS-962] - JobScheduler slows down when requesting large API response
  • [JS-964] - A Monitor script on agent acts different depending if it is combined with a shell job or an API job.
  • [JS-965] - The options in the listbox of the job chain nodes have an incorrect order in the functions like 'set state' and 'add order' using IE10
  • Improvement:
  • [JS-750] - Make the creation of a folderstructure using "recursive" possible
  • [JS-815] - JobSchedulerSSHJob is assigned to new SOSSSHJob2JSAdapter. Old version is provided in JobSchedulerSSHJob_deprecated
  • [JS-958] - It should be possible to use parameters coming from events in the commands defined in the xml event handlers.
  • [JS-959] - JOC: task and order history shows the duration of the task or order
  • Task:
  • [JS-961] - JOC: remove the 'reread' function in the job menu

New in Job Scheduler 1.3.5 (May 13, 2009)

  • Main
  • PHP Managed Jobs Interface has a new implementation inclusive new data model.
  • The older versions and this new version are not compatible, but an easy migration is possible.
  • Bugs
  • [JS-205] - API method job.name() returns no path
  • [JS-209] - Job Scheduler crashes with "Connection reset by peer" (on web service call)
  • [JS-261] - period doesn't work in weekdays/day element of order job
  • [JS-280] - scheduler.dll does't work for debugging anymore
  • [JS-281] - Order History can not be displayed for distributed orders
  • [JS-286] - Managed jobs shows ü in the web gui
  • [JS-288] - Files and tables for eventing will not be installed
  • [JS-289] - Showing of job description does not work
  • [JS-290] - Eventing does not work with windows
  • [JS-295] - Access to a log in a clustered Job Scheduler is not available
  • [JS-301] - job attribute timeout doesn't work anymore
  • [JS-302] - delay_afer_error doesn't work for standalone jobs
  • Improvements
  • [JS-60] - Blanks in script should not be compiled
  • [JS-102] - include order log in warning mails for jobs with order="yes"
  • [JS-109] - Improvements for logging on order.setback()
  • [JS-119] - Open F1 help urls always in the same window
  • [JS-191] - add attribute replace (yes|no) to Element
  • [JS-222] - Provide API methods for hot folder directories
  • [JS-260] - add remove button for enqueued tasks
  • [JS-262] - Details Configuration
  • [JS-273] - Support for titles in job chains
  • [JS-304] - Tab 'Orders' incl. Filter-Management
  • New Features
  • [JS-35] - Search function in the Managed-Explorer
  • [JS-265] - add Attribute end_state to order/add_order element
  • [JS-271] - API to add objects to hot folders
  • [JS-279] - new environment variables for shell jobs
  • [JS-297] - Getting / Setting of Job Scheduler Variables
  • [JS-298] - Working Days in run_time

New in Job Scheduler 1.3.3.1 (Dec 20, 2007)

  • Fix: classpaths with whitespaces do not work when compiling java jobs on the fly
  • Fix: Java package structures with depth>1 don't work when compiling java jobs on the fly
  • Fix: Clicking on browse and then close the explorer window ends the editor
  • Fix: Job Editor provides wrong default values for recoverable and visible job chains in hot folders
  • Fix: Wrong window title in job editor when saving objects to hot folders
  • Fix: Menu item for saving objects disappears in job editor
  • Fix: Wrong default directory in job editor for hot folders
  • Fix: Wrong spacing/sizing for editing parameters and environment variables in job editor
  • Fix: Zombie Orders and job chain remain when deleting job chains
  • Fix: Editor shows wrong language for Job parameter descriptions
  • Fix: supply always empty history
  • Fix: Job sections in the factory.ini are not supported if jobname has path with slashes
  • Fix: API method job.name() returns no path
  • Fix: Command crashes
  • Add SMTP Authentication for e-mail
  • Job and job chain list are sortable by name, next start time, status and path
  • Summary of the latest job and order activities
  • Support for UNC file names in FTP jobs
  • Copy objects for hot folders
  • Support for Massive parallel file transfer
  • bash is not longer required for setup
  • New: Filter for displaying jobs in Built-In HTML GUI