We're working with Adobe on, I think, this same issue.
Are you just changing the service name in Flex Integration in CF Admin? Jay Proulx [EMAIL PROTECTED] ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Niklas Richardson Sent: February 23, 2007 10:12 AM To: [email protected] Subject: Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken? Hi Joao, Thanks for the pointer. With another pointer from Tom, and testing your suggestion, it appears that it's just the destination that you need to change. My guess is that, eventhough you have multiple FDS's running, the destinations must be registered in some server wide registry. Therefore, if you have the same destination name in multiple FDS's, then the last FDS to start overwrites the registry entry for that destination. By renaming the destination name for the "production" instance and then updating the code for the production instance so CF and Flex pointed to the new "production" destination has now fixed everything. It actually doesn't seem to matter than in the CF instances that all the event gateway names are the same across instances. Thanks again for the pointers. Cheers Niklas On 2/22/07, João Fernandes < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: It's something that I already spoke with Tom J. Can you try to create different names for the EG instance and if it doesn't work, try to use different destinationNames? João Fernandes -- Niklas Richardson Prismix Ltd UK based Flex and ColdFusion Specialists
