humbinal opened a new issue, #13423:
URL: https://github.com/apache/dolphinscheduler/issues/13423

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   when using JDK17 to start Dolphinscheduler,and then exec Shell Node, The 
following log appears:
   ```
   [INFO] 2023-01-18 08:02:15.097 +0000 - raw script : echo "hello, ds!"
   [INFO] 2023-01-18 08:02:15.097 +0000 - task execute path : 
/tmp/dolphinscheduler/exec/process/root/8268588038176/8268598608032_1/1/1
   [INFO] 2023-01-18 08:02:15.098 +0000 - Begin to create command 
file:/tmp/dolphinscheduler/exec/process/root/8268588038176/8268598608032_1/1/1/1_1.command
   [INFO] 2023-01-18 08:02:15.099 +0000 - Success create command file, command: 
#!/bin/bash
   BASEDIR=$(cd `dirname $0`; pwd)
   cd $BASEDIR
   source /usr/local/dolphinscheduler/worker-server/conf/dolphinscheduler_env.sh
   
/tmp/dolphinscheduler/exec/process/root/8268588038176/8268598608032_1/1/1/1_1_node.sh
   [INFO] 2023-01-18 08:02:15.102 +0000 - task run command: sudo -u root -E 
bash 
/tmp/dolphinscheduler/exec/process/root/8268588038176/8268598608032_1/1/1/1_1.command
   [ERROR] 2023-01-18 08:02:15.105 +0000 - Unable to make field private final 
int java.lang.ProcessImpl.pid accessible: module java.base does not "opens 
java.lang" to unnamed module @93c2679
   java.lang.reflect.InaccessibleObjectException: Unable to make field private 
final int java.lang.ProcessImpl.pid accessible: module java.base does not 
"opens java.lang" to unnamed module @93c2679
        at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
        at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
        at 
java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
        at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
        at 
org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.getProcessId(AbstractCommandExecutor.java:432)
        at 
org.apache.dolphinscheduler.plugin.task.api.AbstractCommandExecutor.run(AbstractCommandExecutor.java:205)
        at 
org.apache.dolphinscheduler.plugin.task.shell.ShellTask.handle(ShellTask.java:96)
        at 
org.apache.dolphinscheduler.server.worker.runner.DefaultWorkerDelayTaskExecuteRunnable.executeTask(DefaultWorkerDelayTaskExecuteRunnable.java:49)
        at 
org.apache.dolphinscheduler.server.worker.runner.WorkerTaskExecuteRunnable.run(WorkerTaskExecuteRunnable.java:174)
        at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at 
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
        at 
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:74)
        at 
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)
   [INFO] 2023-01-18 08:02:15.105 +0000 - process start, process id is: 0
   ```
   
   Of course, the node executes correctly, Just the log is weird。
   
   when using JDK11,no logs appeared。
   
   
   ### What you expected to happen
   
   no error logs.
   
   ### How to reproduce
   
   using jdk17, run shell node.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to