[
https://issues.apache.org/jira/browse/IGNITE-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-23165:
--------------------------------------
Description:
When running a compute job without deployment unit declared the job class
couldn't be loaded if it's not in the app classpath already.
The following exception is thrown:
{noformat}
Exception in thread "main" org.apache.ignite.compute.ComputeException:
IGN-COMPUTE-3 TraceId:... Cannot load job class by name 'test.Job'
{noformat}
The root cause is that when no units are declared a classloader is created with
empty classpath.
This is ok if we are in the embedded node and the job could be in the app
classpath.
We should check if the classpath was empty in this case and provide a
suggestion to check the units declaration.
was:
When running a compute job without deployment unit declared the job class
couldn't be loaded if it's not in the app classpath already.
The following exception is thrown:
{noformat}
Exception in thread "main" org.apache.ignite.compute.ComputeException:
IGN-COMPUTE-3 TraceId:... Cannot load job class by name 'test.Job'
{noformat}
The root cause is that when no units are declared a classloader is created with
empty classpath.
We should check if the classpath is empty in this case and provide a suggestion
to check the units declaration.
> Improve error message when deployment unit is not provided
> ----------------------------------------------------------
>
> Key: IGNITE-23165
> URL: https://issues.apache.org/jira/browse/IGNITE-23165
> Project: Ignite
> Issue Type: Improvement
> Components: compute
> Reporter: Vadim Pakhnushev
> Assignee: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
>
> When running a compute job without deployment unit declared the job class
> couldn't be loaded if it's not in the app classpath already.
> The following exception is thrown:
> {noformat}
> Exception in thread "main" org.apache.ignite.compute.ComputeException:
> IGN-COMPUTE-3 TraceId:... Cannot load job class by name 'test.Job'
> {noformat}
> The root cause is that when no units are declared a classloader is created
> with empty classpath.
> This is ok if we are in the embedded node and the job could be in the app
> classpath.
> We should check if the classpath was empty in this case and provide a
> suggestion to check the units declaration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
