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

Regeneration process Hanging!

Tim__D

When I regenerate multiple templated files from the GUI in 6.5 the regeneration process fails to regenerate all the files. On the server perl.exe iwregenhtml.cgi and IW_CGI~1.CGI processes are started but never finish. Only a few of the files selected are regenerated and the screen that displays which files were regenerated is never displayed.

I'm trying to debug using the iwpt_compile.ipl -ocode method but its a nightmare. Is this something that any of you have seen in the past and know how to fix or troubleshoot?

Find more posts tagged with

Comments

Migrateduser

In your PT, why don't you log information to some file and when you're in the process of generating all of these files, do a "tail -f" on the log to see where it's hanging.

Also, what is happening to the CPU on the TeamSite server? What does `top` or Task Manager tell you while the files are regenerating?

Dave

Environments:
(1,2) TS6.5SP1, TS6.5SP2 on W2K3
(3) Vignette V7 Portal on Solaris 9

Tim__D

I'm not logging anything right now. The structure is a single DCR with about 8 different PT's all drawing on the same DCR. Regenerated separately everything works fine. When regenerated together depending on which file and corresponding PT's you invoke you can regenerate between 2 - 4 files at the same time but not all of them.

On the server initially the processes I listed above get created but then fail to quit when they are finished. Then the process stops. If I manually kill the process new ones are created and the regeneration begins with a wide range of success.

I should also mention that there are at least 3 additional component PT's being used recursivly on some of these pages.

Edited by Tim__D on 01/31/06 01:45 PM (server time).

Migrateduser

Right, okay, but what I'm wondering is if you were to log information from each of your PT's, you might find where it's hanging. Of course, this could be just an exercise and it may hang at different places each time -- I'd also be curious to know what your PT's are doing. Is one or more of them trying to access a resource that might be locked by another PT? What OS is this running on? Also, why not invoke the PT's serially instead of several at a time?

Dave

Environments:
(1,2) TS6.5SP1, TS6.5SP2 on W2K3
(3) Vignette V7 Portal on Solaris 9

Tim__D

Users select the files from a list and choose to regenerate them. That process will not be changing in the near future so it needs to complete the regeneration process.

Creating a separate log file for each PT could help. Thanks for that. Still it does seem to be irregular. The PT's do lock and write to a resource and unlock it as well when finished. This code has remained unchanged from the 5.5.2 version of Teamsite. That said, even in I comment out this bit in my PT's I have the problem so I'm not sure its a locking issue. When regenerating most of the PT's they are pulling from three other types of data records as components.

Edited by Tim__D on 01/31/06 01:53 PM (server time).

Tim__D

I've fixed this issue and want to share the resolution for those who find this post in a search and may have similar problems.

This is documented but I'll go over it here as well just in case.

I started by creating a .ipl file using the iwpt_compile.ipl command. I created one file for each of my PT's. See upper case text for parameters. One thing that stumped me initially was I omitted -iw_include-location. If your PT has any iw_includes you need this parameter.

iwpt_compile.ipl -iw_include-location FULL_PATH_TO_WORKAREA -pt FULL_PATH_TO_TPL -iw_pt-dcr FULL_PATH_TO_PRIMARY_DCR -ocode d:\FILE.IPL

Next you can setup through the .ipl file(s) using the below command. The |more lets you see the script 1 step at a time. I tried the graphical debugger but found -w more useful than the -d switch.

perl -w file.ipl|more

After I fixed all the warnings in my PT's which were valid complaints the regen process worked fine.

Hope this helps. See documentation on iwpt_compile.ipl for exact details.

Edited by Tim__D on 02/02/06 03:57 PM (server time).

Tim__D

Dave,

Thanks. Your comment about logging got me thinking in the right direction. Thanks for responding.

- TD