Figured this out..
in my production environment, the SSL terminates at the very first
entry-point .. so all requests internally are HTTP requests.
I changed my-secure-amf definition to use a SecureAMFChannel but point
to a non-secure AMFEndpoint. A re-compile and deploy solved the issue.
<channel-definition id="my-secure-amf"
class="mx.messaging.channels.SecureAMFChannel">
<endpoint
url="https://{server.name}:{server.port}/{context.root}/messagebroker/am\
fsecure" class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<add-no-cache-headers>false</add-no-cache-headers>
</properties>
</channel-definition>
--- In [email protected], "Satish Kumar.M" <[EMAIL PROTECTED]> wrote:
>
> Thanks for the reply Tom!..
>
> here goes' my remoting-config.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <service id="remoting-service"
> class="flex.messaging.services.RemotingService"
> messageTypes="flex.messaging.messages.RemotingMessage">
> <adapters>
> <adapter-definition id="java-object"
> class="flex.messaging.services.remoting.adapters.JavaAdapter"
> default="true"/>
> </adapters>
>
> <default-channels>
> <channel ref="my-secure-http"/>
> <channel ref="my-secure-amf"/>
> </default-channels>
>
> <destination id="Flex_RO">
> <channels>
> <channel ref="my-secure-http"/>
> <channel ref="my-secure-amf"/>
> </channels>
> <properties>
> <source>com.ui.flex.FlexFacade</source>
> </properties>
> </destination>
>
> </service>
>
> I've tried other combinations..
> a) Using only my-amf channel
> b) using only my-secure-amf
> c) using the a, b together my-secure-amf followed by my-amf
> d) using a,b, together with my-amf on top followed by my-secure-amd
>
> none of them worked out..
>
> any thoughts?
> Satish
>
>
> --- In [email protected], Tom Chiverton tom.chiverton@
> wrote:
> >
> > On Monday 11 Aug 2008, Satish Kumar.M wrote:
> > > my deployment environment looks like this..
> > > request---> [Load-Balancer]-->[Web-Server]--->[Java Application
> Server]
> > > the load-balancer is where the SSL terminates, as it's the
> front-stop
> > > for all the requests coming in from external world.
> >
> > Well, that's what we do (but with ColdFusion as the server) - have
you
> got
> > both the secure and non secure channel's listed in the destination ?
> Have you
> > removed the non-SSL channel-definition ? have you updated the
endpoint
> uri as
> > well as the endpoint and channel-definition class names ?
> >
> > --
> > Tom Chiverton
> >
> > ****************************************************
> >
> > This email is sent for and on behalf of Halliwells LLP.
> >
> > Halliwells LLP is a limited liability partnership registered in
> England and Wales under registered number OC307980 whose registered
> office address is at Halliwells LLP, 3 Hardman Square, Spinningfields,
> Manchester, M3 3EB. A list of members is available for inspection at
> the registered office. Any reference to a partner in relation to
> Halliwells LLP means a member of Halliwells LLP. Regulated by The
> Solicitors Regulation Authority.
> >
> > CONFIDENTIALITY
> >
> > This email is intended only for the use of the addressee named above
> and may be confidential or legally privileged. If you are not the
> addressee you must not read it and must not use any information
> contained in nor copy it nor inform any person other than Halliwells
LLP
> or the addressee of its existence or contents. If you have received
> this email in error please delete it and notify Halliwells LLP IT
> Department on 0870 365 2500.
> >
> > For more information about Halliwells LLP visit www.halliwells.com.
> >
>
