Yeah, just as I thought - my understanding is very poor - thanks for the info Geoff.
As for the jrun / iis error trapping questions, jrun is crashing when doing a verity update on CFMX enterprise - build is ok; which is weird cos the create calls the update code!! So along with the file upload error I have been thinking about error handling in gerneral - and you have confirmed my thoughts on this - your stuffed. Which is not to say this is a deficincey in CFMX - way out of it's control. Anyhoo, I have put some error trapping into the verity code of farCry to take out to site this morning, which I thought might not be any good anyway (cos it is a jrun issue). The jrun logs have not been helpfull so far. On another verity issue - the collection delete was also returning a (trappable) error. It was looping through the collections, deleting one, then the array index counter would go past the end of the array. I put a cfbreak after the delete in the contional match. I dont recall seeing any issue raised about this before. Let me know if you are interested in see the patch. On Wed, 25 Aug 2004 04:34:20 +1000, Geoff Bowers <[EMAIL PROTECTED]> wrote: > Andrew Mercer wrote: > > So how does this relate to error trapping in CFMX? Is there a > > difference between standard and enterprise? > > Not really. Error trapping in CFMX is just like any other application > error. If its a webserver error then it never got to CFMX to process so > no trapping. If its a JRUN internal error then something has gone wrong > beneath CFMX as it were -- you need to look to the JRUN logs to try and > get additional information. > > Can you trap JRUN and Web server errors from CFMX -- generally no. This > is because CF has not had a chance to process the request. But both the > application server and the web server have their own error trapping and > or diagnostic options. > > > In terms of robustness, security ... Is Tomcat/WebSphere/weblogics and > > better solution that jrun over IIS/Apache? > > Tomcat/WebSphere/weblogics must also run with IIS or Apache. I'd say > JRUN is pretty robust. You're going to get just as cryptic errors with > any of those application servers if not worse. > > > Just did a quick bit of reading and it looks like tomcat is a plugin > > for Apache and IIS. > > Tomcat is NOT a web server plug-in. It is a J2EE application server. > There will no doubt be a web connector for both IIS and Apache (ie. > something that lets Tomcat talk to the web server). > > > Hmmm, maybe IIS is not such an issue. > > > > My concerns (probably due to a misunderstanding) are the relationship > > / coupling of CFMX, java application server and the web server. From > > an (CF) application point of view, what can a developer do do handle > > jrun / webserver (internal error 500)? ie, what happens when the rug > > is pulled out from under your feet? > > Is this the file upload issue you were talking about earlier? Can you > replicate the issue in your development environment or does it only > happen in production? What are the steps to produce the error? > > If this is really becoming an issue you should raise a support ticket > with the Macromedia engineering team. Generally once you get through > the call centre and have your ticket, Macromedia CFMX support is very good. > > > > -- geoff > http://www.daemon.com.au/ > > --- > You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
