Sachin, you have described EXACTLY the same scenario we are experiencing! flex 3,blazeds,java,spring,hibernate,db2,tam,webseal,webshpere,ssl,404.
did you ever solve this problem? we have been trying to solve it for weeks and tried the no-cache-headers and put in a crossdomain.xml but can't get it working. thanks, jake Sachin Patil-2 wrote: > > > F5 > > On Oct 13, 4:17 pm, Sachin Patil <[email protected]> wrote: >> Need Urgent help on BlazeDS on Cluster server >> >> 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://websealqa.mykmart.com/costmodel/costmodel/ >> messagebroker/amfsecure' >> >> [ChannelFaultEvent faultCode="Channel.Connect.Failed" >> faultString="error" faultDetail="NetConnection.Call.Failed: HTTP: >> Status 404: url: 'https://websealqa.mykmart.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/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/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/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> > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "Flex India Community" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex_india?hl=en > -~----------~----~----~----~------~----~------~--~--- > > > -- View this message in context: http://old.nabble.com/-flex_india%3A15032--Need-Urgent-help-on-BlazeDS-on-Cluster-server-tp19963725p30614904.html Sent from the Flex India mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Flex India Community" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/flex_india?hl=en.
