X Gui window creation problem 3546

Dances With Crows

I agree that it's getting old. I mentioned a planned upgrade and was told that since 3.0 will be supported for a while, to leave it alone. Go figure.

I don't think it has

I would agree! I wanted to avoid leaving out a detail that someone might possibly ask for.

We checked on this right away. Nothing scheduled right at 11:39. Those things which run soon before, or are running at the time, were checked and seem to no be part of the problem and I don't think they do anything that requests creation of a window, unless the request is indirect...ie...an error or some anomale that might result in the scheduling software popping an endless series of windows. However, since each window stays put when the other 3 are closed, we have at least some reason to believe this is not the case. The jobs still run as scheduled when the monitoring windows are closed. hmmmm

That's what we used to think. Most, or maybe all, of our jobs are just regular batch runs that report on and-or update one or more databases without interactive user input. Now that I think back- I believe this was probably happening when the system was initially set up and running in test mode, and when the queues were first loaded but all tasks were held. I can't imagine this perception is correct so I will look at this again.

Well- I believe we don't have any code which does this but I will look. Still- since any window stays put when the other 3 are closed, it's a strange situation.

Use the breadcrumbs to

I agree. Hard to track, though.

semaphore?? Now you're talking-

Thanks for the input! regards, Bill