--
--
For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
Git & Wiki: https://github.com/Mach-II/Mach-II-Framework
---
You received this message because you are subscribed to the Google Groups "Mach-II for CFML" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldf...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldfusion+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldf...@googlegroups.com.
Do you have "save class files" turned on in the cf admin? What version of CF are you using?
On Mon, Sep 8, 2014 at 9:42 AM, Marc Rohrer <ma...@oneleaf.com> wrote:
We're not in PROD yet. We have this on DEV. We are able to reproduce the error on our sandbox server too.Marc
On Thursday, September 4, 2014 4:53:02 PM UTC-4, kwiersma wrote:
Are you able to reproduce the error on your local dev environment or do you only see it sometimes in production?--Kurt
On Thu, Sep 4, 2014 at 12:34 PM, Marc Rohrer <ma...@oneleaf.com> wrote:
We are getting occasional missing component errors even though the component does exist.The error is "Could not find the ColdFusion component or interface xxx.xxx.xxx." And the detail is "Ensure that the name is correct and that the component or interface exists."Some times the error will go away with a page refresh, sometimes it won't. We have boosted memory significantly for the JVM to 10GB, which has eliminated most, but still get some.The concern is that we will get these errors again as we continue to migrate a very large app to Mach II. Does anyone know why these errors might be occurring and how to eliminate them?Thanks,
Marc
--
--
For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
Git & Wiki: https://github.com/Mach-II/Mach-II-Framework
---
You received this message because you are subscribed to the Google Groups "Mach-II for CFML" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldfusion+unsubscri...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldf...@googlegroups.com.
Component cache is turned on. I did find a Mach II mapping to a different app in the CF admin. I deleted that. The other mappings are defined in the Application.cfc. After deleting the Mach II mapping, it seemed that the problem went away. But during testing, it showed back up. I've been looking at the error more and it seems to be happening when we call the init() from the gateway.cfc for the first time.
-- Peter J. Farrell OpenBD Steering Committee / Mach-II Lead Developer http://blog.maestropublishing.com Identi.ca / Twitter: @maestrofjp Please do not send me Microsoft Office/Apple iWork documents. Send OpenDocument instead! http://fsf.org/campaigns/opendocument/
--
--
For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
Git & Wiki: https://github.com/Mach-II/Mach-II-Framework
---
You received this message because you are subscribed to the Google Groups "Mach-II for CFML" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mach-ii-for-coldf...@googlegroups.com.
One: try putting your component calls in a simple test file in your web root. You'll either get no error or a more informative one. It sidesteps machii and just tests your cf.
The other is just how cryptic these can be. Mine was a cd error but it was really caused by a change in the way a dependent Java package was called from within the Java VM folder (Amazonws in this case) Switching to an older version of the vm got it working. Fwiw.
config
controllers
model
machII
views
Application.cfc
index.cfm
mach-ii.cfc