There are two main issues in your cron schedule:

1. The source command may not be supported by the shell that interprets the command in the schedule. This depends on what shell /bin/sh is on your system (dash does not support the non-standard source command). Make sure to use . (a dot) in place of source to make your command portable. See e.g. Can't use `source` from cron?

2. The % character has a special meaning in crontabs, and must be escaped as \% if you want to use it as you would ordinary use it on the command line. See How can I execute `date` inside of a crontab job?

3. A possible third issue is whether or not the java executable is found or not, and this depends on the value of the PATH variable in the cron environment. If you want to ensure that java is found, set PATH to include the correct directory in the crontab, or in the environment file that you source, or invoke the executable with its absolute path.

There are a few issues in your cron schedule:

1. The % character has a special meaning in crontabs, and must be escaped as \% if you want to use it as you would ordinary use it on the command line. See How can I execute `date` inside of a crontab job?

2. The source command may not be supported by the shell that interprets the command in the schedule. This depends on what shell /bin/sh is on your system (dash does not support the non-standard source command). Make sure to use . (a dot) in place of source to make your command portable. See e.g. Can't use `source` from cron?

3. A possible third issue is whether or not the java executable is found or not, and this depends on the value of the PATH variable in the cron environment. If you want to ensure that java is found, set PATH to include the correct directory in the crontab, the environment file you source, or invoke the executable with its absolute path.

There are two main issues in your cron schedule:

1. The source command may not be supported by the shell that interprets the command in the schedule. This depends on what shell /bin/sh is on your system (dash does not support the non-standard source command). Make sure to use . (a dot) in place of source to make your command portable. See e.g. Can't use `source` from cron?

2. The % character has a special meaning in crontabs, and must be escaped as \% if you want to use it as you would ordinary use it on the command line. See How can I execute `date` inside of a crontab job?

There are two main issues in your cron schedule:

1. The source command may not be supported by the shell that interprets the command in the schedule. This depends on what shell /bin/sh is on your system (dash does not support the non-standard source command). Make sure to use . (a dot) in place of source to make your command portable. See e.g. Can't use `source` from cron?

2. The % character has a special meaning in crontabs, and must be escaped as \% if you want to use it as you would ordinary use it on the command line. See How can I execute `date` inside of a crontab job?

3. A possible third issue is whether or not the java executable is found or not, and this depends on the value of the PATH variable in the cron environment. If you want to ensure that java is found, set PATH to include the correct directory in the crontab, or in the environment file that you source, or invoke the executable with its absolute path.