Originally posted by: Antoine_Mtl

Hello,

I'm using Java and CP Optimizer with the concert technology. I have two issues when I try to debug my program:

First, the JVM chrashes because of the wrapper of CP Optimizer. I have the name of the method which has crashed the JVM, but no more information, no error message from the wrapper:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ffea2ee48c0, pid=17488, tid=140732545738496
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 1.8.0_25-b17)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libcp_wrap_cpp_java1260.so+0x8ba8c0]  IloCP::_next() const+0x10
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
#.../hs_err_pid17488.log

Second, I have sometimes this exception: ilog.concert.IloException: incorrect search use. I have searched on the Internet, and I am not able to find any information on this exception.

I would like to know if it is normal to have no more information on these errors. Furthermore, what can I do to obtain more information to correctly debug my program please ?

Thank you,

Antoine

Originally posted by: SergeyPolyakovskiy

Hi Antoine,

More information is for sure required when and where this error arises. Looks like you use cp.next() to continue the search. If so, are you doing anything with a temporary solution or other actions in between of calls of cp.next()?

Regards,

Sergey

Originally posted by: GGR

Hi Antoine

Actually it may happen that you miss to call the startNewSearch method before the first next iteration: please refer to

http://www-01.ibm.com/support/knowledgecenter/SSSA5P_12.6.1/ilog.odms.cpo.help/refjavacpoptimizer/html/ilog/cp/IloCP.html?cp=SSSA5P_12.6.1

for full information

Hope that helps

Originally posted by: Antoine_Mtl

Thank you for the answers.

I was indeed trying to do cp.next() while the search had already stopped.