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] 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
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
Glad I could help, Yes, they are registered in a central location using RMI to register each destination. Regards, João Fernandes
RE: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
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: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Niklas Richardson Sent: February 23, 2007 10:12 AM To: flexcoders@yahoogroups.com 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
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
No, we only had to change the destination name in the messaging-config.xmlfile in FDS. That fixed it. On 2/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On Behalf Of *Niklas Richardson *Sent:* February 23, 2007 10:12 AM *To:* flexcoders@yahoogroups.com *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] 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 -- Niklas Richardson Prismix Ltd UK based Flex and ColdFusion Specialists
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
And yes, the CF name does need to be different under Flex Integration in the CF Admin too. On 2/24/07, Niklas Richardson [EMAIL PROTECTED] wrote: No, we only had to change the destination name in the messaging-config.xmlfile in FDS. That fixed it. On 2/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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:* flexcoders@yahoogroups.com [mailto: [EMAIL PROTECTED] *On Behalf Of *Niklas Richardson *Sent:* February 23, 2007 10:12 AM *To:* flexcoders@yahoogroups.com *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] 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 -- Niklas Richardson Prismix Ltd UK based Flex and ColdFusion Specialists -- Niklas Richardson Prismix Ltd UK based Flex and ColdFusion Specialists
[flexcoders] Multiple Instances of CF / FDS and messaging broken?
Hi everyone, I've run into a problem which I think has to do with clashing RTMP ports. I'm totally stumped and need urgent assistance! :-S This is the setup: - JRun with two instances: cfusion and cfusion-testing - Both instances contain an instance of FDS - Updated the services-config.xml in both instances of FDS so that the RTMP ports are different - Apache with two virtual hosts: one passing CF requests to cfusion and the other passing CF requests to cfusion-testing - The Flex application has been compiled for both instances using the correct services-config.xml For arguments sake let's call the cfusion instance production and the cfusion-testing instance testing! The Flex application uses both Remote Object calls to ColdFusion using Mike Nimer's work around when using FDS, and it also uses Flex Messaging with CF Event Gateways. The Flex application on the testing website has no problems with Remote Object calls and also the Flex Messaging integration. It's great. However, the Flex application on the production website has problems with the Flex messaging (i.e. no pushes are coming through), but remote object calls are fine. Therefore, along with talking with Mike Nimer for a bit we've come to the conclusion that there must be some problem with the RTMP communication or something. Oh, I've also tested that the amfpolling URLs are all accessible too. Any help would be great!!! Thanks in advance. Cheers Niklas
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
Niklas, do the event gateways in cfusion and cfusion-testing have the same name? João Fernandes
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
Hi Joao, Yes they do. However, surely if they're on different instances that doesn't matter? Cheers Niklas On 2/22/07, João Fernandes [EMAIL PROTECTED] wrote: Niklas, do the event gateways in cfusion and cfusion-testing have the same name? João Fernandes -- Niklas Richardson Prismix Ltd UK based Flex and ColdFusion Specialists
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
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
Re: [flexcoders] Multiple Instances of CF / FDS and messaging broken?
Hi Joao, Okay, I'll give it a whirl tomorrow. One thought I had was that how does the ColdFusion FlexMessaging Event Gateway know which FDS instance to communicate with? There doesn't seem to be any configuration anywhere for that. Could that be the problem as well? Thanks for the help. Cheers Niklas On 2/22/07, João Fernandes [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
