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

iwat issue ?

nipper

TS 6.7.1, WIn2K

I set up an iwat trigger:

>iwat GroupTaskTaken "C:/interwoven/iw-home/iw-perl/bin/iwperl c:/interwoven/iw-home/custom/wft/bin/take_cgi.ipl"

>C:\interwoven\iw-home\iw-perl\bin\iwperl c:\interwoven\iw-home\custom\wft\bin\take_cgi.ipl

>iwlsat
ID: 53903 "GroupTaskTaken" C:/interwoven/iw-home/iw-perl/bin/iwperl c:/interwoven/iw-home/custom/wft/bin/take_cgi.ipl

So it is registered, the script works (it dumps command line parameters and ENV variables to a file).

But when I register the thing, an iwperl process runs and chews up 100% of my cpu.

By iwrmat and rebooting, I fix my server.

Am I doing anything obviously wrong ? I am trying to catch a group take task event.

Tips/Pointers/RTFMs appreciated.

Andy

Find more posts tagged with

Comments

Bill Klish

Simple mistake, but nice feature for it to go to 100% cpu.

The event name should be TaskGroupTaken

I agree with your logicial name, but it should be the name above. Hope that helps.

nipper

Changed that, still no trigger fires. The 100% CPU was due to MT running on an empty XML file.

I see the event in the event log:

[Mon Feb 26 20:22:09 2007] vmware2k\andy Unknown TaskGroupTaken FastTrack 0x9d04 AdminFix 0x9d35 vmware2k\andy

iwlsat
ID: 54303 "TaskGroupTaken" C:/interwoven/iw-home/iw-perl/bin/iwperl
c:/interwoven/iw-home/custom/wft/bin/take_cgi.ipl

where else can I look ?

Andy

Adam Stoller

Changed that, still no trigger fires. The 100% CPU was due to MT running on an empty XML file.

I see the event in the event log:

[Mon Feb 26 20:22:09 2007] vmware2k\andy Unknown TaskGroupTaken FastTrack 0x9d04 AdminFix 0x9d35 vmware2k\andy

iwlsat
ID: 54303 "TaskGroupTaken" C:/interwoven/iw-home/iw-perl/bin/iwperl
c:/interwoven/iw-home/custom/wft/bin/take_cgi.ipl

where else can I look ?

Andy

Care to post the take_cgi.ipl script?

This should look awful familiar as I copied it from a previous fish post
It runs fine from the command line, updates the log file. No action from the trigger.


#! \iw-home/iw-perl/bin/perl -w
use strict;
use warnings;
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome(); # Get the iw-home from environment

if (open(TXT,">>$iwhome/tmp/iwat.log")) {
        print TXT '=' x 70 . "\n";
        print TXT "ARG: $_\n" foreach(@ARGV);
        print TXT "ENV: $_ => $ENV{$_}\n" foreach(sort(keys(%ENV)));
        close(TXT);
}
else {
    die " '$iwhome/tmp/iwat.log' ($!)";
}

ISCBorisB

This should look awful familiar as I copied it from a previous fish post
It runs fine from the command line, updates the log file. No action from the trigger.


#! \iw-home/iw-perl/bin/perl -w
use strict;
use warnings;
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome(); # Get the iw-home from environment

if (open(TXT,">>$iwhome/tmp/iwat.log")) {
        print TXT '=' x 70 . "\n";
        print TXT "ARG: $_\n" foreach(@ARGV);
        print TXT "ENV: $_ => $ENV{$_}\n" foreach(sort(keys(%ENV)));
        close(TXT);
}
else {
    die " '$iwhome/tmp/iwat.log' ($!)";
}

It's been my experience that you can rely on event.log (formatted) messages only to a certain degree.
You may want to try the following in the the controlled (Development?) environment:

Adam Stoller

It's possible that this represents something that changed (broke?) in 6.7.1. The code I posted, which you are using, worked on 6.5SP2 - though right now I cannot remember if it was Windows or Solaris.

nipper

It's possible that this represents something that changed (broke?) in 6.7.1. The code I posted, which you are using, worked on 6.5SP2 - though right now I cannot remember if it was Windows or Solaris.

Yea I was wondering about that. I moved my trigger to the Dev server (running 6.5 SP2) and it works fine. BTW, I got the take group task, auto start CGI task to work easily with this trigger.

Still nothing fires on my VMWare image running 6.7.1

Anyone with 6.7.1 interested in trying ? All you need is a group task in a WF, run the trigger, save the PERL and see if the trigger writes to the log file.

Thanks

Andy

Adam Stoller

Yea I was wondering about that. I moved my trigger to the Dev server (running 6.5 SP2) and it works fine. BTW, I got the take group task, auto start CGI task to work easily with this trigger.

Still nothing fires on my VMWare image running 6.7.1

Anyone with 6.7.1 interested in trying ? All you need is a group task in a WF, run the trigger, save the PERL and see if the trigger writes to the log file.

Thanks

Andy

Have you opened a case with IWOV? This sounds like a potentially significant bug (the iwat trigger for grouptask ownership was a nice work-arond for not being able to have group_cgi_tasks and implicit ownership of cgitasks by owner of predecessor grouptask).

Bill Klish

I think you need to register the iwat trigger in the iwutild.cfg file. All of these type of things, including iwpt_compile.ipl run under this daemon now. I would try lowering your logging level done by this daemon from warn/error to debug and see if you get any more information, or proof that things are actually doing something.

The manual claims that you don't need to add your command in there, but I might go ahead and try adding it anyway.

If you mail me the stuff to try I will run it on 6.7.1 patch 2 for linux and let you know what happens.

kk_aa_rf

Any luck with this? We are also running into an issue with iwat CreateFSE.
It doesn't run on TS6.7.1 Solaris10.

patrickm

Same problem here, similar script. The utlity deamon shouldn't need to be configured as according to the documentation: "the programs executed by iwat triggers and workflow external tasks need not be specified in iwutild.cfg".

nipper

I never filed a support request since I was only playing on 6.7.1 so you may want to ask support. It worked fine on my 6.5 server.

Andy

beez

It works fine for me on 6.7.1 (Solaris and Windows). I suggest you start with a simple test case such as:

iwat "Thaw" " foo.pl" [where foo.pl just writes something to a file]

and run "iwfreeze --" to trigger it.

Fyi, I dont see any output in utild logs when the trigger fires.

And with CreateFSE events, you need to explicitly turn them on in iw.cfg.

--Mike