Decision Optimization

Decision Optimization

Delivers prescriptive analytics capabilities and decision intelligence to improve decision-making.

 View Only
Expand all | Collapse all

how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

  • 1.  how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Sat February 03, 2018 08:27 AM

    Originally posted by: Lewis-Young


    hello,when a project  run in the CPLEX_Studio128,I encounter a problem  "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE". and the log files as follows:

     

    !ENTRY ilog.odms.ide.opllang 1 0 2018-02-03 20:50:24.076
    !MESSAGE concert_wrap.IloEndMT
    !SESSION 2018-02-03 20:50:28.989 -----------------------------------------------
    eclipse.buildId=Build 0
    java.fullversion=8.0.5.0 - pwa6480sr5-20170905_01(SR5)
    JRE 1.8.0 IBM J9 2.9 Windows 7 amd64-64 Compressed References 20170901_363591 (JIT enabled, AOT enabled)
    J9VM - d56eb84
    JIT  - tr.open_20170901_140853_d56eb84
    OMR  - b033a01
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
    Command-line arguments:  -os win32 -ws win32 -arch x86_64 -clean

    !ENTRY org.eclipse.equinox.ds 4 0 2018-02-03 20:50:30.373
    !MESSAGE FrameworkEvent ERROR
    !STACK 0
    org.osgi.framework.BundleException: Could not resolve module: org.eclipse.equinox.ds [4]
      Unresolved requirement: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"

        at org.eclipse.osgi.container.Module.start(Module.java:434)
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
        at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

    !ENTRY ilog.odms.ide.core 1 0 2018-02-03 20:50:42.206
    !MESSAGE ODM Bundle is OFF

    !ENTRY ilog.odms.ide.core 4 0 2018-02-03 20:54:09.045
    !MESSAGE OplRun is not responding, you must relaunch the RunConfig

     

    !ENTRY ilog.odms.ide.core 4 0 2018-02-03 20:54:11.566
    !MESSAGE Connection refused to host: 127.0.0.1; nested exception is: 
        java.net.ConnectException: Connection refused: connect
    !STACK 0
    java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 
        java.net.ConnectException: Connection refused: connect
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)
        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:214)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
        at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnectionImpl_Stub.close(Unknown Source)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:516)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:456)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteOplrunLauncher.close(IloRemoteOplrunLauncher.java:567)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController.fireRunTerminated(IloRemoteRunController.java:167)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.requestAbort(IloAbstractRunController.java:817)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.terminate(IloAbstractRunController.java:886)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController$HeartBeatJob.run(IloRemoteRunController.java:119)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: java.net.ConnectException: Connection refused: connect
        at java.net.DualStackPlainSocketImpl.connect0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:90)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:380)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:236)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:218)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
        at java.net.Socket.connect(Socket.java:666)
        at java.net.Socket.connect(Socket.java:606)
        at java.net.Socket.<init>(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:239)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:52)
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:160)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:625)
        ... 13 more

    !ENTRY ilog.odms.ide.core 4 0 2018-02-03 20:54:12.569
    !MESSAGE Connection refused to host: 127.0.0.1; nested exception is: 
        java.net.ConnectException: Connection refused: connect
    !STACK 0
    java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 
        java.net.ConnectException: Connection refused: connect
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)
        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:214)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
        at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnectionImpl_Stub.close(Unknown Source)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:516)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:456)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteOplrunLauncher.close(IloRemoteOplrunLauncher.java:567)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController.fireRunTerminated(IloRemoteRunController.java:167)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.requestAbort(IloAbstractRunController.java:817)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.terminate(IloAbstractRunController.java:886)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController$1.handleDebugEvents(IloRemoteRunController.java:155)
        at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1151)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1187)
        at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:431)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: java.net.ConnectException: Connection refused: connect
        at java.net.DualStackPlainSocketImpl.connect0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:90)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:380)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:236)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:218)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
        at java.net.Socket.connect(Socket.java:666)
        at java.net.Socket.connect(Socket.java:606)
        at java.net.Socket.<init>(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:239)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:52)
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:160)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:625)
        ... 17 more

     

    I do not find the reason, Can you tell me where it is going wrong?

    Thanks a lot in advance!


    #CPLEXOptimizers
    #DecisionOptimization


  • 2.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Mon February 05, 2018 01:05 AM

    This usually happens when the engine crashes or runs out of memory. Can you try running your project directly from the command line using oplrun.exe (go to your project directory, make sure oplrun.exe is in your PATH and execute 'oplrun.exe *.mod *.dat').

    Also not that there is a forum dedicated to problems with OPL and the IDE. You may have better luck asking your question there.


    #CPLEXOptimizers
    #DecisionOptimization


  • 3.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Mon February 17, 2020 01:13 PM

    Originally posted by: AnaPedro


    Hello,

    I have a project running in IBM ILOG CPLEX Optimization Studio 12.10 and I found the same problem that you refer: "Oplrun process is not responding". I already solved this project on a machine with less memory using IBM ILOG CPLEX Optimization Studio 12.6…so it can´t be a memory problem. Were you able to solve your problem?

    Best regards,

    Ana Pedro


     


    #CPLEXOptimizers
    #DecisionOptimization


  • 4.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Mon February 17, 2020 04:47 PM

    And when you try with oplrun ?


    #CPLEXOptimizers
    #DecisionOptimization


  • 5.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Tue February 18, 2020 07:05 AM

    Do you see anything in the engine log? Can you post this log here?


    #CPLEXOptimizers
    #DecisionOptimization


  • 6.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Tue February 18, 2020 08:42 AM

    Originally posted by: AnaPedro


    Hi,

    I got this from the log...

     

    !ENTRY ilog.odms.ide.core 4 0 2020-02-18 00:08:28.121
    !MESSAGE Connection refused to host: 127.0.0.1; nested exception is:
        java.net.ConnectException: Connection refused: connect
    !STACK 0
    java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
        java.net.ConnectException: Connection refused: connect
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)
        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:214)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
        at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnectionImpl_Stub.close(Unknown Source)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:516)
        at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:456)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteOplrunLauncher.close(IloRemoteOplrunLauncher.java:564)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController.fireRunTerminated(IloRemoteRunController.java:167)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.requestAbort(IloAbstractRunController.java:817)
        at ilog.odms.ide.internal.core.run.IloAbstractRunController.terminate(IloAbstractRunController.java:886)
        at ilog.odms.ide.internal.core.run.remote.IloRemoteRunController$1.handleDebugEvents(IloRemoteRunController.java:155)
        at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1155)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1189)
        at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:442)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
    Caused by: java.net.ConnectException: Connection refused: connect
        at java.net.DualStackPlainSocketImpl.connect0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:90)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:380)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:236)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:218)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
        at java.net.Socket.connect(Socket.java:666)
        at java.net.Socket.connect(Socket.java:606)
        at java.net.Socket.<init>(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:239)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:52)
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:160)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:625)
        ... 17 more


    #CPLEXOptimizers
    #DecisionOptimization


  • 7.  Re: how to fix this problem, "OplRun is not responding, you must relaunch the RunConfig" in OPL IDE

    Posted Tue February 18, 2020 10:28 AM

    Sorry, this is not what I meant. What I meant is the "Engine Log" tab in the IDE. At the bottom view in the IDE there should be a tab titled "Engine Log". I am wondering if you can see any output there?

    Also, would it be possible to share the offending model and data so that we can try to reproduce here?


    #CPLEXOptimizers
    #DecisionOptimization