Why does Matlab stop in a long running script on Linux server once GADS toolbox is needed

Dear all,

I'm trying to run a very long script in Matlab2013a on a Linux server in singleCompThread mode (concurrent license), I submit my jobs through a queuing system. The script is divided in two phases. The first phase (runs for 1-2 days) needs no additional toolboxes, the second phase (after 1-2 days) DOES need the Global Optimization toolbox. The problem is that once I research the second phase of the script it stops running. Matlab doesn't crash, but it's not printing out anything to the screen anymore and the queuing system tells me its not using any computational resources (CPU usage etc.) anymore, so basically its idling. There is no warning message.

matlab -nodesktop -nosplash -nodisplay -singleCompThread -r "addpath('script_path') script_name"

Is this a licensing issue? I have licenses available at every point in time, but could it be that my toolbox license times out after a while since I'm not using it for 1 day?

I hope the description of my problem suffices.

Cheers, Thomas

[Thomas]

I'm getting closer to the problem. It seems like, even though running in single thread mode, MATLAB starts several processes on the server that compete against another. When I start only 32 jobs on my 64 core machine, everything works fine. Does anyone have an idea why this is and how I can suppress it?