Glassfish DeploymentException: Error in linking security policy for

Question

I have been trying to deploy my web application (war) from Glassfish AdminConsole but I keep getting the following error message -

Exception while loading the app : Error in linking security policy for MyApp-war -- Inconsistent Module State.

But it deploys without any problem when I do it from Netbeans. (I don't know if Netbeans is doing something that I am missing before deploying the application.)

And I also tried with the latest version of Glassfish (i.e. V3.1.1 (build 12) ), and I can deploy the same application without any problem from AdminConsole.

I am using Glassfish 3.1 (build 43) and Netbeans 7.0.

Is there any Security Policy setting that I have to have before deploying my application with this version of Glassfish?

score 105 · Accepted Answer · answered Aug 02 '12 at 03:23

The same thing was happening to me.

Here is what I did:

Stoped the Glassfish server
Deleted all the content from glassfishhome/glassfish/domains/yourdomainname/generated
Started Glassfish

It worked for me. But what still sucks is that everytime I need to deploy I need to follow this procedure again...

score 42 · Answer 2 · answered Sep 09 '13 at 13:38

42

I will answer this in response to the comment of @SteveTaylor. His answer in the above comment helped me solving the problem, so he is the one who deserves the credits.

Original answer from @SteveTaylor:

The problem is a corrupt OSGi cache. The reason upgrading worked for you is because you started with a clean OSGi cache. All that's needed to fix this problem is delete the entire OSGi cache under $GLASSFISH_HOME/glassfish/domains//osgi-cache

This answer worked for me as well. Thanks a lot. I am using a cluster (Oracle GlassFish 3.1.2.2) consisting of two nodes and a domain server. I removed the OSGi cache under all three directories (2 nodes and domain) after I stopped the cluster and restarted it then. After that, the problem was solved.

answered Sep 09 '13 at 13:38

qupera

1,039
9
6

Thanks. Worked for me as well!! – Amila Fonseka Sep 27 '16 at 00:36
Worked for me - had to remvoe the generated and osgi-cache directories and restart the appserver :) – SidJ Dec 27 '17 at 05:12
This is what worked for me also, I was already trying to delete the domains/domain1/generated/* but did not work. Deleting the osgi-cache/* worked. – Spyros K Jun 14 '18 at 13:00
Thanks. Worked for me without removing the /generated. – dadan Oct 20 '20 at 09:54

score 2 · Answer 3 · answered Feb 29 '12 at 11:29

2

It happen to me to, especially after I check out different version of my web application and try to deploy it to Glassfish.

The only certain solution I've found is to completely stop galssfish, restart it and deploy the application.

answered Feb 29 '12 at 11:29

Ido Ran

10,584
17
80
143

This was my option, and server throws this exception: javax.management.RuntimeMBeanException: java.lang.RuntimeException: java.lang.IllegalStateException: BootAMX listener was not called – angelcervera Oct 17 '12 at 17:40
1

The BootAMX listener exception is not relevant, and is completely safe to ignore. – Pawel Veselov Apr 16 '15 at 21:45

score 1 · Answer 4 · answered Dec 28 '18 at 10:42

1

In my case, I was missing @Stateless tag in one of my Managed Beans. Adding it, solved it for me. Hope it helps.

answered Dec 28 '18 at 10:42

Ricardo F.

496
1
4
11

score 1 · Answer 5 · answered Sep 29 '11 at 02:26

1

Probably a bug in the version of Glassfish I was using.

Basically changing to a different (later) version solved the problem.

answered Sep 29 '11 at 02:26

Bhesh Gurung

50,430
22
93
142

For me, the change to GlassFish 3.1.2.2 (not 3.1.2!) helped. – Benny Code Aug 27 '12 at 13:15
+Bhesh Gurung, I believe it's not bug. – Sree Rama Nov 21 '12 at 07:35
to resolve the issue : restart the server/clean the project after that run the application. It should mostly work because it worked for me without switching to 3.1.2.2. – Sree Rama Nov 21 '12 at 07:38
11

The problem is a corrupt OSGi cache. The reason upgrading worked for you is because you started with a clean OSGi cache. All that's needed to fix this problem is delete the entire OSGi cache under `$GLASSFISH_HOME/glassfish/domains//osgi-cache`. – Steve Dec 16 '12 at 16:04
@SteveTaylor your answer worked for me as well. Thanks a lot. I am using a cluster (Oracle GlassFish 3.1.2.2) consisting of two nodes and a domain server. I removed the OSGi cache under all three directories (2 nodes and domain) after I stopped the cluster and restarted it then. After that, the problem was solved. – qupera Sep 09 '13 at 13:35

score 0 · Answer 6 · answered Apr 26 '12 at 13:35

I don't know if this helps, but I got the same error when deploying from the command line. In my case I'm using a pretty up-to-date version (GlassFish Server Open Source Edition 3.1.2 (build 23)). What worked for me was removing --force=true from this:

  $ sudo /usr/local/glassfish3/bin/asadmin deploy --force=true ~cornell/designer.war

What's important (I think) is that I had not previously deployed the app. Confusing!

score 0 · Answer 7 · answered Jan 04 '21 at 06:13

0

In my case ,just I do "clean and build". that usually works well.

answered Jan 04 '21 at 06:13

naturallucky

1
3

Erick Alves · Answer 8 · 2013-03-15T20:08:28.427

-1

It happen to me too. In my case, it have occurred when I try to deploy the project and forget to start the database server, and then when I start the database server and I deployed again, I got this error message. When this occurred, I recompile the code, stop the server, undeploy the old project and deploy the new again.

edited Mar 15 '13 at 20:08

answered Mar 15 '13 at 17:39

Erick Alves

354
1
4
10

Glassfish DeploymentException: Error in linking security policy for

8 Answers8

Linked