Running the Procurement Solver Causes Dash and Application Server to Crash (Doc ID 744777.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

-- Problem Statement:
On Oracle Transportation Management (OTM) version 5.5.03 to 5.5.05 :

When attempting to run any Procurement actions that use Dash, the application server will crash and the
following error is generated in the application server's console.log:

ERROR:

INFO | jvm 2 | 2008/03/12 15:32:59 | Stack 0: start=0xf59ad000, end=0xf59ef000, guards=0xf59b2000 (ok), forbidden=0xf59b0000
INFO | jvm 2 | 2008/03/12 15:32:59 | Thread Stack Trace:
INFO | jvm 2 | 2008/03/12 15:32:59 | -- Java stack --
INFO | jvm 2 | 2008/03/12 15:32:59 | at com/dashoptimization/XPRS.license(Lcom/dashoptimization/IntHolder;Lcom/dashoptimization/StringHolder;)I(Native Method)
INFO | jvm 2 | 2008/03/12 15:32:59 | at glog/optimization/mip/dash/DashSolver.initializeLicense()Z(DashSolver.java:89)
INFO | jvm 2 | 2008/03/12 15:32:59 | ^-- Holding lock: java/lang/Class@0xd8c8398[thin lock]
INFO | jvm 2 | 2008/03/12 15:32:59 | at glog/optimization/mip/dash/DashSolver.<init>(Lglog/optimization/util/OptimizationTask;)V(DashSolver.java:43)
INFO | jvm 2 | 2008/03/12 15:32:59 | at glog/optimization/mip/MIPSolver.getLocalSolver(Lglog/optimization/util/OptimizationTask;Lglog/optimization/mip/MIPSolverType;)Lglog/optimization/mip/MIPSolver;(MIPSolver.java:80)
INFO | jvm 2 | 2008/03/12 15:32:59 | at glog/optimization/mip/MIPSolver.getSolver(Lglog/optimization/util/OptimizationTask;Lglog/optimization/mip/MIPSolverType;)Lglog/optimization/mip/MIPSolver;(MIPSolver.java:71)

-- Steps To Reproduce:

1. Log into the OTM instance and access the Dash test servlet via the the following URL:

glog.webserver.optimization.test.SolverDiagServlet

After you log in the following URL would be displayed in the browser's address line.

http://<otm_url>/GC3/glog.webserver.util.FrameGC3Servlet

Change the URL to this:

http://<otm_url>/GC3/glog.webserver.optimization.test.SolverDiagServlet

The servlet will open a OTM Solver Testing Screen.

2. Choose "Solver" = "Dash" and "Tests" = "TravellingSaleman" and click Solve.

Instead of the typical response, an error will be generated on the screen referencing a connection failure with the application server, but a review of the application server's console logs will show the errors mentioned above.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.