Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Grouptask with no owner Timeout Crashes TeamSite
System
I am trying to create a grouptask with a timeout that is set to an explicit date. If no user takes ownership of the task before the timeout occurs, it seems to crash TeamSite.
Attached is the XML that I passed to the workflow instantiator to create the task, followed by what iwgetwfobj now gives me for the task. Note that the timeout value was changed during workflow using iwsettasktimeout.
As I believe you can clearly tell from the expiration="1043789400", this task should have transitioned by timeout at 15:30 today (about 30 minutes ago central time). When this time was hit, TeamSite crashed. In the Windows Event Viewer I see:
The application, d:/releng/Release/hotgas/dev/main/dev/TS5.5/TS5.5.2L_SP1/iwbuild/nti86.REL/src/hammer/iwserver.exe, generated an application error The error occurred on 01/28/2003 @ 15:30:00.738 The exception generated was c0000005 at address 7993C355 ()
In IWHOME/local/logs/iwjoberrors.log I see:
[Tue Jan 28 15:30:00 2003] No role for .
A similar message appears in iwtrace.log:
[Tue Jan 28 15:30:00 2003] No role for .
I remember filing a support case some time ago about grouptask timeout events not activating if nobody had taken ownership of the task and I wonder if this the attempted resolution. It is also quite possible that I am doing something wrong. Does anyone know anything about this?
Find more posts tagged with
Comments
james1
I see bug 36437 seems to coincide with what you're talking about. I see that bug fixed in 5.5.2L SP1 and in 5.5.2 SP2. I assume you're on 5.5.2L SP1. Can you provide the output from "iwversion"?
-- James
--
James H Koh
Interwoven Engineering
Migrateduser
5.5.2 Build 11020 20020823
james1
OK, I think the bug was fixed for 5.5.2L SP1 after build 11020, so you should check Tech Support to see if there might be a patch available for you. If not, then I guess you will have to upgrade to SP2 to get the bug fix.
-- James
--
James H Koh
Interwoven Engineering