Coldbox Error "Neither the method _actionExists was found in component"

Communities ColdBox HMVC
#1

I’m getting a seemingly random error message on a few of my Coldbox pages that I’m having a hard time figuring out. Most of the time the page loads fine, but every couple days or so this error will appear out of nowhere. A fwreinit will temporarily fix the issue.

Error Info:
**Message Content** :
Neither the method _actionExists was found in component C:\inetpub\wwwroot\taag\handlers\textMessagesNew.cfc nor was there any default method with this name present in any of the implementing interface.

URL: /index.cfm/textMessagesNew/report
**Page user was on**: /index.cfm
**Stack Trace**: C:\inetpub\wwwroot\taag\coldbox\system\web\services\HandlerService.cfc, Line 152
C:\inetpub\wwwroot\taag\coldbox\system\web\Controller.cfc, Line 745
C:\inetpub\wwwroot\taag\coldbox\system\web\Controller.cfc, Line 646
C:\inetpub\wwwroot\taag\coldbox\system\Bootstrap.cfc, Line 272
C:\inetpub\wwwroot\taag\Application.cfc, Line 204

**Additional Details** :
Ensure that the method is defined, and that it is spelled correctly

A few things I have tried so far with no luck:
-renaming the handler
-adding an init function to the handler (though it is not used in other handlers)
-explicitly extending the cb event handler extends="coldbox.system.eventhandler"

I have CB 6.5.2 setup to run on a legacy CF application. Its loaded in the onApplicationStart and CB requests are processed in onRequestStart

I can provide code snippets if anyone thinks it will be helpful but I basically created the handler through Commandbox scaffolding, so nothing special there.

Any help would be much appreciated
Thanks

#2

Can you post what version of CFML you are using?

#3

CF2018,0,13,329786, currently
Hope to upgrade to CF2023 soon

#4

How much load is on the server? I do have seen issues on acf where method pointers disappear for some reason.

#5

Unfortunately we don’t have any Performance Monitoring Tools like FusionReactor to provide you with any detailed information. I hope to get that in place soon, perhaps this will provide some additional motivation on that front. The app is a fairly large legacy CF application without much structure, which we are just beginning to migrate to Coldbox so I’m sure we have some long running reports/pages that put a fair amount of load on the server. Most of the time though it doesn’t seem to effect the servers performance.

#6

@lmajano
How would you go about addressing this issue? I am kind of at a loss.
Take a closer look at execution times of all actions of my problem handler? I’m sure setting up Fusion Reactor would be a beneficial for our app but do you think it could be useful in addressing this particular issue? Also, do you think this error is specific to ACF and not Lucee?

Thanks, any incite or direction would be much appreciated.

#7

Hi @Reggie_Park .

This is really an unusual problem. I have only seen it under high load using ACF engines. I am not sure if you have the latest engine fully patched. I also see you are in CB 6.5.2 Is there a way to upgrade to the latest of 6.8.1 and see if the errors continue to happen?

Having FusionReactor will definitely help to get further insight. @bdw429s have you seen this before?

#8

Thanks @lmajano, I’ll start with upgrading CB like you suggested and see if that does the trick. I have 6.8.1 up on our test servers now. I have also recently applied a few patches to CF and am on 2018,0,15,330106 now. Oddly enough it looks like they just released Update 16 today which I will apply soon as well. Thanks!

#9

Unfortunately, upgrading to CB 6.8.1 didn’t seem to address this issue. Still working on a solution. Seems to be occurring every couple days.