Mach-II/Mach-II-Framework — Issue #13: Element DATA is undefined in DATASTORAGE
Author: mpwoodward
Created: 2012-03-01 00:42:13+00:00
State: open

(Moved from http://trac.mach-ii.com/machii/ticket/785)

Periodically getting this error from the MachII Dashboard. It's happening on line 168 of Logger.cfc in version 1.8. The code is below and throws an exception on ``

See also: http://groups.google.com/group/mach-ii-for-coldfusion/browse_thread/thread/2789854a4a21ae4a?pli=1

Code:

`	`
`	`

`	`

`	`
`	`
`	`
`	`

`	`

`	`
`	`
`	`

`	`
`	`

Changed 9 months ago by aj_ferrigno

I've been looking at this... maybe we should put another loop and a cftry/cfcatch around lines 165 - 169, and if it fails, keep this new looping variable to false so it will just keep doing 165-169 over again until it gets it right (setting the looping variable to true). It should only loop twice at worst, I hope. Maybe rethrow if it loops 5 times or something.

I can submit a patch to you if you want - do you know how I would test this change? It seems to happen in my environment for users who are actually not in the dashboard at all. Somehow this logging file is called by the core.

comment:2 Changed 9 months ago by peterjfarrell

Keywords logger added
Owner changed from peterfarrell to peterjfarrell
Status changed from new to assigned
Description modified (diff)
Milestone set to Mach-II 1.9.0 Milestone 3
comment:3 Changed 8 months ago by peterjfarrell

Cc aj_ferringo, matt_woodward, kurt_wiersma, peterjfarrell added
@Domminic, are you guys using ACF9? I can't get this to reproduce on ACF8 and I think this might be related to ticket #795 -- the only commonality seems to be StructKeyDelete? and ACF9.

comment:4 Changed 8 months ago by peterjfarrell

Milestone changed from Mach-II 1.9.0 Milestone 3 to Mach-II 1.9.5 Milestone 1
Switching to 1.9.5

comment:5 Changed 8 months ago by Dominic

Yes, we are running CF9

comment:6 Changed 8 months ago by peterjfarrell

I should also ask if you're using the ACF Server Monitor (like profiling, memory, etc.) and if so, what settings?

comment:7 Changed 8 months ago by Dominic

Yes, we have Profiling and Monistoring turned on, Memory Tracking turned off.

comment:8 Changed 5 months ago by aj_ferrigno

Just checking in on the status of this ticket. It is still happening for us continually on version 1.8. Are we sold on the idea that this problem is related to 795? I now realize this is failing at ArrayDeleteAt? and that ticket is failing for StructDeleteAt? - are they related?

I think they are: here is the same test case from Doug Smith on that ticket, but modified to do the same thing for Arrays.

``
``
``
``

`

Items in array: #ArrayLen(local.stc)#

`
`

Has "three"? #local.stc[3]#NO

`

``

`

#local.title#

`

``

``

` `

``

HOWEVER, I just ran this test case and Doug's from 795 on Railo (version 3.3.0.027 rc) and it also outputs the same exact behavior. This makes me question whether this is a bug, or at least this may be the wrong test case. Thoughts? Should I post this in that ticket as well?