1 Reply Latest reply on Apr 26, 2010 4:52 PM by Chris NameToUpdate

    post-provisioning batch - strange behavior

      I am alternately getting two strange results in post-provisioning batch jobs.  One or the other of these always seems to happen with this one batch  job.  Sometimes the jobs fail with no rscd_dir property defined, other times a second instance of the batch job is launched about 5 or 10 seconds after the first starts (and the rscd_dir is apparently properly defined).


      All the contained deploy jobs fail when the first happens of course, though NSH script jobs run fine.  When the second happens, often between the two everything will succeed, with one instance of a deploy job failing because "setup is already running" or something and the other succeeding.


      Anyone even seen anything like this?