* So you're saying there is no "request" scope itself? That might indicate a cfthread is being generated * Are you using cfthread anywhere? * Are you calling your service layer from your view? * Are you using both contentArg or contentKey at the same time? * Are you dynamically calling displayView in the EventContext?
Can you share what one of your event-handlers looks like and then relevant code in the listener / filters? davee said the following on 08/12/2009 10:52 AM: > > On Aug 11, 2:51 pm, "Peter J. Farrell" <[email protected]> wrote: > >> I've never seen or even heard of any behavior like this before. >> >> * What version of Mach-II are you using? >> > 1.6.0 > > > >> * Are you using AJAX to do the form posts? >> > I do use ajax for some of the posts, but most are plain vanilla html > posts. I have been seeing this for a while on other applications that > I didn't write but never took the time to track them down. > Are you using Railo by chance? Can you describe your server environment / setup? > > > >> I bet if you use an HTTP header sniffer like Live Headers plugin for >> Firefox you'll see two requests being made by the browser. Another >> problem can be if you are using rewrite support in your webserver and >> it's rewriting stuff twice. >> > This is happening with the CF development server. I have no access to > production logs so I can't see if it is happening there, but since I > can see it on my localhost, I'm not assuming it can or cannot be seen > on other servers. In any case, it seems incredibly dangerous to allow > a browser to make two posts to the same url and have the second post > omit the request object. I'm not convinced that it is a browser error > since the second event is fired between the time the gateway function > finishes and the view pages are displayed. Mach-II can only process one event at a time. It's impossible for it to process two events at once. > This is demonstrable by > moving a cfabort around the app. If it's in the gateway or listener > after everything is done, it only executes it once, but if the abort > is in a view page, it seems to spawn a second thread with no request > scope. > Can you share your view and how you are doing your layouts (via event-handlers or subroutines). >> I seriously doubt that it's any particular with the framework going on >> as there would be *a lot* of broken applications in the wild. >> > > Notice that I explicitly said I knew it was something I was doing, > but don't know enough about the event handling process to properly > debug it since nothing I can see in the app is causing it. I do know > that is is a mach-ii issue, but that doesn't mean that it's not caused > by the application. This is why I'm trying to get to the bottom of it, > so we know what is is to avoid in the future. I could spend the next > couple of weeks stumbling around, but I'd rather not go through that > painful process if it's avoidable. No need to get defensive, just trying to help. I think if you can share some code -- that would be most helpful because otherwise it's just shots in the dark. Best, .Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---
