Skip to content

x Want to ask a question or reply? Click here to join the group.
Richard P

Improved management of Batch Server BATCH administration session (X3-326598)

1 minute read time.

You might have noticed the following change mentioned in the Community Hub Announcement

ALERT: Syracuse Server 12.20.13 (Sage X3 2024 R1) and Syracuse Server 12.21.4 (Sage X3 2024 R2) are now available:

I thought I’d provide some more details on what this change is.

Batch Server manages requests via an Administration Session which checks for relevant Batch Requests which need to be actioned.

Up until this point, this Administration Session has been running for the whole lifetime of the Batch Server – i.e. from when the Batch Server is started, until the Batch Server is stopped.

The creation of the Administration Session can be seen in the Activity log list.

As of this improvement, a new parameter setting has been made available which allows you to specify a life-time in minutes – this means that a new Administration Session is automatically created after the specified number of minutes

The default life-time is 240 minutes.

To demonstrate the feature more easily, I changed mine to 2 minutes.

When I applied the new Syracuse, the language changed to French after the initial Batch Server start and first administration session.

This has been reported as a bug.

This enhancement should reduce the risks of memory issues with long-running Administration Session adonix processes, and make Batch Server more robust.

  • Hello,
    Thank you for these clarifications.

    Unfortunately, this patch is not available for versions < 12.20 (e.g., 12.17).
    I’m therefore looking for a homemade automated solution.

    We agree that this works around an issue with the lost link between the Syracuse session and the X3 batch server session ?
    A bit like an ECONNRESET, except the adonix and sadoss processes are still running.

    If restarting only the X3 batch session has no impact on tasks in progress.
    So a scheduled Windows task to periodically kill the X3 batch server session would have the same effect as the patch ?

    Would the KB on keepalive + shared memory (registry key) not apply in this type of case ?

    Thanks in advance for your feedback.
    Best regards.

  • Hi Ryan,

    It could depend on the frequency of problems.

    Regards,

    Reg.

  • Hi, What is the recommended setting for this new parameter for a customer with a lot of recurring tasks?

*Community Hub is the new name for Sage City