Great news to those of us who have been experiencing the illegalStateExceptions and the related corrupted/truncated cfquery calls. Adobe just released a hotfix for ColdFusion MX 7.02.

Get the fix here: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=kb401830

***EDIT***  New Link (thanks for the new link Rich): http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402002&sliceId=1  

This was issued to resolve the strange behavior I blogged about here: Corrupted queries in ColdFusion MX 7

(Issue documentation from Adobe.com)

Issue

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

java.lang.IllegalStateException
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.