During my work, I had some issues with java-web-start (jws) and GlassFish v3.0.1 with activated “Security Manager”. The goal was to deploy a simple hello world Java EE 6 “Enterprise Application” with a “EJB-Module” and a “Enterprise Client Application” an run the “Enterprise Client Application” through the jws. The basic function was a “Remote Call” (@EJB) of a @javax.ejb.Stateless EJB out of my swing based “Enterprise Client Application”.

Certainly, this construct works fine inside Netbeans and without jws (“Enterprise Application” deployment out of Netbeans to GlassFish and starting the “Enterprise Client Application” directly).

directory deployment

jar-files which should started with jws (and all needed libraries) need a signature. Netbeans have the feature, that it can deploy a Application directly into the GlassFish Application directory. In this case GlassFish doesn’t sign the jar files. The are signed by Netbeans and his key. The result is, that the deployment fail and you get a message like:

1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module …

Solution: Deploy the application (.ear-file) through the web gui of GlassFish v3. Don’t forget to set the “Java Web Start”-Option in the “Deploy Applications or Modules”-Window. GlassFish auto sign all jar-files which are deployed with the web gui.

Server Permission

If you activate the “Security Manager” for GlassFish in the web gui (“Configuration”->”Security”), GlassFish can not sign the jar-files. You get some exception as followed (it’s a summary):

java.io.IOException: Server returned HTTP response code: 500 for URL:http://….
JACC Policy Provider: Failed Permission Check, context(null)- permission((java.lang.RuntimePermission accessClassInPackage.sun.misc))
java.lang.RuntimeException: java.io.IOException: java.lang.Exception: Error attempting to create signed jar /opt/glassfish/…
Caused by: java.io.IOException: java.lang.Exception: Error attempting to create signed jar
Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission accessClassInPackage.sun.misc)

Solution: Add following lines into the policy-file(server.policy) of the GlassFish-Domain:

//JWS Permission
//JACC Policy Provider: Failed Permission  Check, context(null)- permission java.lang.RuntimePermission  accessClassInPackage.sun.misc
grant {
permission java.lang.RuntimePermission "accessClassInPackage.sun.misc";
permission java.lang.RuntimePermission "accessClassInPackage.sun.security.*";
};

client and server cache

When I have made an update the “Enterprise Client Application” should actually update itself automatically. However, Java does not always recognize the new version. In that case, you can force the update / a fresh download by doing the following:
Start -> Run -> Type “javaws -viewer” (without the quotes) -> Ok

A window named “Java Cache Viewer” should pop up. In that window, delete everything that look like your Application, close it and try to start the jws again. You should see a download window for the new version and the program should start normally.

When I did major reconfiguration on GlassFish and/or I believed “it should work, but it didn’t” I made the same on my server

bash# rm -r /opt/glassfishv3/glassfish/domains/domain1/java-web-start/
bash# rm -r /opt/glassfishv3/glassfish/domains/domain1/osgi-cache/