Normally, when we run a job on our local machine it picks up our local kettle.properties variables values. Then, when we schedule the job, because it is then running through the repository on our Linux server, it picks up the Linux kettle.properties variable values. This is all good (and important!).
HOWEVER, we've recently had an issue where newly-created jobs that run through the scheduler are picking up the kettle.properties values from the local Windows machine that scheduled the job. This is a problem!
Has anyone seen this before or have any suggestions about what to check? We've validated that the $KETTLE_HOME path is properly set on the Linux server and that the kettle.properties file is under that directory. We've checked the contents of the Linux kettle.properties file. We've rebooted our Linux server and our local machines.
We're running 4.4.2-GA
Note, a job that was created and scheduled a while back is still regularly running through the scheduler and picking up the correct Linux-based kettle.properties values.
HOWEVER, we've recently had an issue where newly-created jobs that run through the scheduler are picking up the kettle.properties values from the local Windows machine that scheduled the job. This is a problem!
Has anyone seen this before or have any suggestions about what to check? We've validated that the $KETTLE_HOME path is properly set on the Linux server and that the kettle.properties file is under that directory. We've checked the contents of the Linux kettle.properties file. We've rebooted our Linux server and our local machines.
We're running 4.4.2-GA
Note, a job that was created and scheduled a while back is still regularly running through the scheduler and picking up the correct Linux-based kettle.properties values.