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

CGI losing browser thread

Jeremy

TS6.1SP2 Solaris
Hi,

This is a strange one. I'm running a CGI script as a custom menu item. Part of the script is to use OpenDeploy to depoy some files. Once this has completed deploying it is to show a Successful/Failure message in the browser.
This works fine when there are only a few files to deploy, but when there is a large number of files the message is never returned to the browser. I have checked and the OD has completed running but the return value is not sent back to the browser.
Its almost as though the link between the script and the browser has been lost as the delay was too long (long is about 6min in this case).

Has anyone come across anything like this before? Or has anyone got any idea's about how to get around it?

Here is the lines I use to call the OD cmd:

my $odCmd = "$IWHOME/OpenDeployNG/bin/iwodstart mi/transfer_config/transfer_config_local -k branch=$branch";
my $odResult = system "$odCmd 2>&1";
print "Result : $? $odResult";

The print statement is never reached when a larger deploy takes place.

Thanks for any tips or hints.

Jeremy

Find more posts tagged with

Comments

chuckles

Can you run this at the command line? It might be that the browser is timing out on the request. You can try something like:

open CMD, "$odCommand |";
while (read(CMD, my $bytes, 8)) {
print $bytes;
}
print "result: $?\n";

This would stream the result of your command-line directly to the browser as it comes and might keep it from getting bored.

ccprofessional

The default timeout for iw-webd is 300 seconds.

You can change this in <iw-home>/iw-webd/conf/httpd.conf file. This may help.

Adam Stoller

While this is a useful bit of code for some situations, I don't think it will help with OpenDeploy - because OD doesn't spit anything out until it's done - so there won't be anything to read until then either.

The iw-webd setting mentioned by ccprofessional seems more likely to help in this situation.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Jeremy

I changed the iw-webd timeout setting from 300 to 600 which should be 10 minutes. I then restarted Teamsite to make sure the change took place. Or would I need to restart the machine?

The deployment took 5:43min to complete yet it still did not move on in the code. In other words it didn't recognise it had completed.

Is there anyway to run a command and at the same time ping something back to the browser? If not then I'll probably somehow make this a static page with a "Refresh" button for the user to refresh to see the progress of the deployment.
Any idea's?

Thanks.

Adam Stoller

Since you're on Solaris - you could try forking the OD process and then in your wait loop, send a space ( ) periodically to the browser window to keep the connection alive. I haven't done this, so I don't know the fork() details off-hand, but I believe it would be possible.

See: perldoc -f fork -- for some details, also try looking at search.cpan.org and/or web-searching for "perl fork"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Jeremy

Great! Thanks for that point in the right direction Fish. I managed to figure out the fork process and ran the OD command from the child process. In the parent process every 30 seconds I ran the iwodserverstatus command to try get a match on the name of the deployment. If it was still running then it slept for another 30 seconds.
Once it wasn't running anymore then it returned with the OD result.
This worked with a deployment of over 10 minutes so I am happy it is working!
Thanks for the help!

Adam Stoller

If you get a chance - it would be nice if you posted the code...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Jeremy

Sure no problem.
I'm sure you'll be able to clean it up or even code it better! But right now it works for me which is what makes me happy!

At the point where the $childpid is defined is the fork in the code. It then runs both the parent and child code at the same time.
After the child code is completed it exits otherwise there would be a rogue iwperl process running in the background.

Every 20 seconds it checks again to see if the OD is still running. Once it has completed it leaves the while loop and continues into the rest of the code.


   #ALL PREVIOUS CODE HERE....

   #Now to Opendeploy the files to the workarea

    my $odCmd = "$IWHOME/OpenDeployNG/bin/iwodstart mi/transfer_config/transfer_config_local -k branch=$branch";

    defined(my $childpid = fork) or die "Cannot fork: $!";
    if ($childpid) {
        #This is the Parent process
        sleep(5);  # This makes sure the OD is running before it tries to run the iwodserverstatus cmd
        my $flagSet = 1;
        while ($flagSet) {
            print ". ";
            my $cmdResult = `$IWHOME/OpenDeployNG/bin/iwodserverstatus 2>&1`;
            if ($cmdResult !~ m|mi/transfer_config/transfer_config_local|i) {
                print "<br>Finished Running<br>";
                $flagSet = 0;
            }
            sleep(20);
        }
    } else {
        #this is the child process
        my $odResult = `$odCmd 2>&1`;
        exit(0);
    }

   #MORE CODE CONTINUES HERE

Edited by Jeremy on 09/05/05 06:34 AM (server time).