The creation of a job resource is synchronized. There had been
some very rare issues where a service thread creating a managed
job resource kept stuck and blocked subsequent threads an caused
all available service threads to be consumed. This finally caused
the container to keep stuck.
This synchronization seems to be unnecessary. However, if we
remove the synchronization here we must take care that access to
the idempotence id map managed in MEJHome is synchronized properly.