Closed glassfishrobot closed 7 years ago
Reported by ayakovlev
@jwells131313 said: So looking at the stack trace we can see that hk2 is doing a doPriviledged:
at java.security.AccessController.doPrivileged(AccessController.java:32)
This means that hk2 is doing the correct thing and that instead whomever is granting rights must not have included the hk2 libraries. I would suggest running with
-Djava.security.debug=access,failure,domain
This will tell you what protection domain failed to have the priv. Then figure out who is granting privs and check to be sure that all the hk2 jars have the necessary right. An example grant file is here: https://github.com/hk2-project/hk2/blob/master/hk2-locator/src/test/resources/policy.txt
In general it is safe to grant java.security.AllPermission to hk2 jars
@jwells131313 said: We can see from the stack trace that hk2 is inside a doPriv block, and hence this has to do with what is being granted
ayakovlev said: Thank you for your answer. But, as I wrote, GAE is PaaS and we cannot modify java security policies: https://cloud.google.com/appengine/docs/standard/java/runtime#Java_The_sandbox
Do you mean that this issue is on App Engine side? If so, I still don't understand why it worked in HK2 2.4.0-b34 and earlier.
This issue was imported from java.net JIRA HK2-307
Marked as won't fix on Thursday, March 16th 2017, 4:43:38 am
The issue occurs after HK-306 when I rolled back Jersey version to 2.23.2 with HK2 2.5.0-b05.
It happens for each request to Jersey Application.
The stacktrace:
Here are some facts:
I have the following maven configuration:
Environment
Google App Engine Standard Environment
Affected Versions
[2.5.0]