"create method may not be called on a loaded entity" even though I reset

[sdwebguy]

I am running the latest version of this module and I see this exception quite a bit using this module in my API:

The create method may not be called on a loaded entity. Use the update() method to update an existing entity or reset the entity state

It comes from ActiveEntity.cfc line 128.

But I am calling it using this code:

getModel('LoggingService@MYAPI').reset().populate(prc.apiLogEntry).create();

which IS resetting first, as instructed. I have not found a pattern when this happens -- it doesn't happen all the time. Any ideas?

[jclausen]

@sdwebguy : Can you check what is being passed in prc.apiLogEntry when that error occurs? If there is an _id key being passed in there, it would throw that error. The reset() calls evict() which ensures that key is cleared.

If the log entry is coming from logstash or another mongo document which uses an _id it could be populating that.

Also, do you have any overloads to reset() in your LoggingService component?

[sdwebguy]

@jclausen When this happens, we get an exceptions email with a dump of most of the variables in play. We dont have an _id key in that document.

The prc.apiLogEntry contains the following structure:

{ 
	request={
		method=event.getHTTPMethod(), 
		timestamp=now(),
		route=event.getCurrentRoute(),
		routedurl=event.getCurrentRoutedURL(),
		bodycontent=ToString(GetHttpRequestData().content),
		headers=serialize(getHTTPRequestData().headers)
	},
	response={
		statuscode = prc.response.getStatusCode(),
		statustext = prc.response.getStatusText(),
		headers = serialize(prc.response.getHeaders()),
		bodycontent = prc.response.getDataPacket().toString(),
		responsetime = prc.response.getResponseTime()
	},
	sitecode=SITECODE_FROM_TOKEN,
	userid=USERID_FROM_TOKEN,
	tick=getTickCount()
}

We arent overriding any functions either. In fact, the entirety of our LoggingService is this:

component extends="cbmongodb.models.ActiveEntity" collection="APIV1Log" cache="true" {

	property name="userid" schema="true" validate="numeric";
	property name="sitecode" schema="true" validate="string";
	property name="tick" schema="true" validate="numeric";
	property name="request" schema="true" validate="struct";
	property name="request.method" schema="true" validate="string";
	property name="request.timestamp" schema="true" validate="date";
	property name="request.routedurl" schema="true" validate="string";
	property name="request.headers" schema="true" validate="string";
	property name="request.bodycontent" schema="true" validate="string";
	property name="request.route" schema="true" validate="string";
	property name="response" schema="true" validate="struct";
	property name="response.statuscode" schema="true" validate="numeric";
	property name="response.statustext" schema="true" validate="string";
	property name="response.headers" schema="true" validate="string";
	property name="response.bodycontent" schema="true" validate="string";
	property name="response.responsetime" schema="true" validate="numeric";

}

The only reason that tick property is there is to try to trick it to always see it as a unique document.

It doesnt happen all the time, which is the strange thing. I'm at a loss.