Full error is: coldfusion.xml.rpc.CFCInvocationException: [java.lang.ClassNotFoundException : xmr.artxorms_webservice.class.xyn.XYNReportVO][java.lang.LinkageError : duplicate class definition: xmr/artxorms_webservice/class/xyn/XYNReportVO] Note, some paths have been altered to preserve anonymity of my client (not that they care, its just good practice).

I’ve had absolutely no luck finding anything useful about this error on the interwebs as it relates to ColdFusion web services. Anyone got a clue? I’ll update if I figure it out.
CLUES:
- Clearing the template cache seems to clear this up temporarily but it comes back within a few hours of use.
- Server was recently upgraded to 8,0,1,195765 a few days before this problem was noticed. Service had no known problems previously.
- Java VM Version 1.5.0_07-b03
- JRun 4.? afaik
Update/Possible Solution?
I am pretty sure that this issue has something to do with case sensitivity on custom return types through the webservice response. I found this article which seems to indicate that there were some changes in the way that ColdFusion 8.1 generates WSDL files as far as case goes. http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=1&catid=7&threadid=1386433#5057074.
My latest guess is thus: Returning a complex data type through ColdFusion Webservice involves serializing a component into a SOAP format. Once an object is serialized it sticks around in a cache somewhere. Starting in CF8.1 if your reference gets changed before serializing the serializer will try again next go round only to find that the end result is already present. Rather than replacing the cached version as was probably intended, we get an error.
I’ve found a few places where my capitalization for component references were not consistent so I’m going through and making sure everything has the same case. The ones that are showing up as errors are the components that get serialized and returned through the web service response.
I’ve set up a brutal unit/stress tester for the web service. Assuming all goes well for the next 24-48 hours I may take this one to Adobe support.
IF you have anything helpful to add or you know that I’m way off, please share!!
