> But if you really think it's one request that triggers them both, then by
> single stepping through things from the start (or some point before you know
> they're not both running), you should be able to immediately see when the
> 2nd request thread pops up. Hope that helps.
>
> /charlie
>
Thanks Charlie. It is hard to see where it was being triggered since
this is a model.glue app and event=eventName is handled by an XML
file, and I do not think FD will stop at a breakpoint in an XML file.
I would have to dig into the MG code, somewhere in the event handler
and set a break point there, or maybe even go back to index.cfm and
set the breakpoint at the beginning.
I have resolved it and it was very bazaar. The issue causing the 2
threads to kick off was the following:
onclick="location.href='index.cfm?
event=Report.SetupStep3&firstID=1381&secondID=156';"
This is part of a multi step process with back and forward buttons. If
I change this to a straight href link, it only kicks off one thread
and my problem goes away.
So I am going to re-work that but would be interesting to know why the
location.href had that effect. But even if I did set a break point
somewhere earlier, I don't think it would have caught this since it is
JS kicking it off. But, FD did immediately confirm to me I had 2
threads running which was a huge help.
Thanks,
Dan