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; } } }

Strange iwtrace error message

Bill Klish

TeamSite 6.5 SP1
Solaris 2.9

Any idea what these error messages mean below? There are quite a few of these in the log file tonight.

[Mon Dec 11 21:09:13 2006] Store : Snapshot encountered 1 referenced mfd points, first ref mfd point id = 718CF2.
[Mon Dec 11 21:09:14 2006] Store : Snapshot encountered 1 referenced mfd points, first ref mfd point id = 7193E5.
[Mon Dec 11 21:09:15 2006] Store : Snapshot encountered 1 referenced mfd points, first ref mfd point id = 719A9C.

Find more posts tagged with

Comments

Frederik

not me. But for backing store related messages I would make a support case immediately. Better safe than sorry ;-)

Bill Klish

Response from support in case anyone else sees this:

This is a timing issue (non-issue, really) related to the order in which critical sections and flush helpers are acquired in the workflow store. Workflow operations acquire the flush helper AFTER acquiring the critical section (opposite of non-workflow stores), because there are some long running workflow operations which must hold the critical section for their entire duration. Releasing a flush helper potentially triggers a snapshot, which in the case of a destroy workflow operation may occur before the operation's critical section (and corresponding handle) are released, resulting in the message you see in iwtrace.log.

Also there is a bug related to these 68005. The bug is related to TS 6.5 sp1 and sp2.

pbarua

Bill,
Hopefully you still remember this stuff :-) Can you explain to me what you really mean by "Releasing a flush helper potentially triggers a snapshot, which in the case of a destroy workflow operation may occur before the operation's critical section (and corresponding handle) are released"?

We're seeing the same message in iwtrace, and it's for a workflow id that's been ended. Also looks like workflow store is not able to purge this item from its cache. FYI, the WA that this WF was created from, was removed before this job was ended.

Thanks,
Pallabi

Response from support in case anyone else sees this:

This is a timing issue (non-issue, really) related to the order in which critical sections and flush helpers are acquired in the workflow store. Workflow operations acquire the flush helper AFTER acquiring the critical section (opposite of non-workflow stores), because there are some long running workflow operations which must hold the critical section for their entire duration. Releasing a flush helper potentially triggers a snapshot, which in the case of a destroy workflow operation may occur before the operation's critical section (and corresponding handle) are released, resulting in the message you see in iwtrace.log.

Also there is a bug related to these 68005. The bug is related to TS 6.5 sp1 and sp2.

phenom

We encountered the exact same issue on TS 6.5 SP3. Is contacting Autonomy's support the only way to proceed?