I am experiencing and issue when I want to trigger a remote parameterized job and send little or no parameters.

Build #39 never exists on the end system. All the parameters of the job have default values, when triggering I would expect that if a parameter is not passed, the default should be used. Utlimately, the job is not triggered(run). It looks as though the remote server is not returning what is expected?

Started by user anonymous
[EnvInject] - Loading node environment variables.
Building on master in workspace /localdisk/jenkins/jobs/RemoteCallJob/workspace
Triggering this remote job: SCMExecutioner1
Not checking if the remote job SCMExecutioner1 is building.
Triggering remote job now.
Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build.
Checking parameters of #39
Remote Jenkins server returned empty response or invalid JSON - but we can still proceed with the remote build.
Query failed.
Checking parameters of #38
Unable to find expected value for protocol
Unable to find expected value for web.path
Unable to find expected value for ls.branch.dir
Unable to find expected value for ls.artifact.dir
Unable to find expected value for browser.type
Unable to find expected value for browser.version
Unable to find expected value for platform
Unable to find expected value for anttesttarget
Unable to find expected value for test_label
Unable to find expected value for admin.server
Unable to find expected value for hadoop.cluster.host.name
Unable to find expected value for dp.host.name
Unable to find expected value for bdd.admin.cli.path
Unable to find expected value for dp.cli.install.path
Unable to find expected value for REVISION
Unable to find expected value for df.buildBranchName
Unable to find expected value for suite
Unable to find expected value for fetch.deps.root
This job is build #[38] on the remote server.
Not blocking local job until remote job completes - fire and forget.
Notifying upstream projects of job completion
Finished: SUCCESS