Job Scheduler

Scheduler gets connection refused (interface shows "process lost") when trying to start new tasks

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.3.1
Fix Version/s: 1.3.2
Component/s: Job Scheduler Binaries

Description:

Hide

In rare system configurations the Job Scheduler fails to start some tasks, while others are started without any problems.
The failed tasks get "connection refused" when connecting to the main process.
When trying to find a new port to offer to a new task, the operating system seems to "lie" about which ports may be bindet. The OS let's the Job Scheduler bind ports that are already used by the Job Scheduler itself although they should be able to be bound at that moment.

Show
In rare system configurations the Job Scheduler fails to start some tasks, while others are started without any problems. The failed tasks get "connection refused" when connecting to the main process. When trying to find a new port to offer to a new task, the operating system seems to "lie" about which ports may be bindet. The OS let's the Job Scheduler bind ports that are already used by the Job Scheduler itself although they should be able to be bound at that moment.

Environment:

Windows with certain firewalls/anti virus software

Activity

Ascending order - Click to sort in descending order

There are no comments yet on this issue.

People

Assignee:

Joacim Zschimmer

Reporter:

Andreas Liebert
Votes:

0

Watchers:

0

Dates

Created:

02 August 2007 14:46

Updated:

23 August 2007 10:42

Resolved:

02 August 2007 14:48