x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 139 subscribers
  • Views 511 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
David Calisto

Batch Server running but not processing new tasks.

SOLVED
Posted By

Hi,

Lately, some of our X3 servers are having problems with the batch server.
It's running normally until it stops processing tasks, while maintaining the status as running.

I've enabled the logs under Administration, Settings, Global Settings for the batch options to silly and ended up getting some additional info.

N0 Logs example:
batch.server | info | BatchServer_X3V12 end control loop
batch.server | info | BatchServer_X3V12 begin control loop The batch controller can handle 8 queries simultaneously
...
batch.server | warn | BatchServer_X3V12 previous loop not ended !!!
batch.server | warn | BatchServer_X3V12 previous loop not ended !!!
...
batch.server | warn | BatchServer_X3V12 previous loop not ended !!!
batch.server | silly | ProcessLock_batch controlLock
batch.server | silly | ProcessLock_batch batch_APPSERVER_N0_11544 has still the lock
batch.server | warn | BatchServer_X3V12 previous loop not ended !!!
batch.server | warn | BatchServer_X3V12 previous loop not ended !!!
batch.server | silly | ProcessLock_batch controlLock
batch.server | silly | ProcessLock_batch batch_APPSERVER_N0_11544 has still the lock

serveur.tra file under Folders\X3\SRV\TRA stops writing new information.
On windows event viewer can't find anything that matches the time batch server stops processing new tasks.

What am I missing? is there an approach to solve this issue?
Thanks.

  • 0

    Usually stopping and restarting the batch server can resolve these sorts of issues.

  • +1
    verified answer

    Ensure that you are performing batch server maintenance often. Normally abnormally large trace files, and large amount of trace files has this effect on the Batch Server functionality.    

    Batch Server Maintenance

    This should be done weekly, but depends on the number of transactions within the folder. To perform the maintenance, stop the Batch Server and Accounting Task and then either copy (files to be copied to storage location not within the Sage X3 folder schema) or delete the following files:

    In the Sage X3 Runtime folder ("..\Runtime\tmp"):

    • psadxnnnn.bat & .res
    • RQTnnnn.bat & .pid
    • serveur.bat & .pid
    • cmdnnnn.dat files
    • Don't delete serveur.ent and serveur.out files (Unix and Linux only)

    In the X3 Batch Server TRA folders ("..\X3\SRV\TRA"):

    • RTZ the "serveur.tra" file if larger than 1MB
    • Delete/Copy old RQTnnnn.tra files

    In each endpoints TRA folder ("..\FOLDER\TRA"):

    • RTZ the "ACCENTRY.tra" file if it's bigger than 1MB
    • Delete/Copy old *.tra files

    In each endpoints tmp folders ("..\FOLDER\tmp")

    • RTZ the "espion.tra" and "transac.tra" files if they are larger than 1MB
    • Delete/Copy old temporary files



  • 0 in reply to Kingy

    Hi Kingy,

    That's normally what we end up doing for a quick fix, but we are looking for a more permanent fix because some customers have tasks for importing files and their internal processes end up stopping.

    This is occurring almost once a week.

    Thanks for the feedback.

  • 0 in reply to Regard Hulsbos

    Some of the files above have standard purge processes that can be set to run regularly and I would use those for preference rather than randomly deleting files over 1mb.

    I would also check that there are no irrelevant statistics processes attached to any of the imports.

    A client had these set up against Purchase and Sales invoices and it was the secondary connection to those tables that caused time outs during the imports.

    Worth a look.

  • 0 in reply to Regard Hulsbos

    Hi Hulsbos,

    We did some of this, but ended up not doing all at once. I'm going to do it at the beginning and at the end of the week and check if I still have the same issue.

    As for the temp folder under runtime, we ended up not doing anything.

    Thanks for the feedback.

*Community Hub is the new name for Sage City