petrov-mg commented on issue #10907:
URL: https://github.com/apache/ignite/issues/10907#issuecomment-1703170657
> an error message was reported, and I have also posted the error message on
it
Could you please attach the **stacktrace** and not just the error message.
It should look something like this:
```
class org.apache.ignite.IgniteException: Access to Ignite Internal tasks is
restricted
[task=org.apache.ignite.internal.processors.closure.GridClosureProcessor$T6,
job=class org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2]
at org.apache.ignite.internal.util.lang.RunnableX.run(RunnableX.java:40)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.assertFailed(ComputeTaskPermissionsTest.java:549)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.checkCallable(ComputeTaskPermissionsTest.java:511)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.checkTaskStart(ComputeTaskPermissionsTest.java:347)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.testNode(ComputeTaskPermissionsTest.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2504)
at java.lang.Thread.run(Thread.java:750)
Caused by: class org.apache.ignite.plugin.security.SecurityException: Access
to Ignite Internal tasks is restricted
[task=org.apache.ignite.internal.processors.closure.GridClosureProcessor$T6,
job=class org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2]
at
org.apache.ignite.internal.processors.task.GridTaskWorker.authorizeSystemTaskJob(GridTaskWorker.java:1786)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:595)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:533)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:753)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:369)
at
org.apache.ignite.internal.IgniteComputeHandler.broadcastAsync(IgniteComputeHandler.java:362)
at
org.apache.ignite.internal.IgniteComputeImpl.broadcast(IgniteComputeImpl.java:282)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.lambda$checkTaskStart$13(ComputeTaskPermissionsTest.java:347)
at
org.apache.ignite.common.ComputeTaskPermissionsTest.lambda$checkCallable$9d5e5b8f$3(ComputeTaskPermissionsTest.java:511)
at org.apache.ignite.internal.util.lang.RunnableX.run(RunnableX.java:37)
... 14 more
```
Without **stacktrace** it's very hard to understand what's going on.
I even locally tested the project you are developing -
https://github.com/quickmsg/smqttx (I hope I'm not mistaken and the code
snippets mentioned above were based on this source). I upgraded the Ignite
dependency to 2.15, launched `io.github.quickmsg.jar.JarStarter` and
successfully ran the command to get information about the cluster
`http://localhost:60000/smqtt/cluster`. I could not reproduce the problem you
mentioned.
If any other steps are required to reproduce the problem, feel free to
describe them.
--
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]
