I have been getting several reports about IllegalStateExceptions from several people now and wanted to have this documented to help other ColdBox or ColdFusion developers out there.

Have you been getting any IllegalStateExceptions in ModuleTag on your ColdBox Applications?? Are you using ColdFusion 7? Well, Adobe has a hot fix for this bug and it has been an old issue and of course, resolved in ColdFusion 8.

Adobe has resolved an issue with IllegalStateExceptions thrown intermittently by ModuleTag. The stacktrace generated is similar to the following:


at coldfusion.tagext.lang.ModuleTag.doAfterBody(ModuleTag.java:439)

at cfindex2ecfm842540228.runPage(C:\InetPub\wwwroot\IllegalStateException\index.cfm:18)

at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)

at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:349)

at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)

at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:219)

at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:51)

The scenario where this problem occurs typically includes the following items:

1. Use of an application framework.

2. Use of Application.cfc and OnRequestEnd or OnSessionEnd method.

3. Calling methods on ColdFusion Components stored in shared scopes, often the application scope.

4. The use of custom tags.

Secondary issues caused by the IllegalStateException are often resolved by application of the patch. These issues have included query truncation and invalid parameter binding errors with cfquery and cfqueryparam.