Well done - and here's the promised blogpost re my "null, null" error:
http://bloginblack.de/2011/12/coldfusion-null-null-errors-cfinterface-another-possible-reason/ :) Cheers Kai > Hi everyone, I eventually sorted this out. > > I isolated the problem to a QoQ combined with some occasionally bad data. > > One of the queries contained un-typed columns. One column contained mainly > zeros but occasionally an empty string. > > I wasn't joining on this column but I was selecting it. > > CF tries to be smart and set a type on the resulting column in the new query. > It then barfs when it encounters the empty string. > > In this case, garbage in garbage out would suit me fine, but no, it don't > work like that! > > Thanks everyone for your input, it's probably a CF bug, where an unexpected > error happens and CF doesn't produce a proper error for it. > > Cheers. > > On 07/12/2011, at 19:34 Kai Koenig <grmblz...@gmail.com> wrote: > >>> >>> @Kai ... What about one of those JVM inspection tools, do they show >>> exceptions as they occur? Maybe we can see it there? >> >> Hmm, I wonder if one could actually see it in the list of thread stack >> traces in a full heap dump. I guess the thread causing the error would have >> to be running at the time you'd take the heap dump. >> >> But it's an interesting idea. >> >> -- -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
