Error Messagesend Flex
Contents |
ElementsAdobe Dreamweaver Adobe MuseAdobe Animate CCAdobe Premiere ProAdobe After EffectsAdobe IllustratorAdobe InDesignView all communitiesExplore Menu beginsMeet the expertsLearn our productsConnect netconnection call failed http failed with your peersError: You don't have JavaScript enabled.
Flex Netconnection.call.failed: Http: Failed
This tool uses JavaScript and much of it will not work correctly
Netconnection.call.failed Http Status 500
without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Configuration and Getting Started All CommunitiesAdobe Open SourceBlazeDSConfiguration and Getting Started 8 Replies Latest reply on Feb 11, 2015 4:46 AM by priyankap250191 faultString="Send failed" faultCode="Client.Error.MessageSend" faultDetail="Channel.Connect.Failed ee88 Mar 8, 2010 1:55 AM I've installed the turnkey installation of blazeds.I've started the sampledb, started the tomcat server, chosen the correct configs in my flex client application.I made a simple javaclass "MyTestClass" with a getString method and put it in [turnkeyinstallationfolder]/tomcat/webapps/samples/WEB-INF/classes/flex/samplesI configured a destination in the remoting-config.xml of the samples with source flex.samples.MyTestClass.When I run my flex client application I always get this error message: (below is the code of my java class, flex air client app and the remoting-config.xml)error message[RPC Fault faultString="Send failed" faultCode="Client.Error.MessageSend" faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'http://lazeTestRemoting.swf/samples/messagebroker/amf'"] at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\gumbo_beta2\frameworks\p rojects\rpc\src\mx\rpc\AbstractInvoker.as:345] at mx.rpc::Responder/fault()[E:\dev\gumbo_beta2\frameworks\projects\rpc\src\mx\rpc\Responder .as:68] at mx.rpc::AsyncRequest/fault()[E:\dev\gumbo_beta2\frameworks\projects\rpc\src\mx\rpc\AsyncR equest.as:113] at mx.messaging::ChannelSet/faultPendingSends()[E:\dev\gumbo_beta2\frameworks\projects\rpc\s rc\mx\messaging\ChannelSet.as:1614] at mx.messaging::ChannelSet/channelFaultHandler()[E:\dev\gumbo_beta2\frameworks\projects\rpc \src\mx\messaging\ChannelSet.as:1206] at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.messaging::Channel/connectFailed()[E:\dev\gumbo_beta2\frameworks\projects\rpc\src\mx\m essaging\Channel.as:1128] at mx.messaging.channels::PollingChannel/connectFailed()[E:\dev\gumbo_beta2\frameworks\proje cts\rpc\src\mx\messaging\channels\PollingChannel.as:406] at mx.messaging.cha
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Client.Error.MessageSend problem with Flex/BlazeDS on https://forums.adobe.com/thread/591758 JBoss up vote 4 down vote favorite 1 I'm developing a Flex 3.4 app that interops with a Java EE backend running on a JBoss-4.2.2 server, through the most recent release of BlazeDS. When I ran the Flex app from Flash Builder 4 beta 2 on Tomcat, everything was fine, the Flex app was able to make the remote call needed. But my production environment is http://stackoverflow.com/questions/1715296/client-error-messagesend-problem-with-flex-blazeds-on-jboss on JBoss, and when I moved the app to JBoss (with services-config.xml updated to fit JBoss), the Flex app keeps complaining Client.Error.MessageSend upon remote calls. At first, when I manually deployed the app to JBoss, the faultDetail was "Channel.Security.Error error Error #2048 ... "; later I tried to run the app from Flash Builder, and then faultDetail became "Channel.Connect.Failed error NetConnection.Call.BadVersion". In services-config.xml, under
Forum.net version 1.9.1.8 (NET v4.0) - 3/29/2008Copyright © 2003-2008 Yet Another Forum.net. All rights reserved.This page was generated in 0.035 seconds.
ColdFusion I've been doing some with for the Flextras promotions around 360|Flex. As part of the promotions I am creating a customized version of my Game; strictly for Flextras. It is going to allow people to login and will keep score on our server instead of internally to the app. Since this is a Flash app; I'm using Flash Remoting to connect to our ColdFusion server. Everything worked fine on my local machine. Everything worked fine on my development server (AKA Staging). However, my production machine was giving errors that looked like this: faultCode: "Client.Error.MessageSend" faultDetail: "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: faultString: "Send failed" I've tried a lot of different things including not using http instead of https. I knew that Flash Remoting was working on the production server because I had other Flex apps working without problems. So, what was the problem?I've been working on this on and off for about five days; so tried a lot of different things. In the end I discovered two things: Make sure your Flash Remoting URL has a '/' at the end of it. 'https://www.flextras.com/flex2gateway' was not working. It appeared to add a JSessionID on it; which was causing the server to throw a 404 error; causing the whole call to fail. However, if I changed this to 'https://www.flextras.com/flex2gateway/' that problem went away. Turn off the Flash Builder Network Monitor. The Flash Builder Network monitor was intercepting the call and causing it to fail. The calls appeared to work fine from a web browser with the Flash Builder Network Monitor enabled, but not from the mobile app. I think--but am not completely sure--part of my issues related to using HTTPS on the server instead of HTTP. That could be the reason I had issues on the production server, but not my local or staging box. Comments (9) | Send | del.icio.us | Digg It! | Linking Blogs | 14127 Views Comments (Comment Moderation is enabled. Your comment will not appear until approved.) [Add Comment] [Subscribe to Comments] The reason why the URL wasn't working is because of this :If you have a Java based server, with session tracking, it will automatically add the jsessionID to the end of your url. This is not the default behavior of ColdFusion's JRUN, however it is the default for JETTY, Tomcat and Websphere. When you make a Remot