I cannot reproduce the problem using the procedure described.
However the same stack trace can be reproduced if I start javaws with a extra slash "/" in front. We suspect this bug is the same instance as 4494155.
There are 2 problems at work here:
1. The install script does not correctly construct the path to the javaws
directory if javaws is installed in the root directory on Unix. In this case,
it will think the path to the javaws script is //javaws/javaws, this is the path
that is used when an app is started through the browser. Because of this, apps
started through the browser encounter the problem in 2.
2. If a javaws app is invoked on Unix with an extra slash at the beginning of the path (e.g. "//javaws/javaws app.jnlp"), the javaws system code itself will
not be assigned the correct permissions resulting in lots of
AccessControlExceptions and a hung app. When javaws is invoked, the shell
script takes the invocation command ("//javaws/javaws"), and passes it to the
native code. The native code constructs a file URL from this, which points to
the security policy file, and passes this to java code. (The policy file gives
javaws system code all permissions). The extra slash causes the URL to be
malformed and javaws system code ends up not being assigned all-permissions,
causing the ACExceptions.
I think we should fix both 1 and 2. 1 is easily fixed by special casing an
install in the root directory in the install script. 2 is fixed by checking
the invocation command in the install script for double slashes, and changing
them to a single slash.