Originally posted by: SystemAdmin

Although I set the time limit to 1800 seconds using "setParam(IloCplex::TiLim ,1800)" in Cplex 12.5, the time spent to solve the root node processing (before B&C) has reached to 86000 seconds in some instances! How can this occur? Is there a way to force Cplex to stop around 1800 seconds (I know that it may exceed 1800 seconds but should not be as much as 86000 seconds).

I was using the same time limit statement in Cplex 12.2 without any problem.
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

CPLEX should not overshoot the time limit by that much. Can you show us a log file for this problem?
Or even better, can you provide the model that causes this trouble?
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

I encounter similar problem using 12.4, when I set the time limit to be 2 seconds, in fact the solver took more than 1 hour for some data.

Is this an bug?
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: SystemAdmin

Yes, I think that this can be considered a bug. Can you provide log file and/or a model to reproduce this issue?
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: falvelos

I have the same problem with cplex 12.4.

Any idea of a workaround? I tried using my own timer and mipcallback (I am solvign a large MIP) but did not work. 

#CPLEXOptimizers
#DecisionOptimization

Why did using your own timer and the mipcallback fail?

What API do you use? If nothing else helps you could use a terminate flag or an aborter that is activated by a different thread or an appropriate signal.

#CPLEXOptimizers
#DecisionOptimization