My Oracle Support Banner

Starting Webstart Java Client via Command Script (cmd) File Fails with Error: Application could not be started ... Server returned HTTP response code: 408 for URL (Doc ID 2026659.1)

Last updated on FEBRUARY 24, 2019

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 to 6.1.3.0 [Release 6.1.0]
Information in this document applies to any platform.

Symptoms

When attempting to start the WebStart Java-Client using a command script with command lines like

"<JAVA_HOME>\jre1.7\bin\javaws.exe" "http://<HOST>:<PORT>/Jacc/jacc.jnlp"

the following error occurs sporadically - an error window appears


Application Error:
Application could not be started
 More Information is showing
  Error: Unable to load resource:
   http://<HOST>:<PORT>/Jacc/jacc.jnlp?id=Lodd-uRBQUP9Dm...


The Java Webstart trace showing:

....

  cache: Resource
http://<HOST>:<PORT>/Jacc/jacc.jnlp?id=Lodd-uRBQUP9Dm8... has expired.

#### Java Web Start Error:
#### Server returned HTTP response code: 408 for URL:
   http://<HOST>:<PORT>/Jacc/jacc.jnlp?id=Lodd-uRBQUP9Dm...

...


Additional facts:

Java Cache never gets corrupted / never expires when starting the WebStart Java Client directly in browser with URL:

http://<HOST>:<PORT>/Jacc/jacc.jnlp

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


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