nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Target path unavailable. Will keep checking.

System

We had a major update to one of our sites today, and many deployments failed due to the below error. Log file attached - devnet search as usual doesnt return anything...

many users were pushing many workflows through at the same time

ENG: 2009-11-24 10:03:11 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:16 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:22 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:27 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:33 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:38 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:44 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:49 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:03:54 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:04:00 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.
ENG: 2009-11-24 10:04:05 EST GMT-05:00 Thread-916 Target path unavailable. Will keep checking.

Find more posts tagged with

Comments

Pawan

Since you are saying that many users simultaneously deployed content and I assume to the same directory path, then the blockCheckInterval must be equal to 5 seconds as you must have noticed in the logs. The deployment fails if the value specified for the blockMaxWaitTime exceeds, by default its 300 seconds. You may increase the value of the two attributes and clear your registry using the command iwodcmd serverreset -clearpathreg <pattern> if no pattern is specified then all the paths are cleared. Try this on your dev box first let us know how it works.

Migrateduser

what are the recommended/best practice settings for these if there are a lot of concurrent deployments?

Pawan

what are the recommended/best practice settings for these if there are a lot of concurrent deployments?

As mentioned earlier, you may increase the delay with the two attributes based on your statistics. Along with this you should always have a unique instance name for each deployment. However, these settings depend a lot on your architecture like multi-tier deployment, transactional deployment, dnr, etc. Experts may add their thoughts here.

Adam Stoller

what are the recommended/best practice settings for these if there are a lot of concurrent deployments?

If these are all transactional deployments, then I'd think you'd want to enable receiver-side queuing.

It's covered in the manuals and discussed in at least two threads that I recall having responded to about it.