Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks that run on nodes created with : java -jar node.jar , fail. #3243

Open
marcocast opened this issue Jun 14, 2018 · 0 comments
Open

Tasks that run on nodes created with : java -jar node.jar , fail. #3243

marcocast opened this issue Jun 14, 2018 · 0 comments
Milestone

Comments

@marcocast
Copy link
Contributor

when I start a node using java -jar node.jar, if I run a task on it, it fails

33t0@mortadella;10:09:16] Logging initialized @631ms [33t0@mortadella;10:09:16] jetty-9.2.14.v20151106 [33t0@mortadella;10:09:16] Started o.e.j.s.ServletContextHandler@123f1134{/proactive,null,AVAILABLE} [33t0@mortadella;10:09:16] Started ServerConnector@1a84f40f{HTTP/1.1}{0.0.0.0:50645} [33t0@mortadella;10:09:16] Started @873ms [33t0@mortadella;10:09:22] java.security.AccessControlException: access denied ("java.io.FilePermission" "C:\Users\fviale\AppData\Local\Temp\PA_JVM1949452224\mortadella_10628\33t0\-89669796\0007968222938111624675.tmp" "read") [33t0@mortadella;10:09:22] at java.security.AccessControlContext.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.security.AccessController.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.lang.SecurityManager.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.lang.SecurityManager.checkRead(Unknown Source) [33t0@mortadella;10:09:22] at java.io.File.exists(Unknown Source) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.deleteContextFile(ExecuteForkedTaskInsideNewJvm.java:72) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.deserializeContext(ExecuteForkedTaskInsideNewJvm.java:66) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.fromForkedJVM(ExecuteForkedTaskInsideNewJvm.java:113) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.main(ExecuteForkedTaskInsideNewJvm.java:105) [33t0@mortadella;10:09:22] Could not serialize exception as task result: [33t0@mortadella;10:09:22] java.security.AccessControlException: access denied ("java.io.FilePermission" "C:\Users\fviale\AppData\Local\Temp\PA_JVM1949452224\mortadella_10628\33t0\-89669796\0007968222938111624675.tmp" "write") [33t0@mortadella;10:09:22] at java.security.AccessControlContext.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.security.AccessController.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.lang.SecurityManager.checkPermission(Unknown Source) [33t0@mortadella;10:09:22] at java.lang.SecurityManager.checkWrite(Unknown Source) [33t0@mortadella;10:09:22] at java.io.FileOutputStream.<init>(Unknown Source) [33t0@mortadella;10:09:22] at java.io.FileOutputStream.<init>(Unknown Source) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.serializeTaskResult(ExecuteForkedTaskInsideNewJvm.java:89) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.fromForkedJVM(ExecuteForkedTaskInsideNewJvm.java:121) [33t0@mortadella;10:09:22] at org.ow2.proactive.scheduler.task.executors.forked.env.ExecuteForkedTaskInsideNewJvm.main(ExecuteForkedTaskInsideNewJvm.java:105)

Command line is something like this

java -Dproactive.communication.protocol=pamr -Dproactive.pamr.router.address=trydev.activeeon.com -jar node.jar -f "your_cred.txt" -r pamr://4096

Problem maybe comes from this:

-Djava.security.policy=onejar:/lib/rm-node-8.2.0-SNAPSHOT.jar/config/security.java.policy-client
this is what is forwarded to the forked JVM

Not sure this url is understandable by the forked jvm...

You need to run a task on it using a selection script, script console will not raise the issue (only tasks runs in the forked jvm).

The problem seems to be really this url for java.security.policy AND proactive.configuration,
both have a onejar url, log4J.configuration has a correct url

@marcocast marcocast added this to the 8.2.0 milestone Jun 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant