We are using flex 3, blazeDS and Java Application (spring, hibernate, DB2). We are using WebSphere server. We tested our project on local and dev and its worked fine (on http channel). Now we are moving to QA where the development environment is slightly changed. We have 2 servers on QA. We are using IBM-TAM for security and clustering we are using WebSphere server.
I am new to blazeDS and do not know how it works on cluster environment. I am getting the following error when I try to navigate to flex screen. Please help me to solve this issue. Error: Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 404: url: 'https://www.myserver.com/costmodel/costmodel/ messagebroker/amfsecure' [ChannelFaultEvent faultCode="Channel.Connect.Failed" faultString="error" faultDetail="NetConnection.Call.Failed: HTTP: Status 404: url: 'https://www.myserver.com/costmodel/costmodel/ messagebroker/amfsecure'" channelId="my-secure-amf" type="channelFault" bubbles=false cancelable=false eventPhase=2] --------------------------------------------------------------- the service-config.xml file is: --------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <services-config> <services> <service-include file-path="remoting-config.xml" /> <service-include file-path="proxy-config.xml" /> <service-include file-path="messaging-config.xml" /> </services> <security> <login-command class="flex.messaging.security.WebSphereLoginCommand" server="WebSphere"/> </security> <channels> <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel"> <endpoint url="http://{server.name}:{server.port}/ costmodel /messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/> </channel-definition> <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel"> <endpoint url="https://{server.name}:{server.port}/ costmodel/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/> <properties> <add-no-cache-headers>false</add-no-cache-headers> </properties> </channel-definition> <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel"> <endpoint url="http://{server.name}:{server.port}/ costmodel/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/> <properties> <polling-enabled>true</polling-enabled> <polling-interval-seconds>4</polling-interval- seconds> </properties> </channel-definition> </channels> <logging> <target class="flex.messaging.log.ConsoleTarget" level="Error"> <properties> <prefix>[BlazeDS] </prefix> <includeDate>false</includeDate> <includeTime>false</includeTime> <includeLevel>false</includeLevel> <includeCategory>false</includeCategory> </properties> <filters> <pattern>Endpoint.*</pattern> <pattern>Service.*</pattern> <pattern>Configuration</pattern> </filters> </target> </logging> <system> <redeploy> <enabled>false</enabled> </redeploy> </system> </services-config> --------------------------------------------------------------- The remoting-config.xml file: --------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <service id="remoting-service" class="flex.messaging.services.RemotingService"> <adapters> <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter" default="true"/> </adapters> <default-channels> <channel ref="my-secure-amf"/> </default-channels> <destination id="destination1"> <properties> <source>com.searshc.Reporting</source> </properties> </destination> </service>

