Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Deploy Flex Blazeds Application to Remote Server

Avatar

Level 1

Hi All

I built a blazeds application on my local tomcat server and it worked fine

then

1. I exported my java web project as a war file and put it on my host server.

2. I changed my services-config.xml file to reflect the changes in Servers

3. running my flex project I get

NetConnection.Call.Failed: HTTP: Failed: url: 'http://68.178.254.63:9080/samples/messagebroker/amf'

help will be appreciated

mordsm

9 Replies

Avatar

Level 1

Did you figure this out?  I'm having the exact same issue and can't figure out what the solution is.

Avatar

Level 3

Hi,

           Try to maintain your FlexProject name and Your ContextPath same.

Avatar

Level 1

thanks , It works for me now it turn out that the server port in my hosting

were different

Avatar

Level 1

I posted a support ticket to my hosting company and they apparently block port 8080.

So I have 2 options:

1.  Figure out what ports are available (and I'm going to guess not many other than 80) and use it.

2.  Upgrade my hosting package so that I can open up that port.

If 80 is the only port available, can I use that if I use an HTTPEndpoint?

Avatar

Level 1

Well it looks like I have any port in the 30000 - 35000 range available.

So now it looks like I just need to pick a port and configure blazeDS to listen on that port.

Is this just a change to the services-config.xml file or is there more to it?

Avatar

Level 1

Hi

My problem was connected to worong port use.

if it works for you in your localhost and every thing else fails check that

the server is working on the port you wrote in services-config and that this

port is open in firewall

mordsm

Avatar

Level 1

which port the tomcat working on?

Avatar

Level 1

I'm not using Tomcat.  I'm using a J2EE server called Resin which is what my hosting provider uses.

I can run my application on port 80 or 8080 locally, but port 8080 is blocked by the provider because its a shared server and they probably want to lock things down pretty tightly, which I totally understand.

I tried running blazeDS off port 80 but got a 503 error when I tried to connect.  Is there any reason why I shouldn't be able to run off port 80?  It works locally just fine, maybe its another restraint from my provider?

Avatar

Level 1

Turns out that the issue running on port 80 was a server configuration issue.  The hosting folks took care of the issue yesterday and everything seems to be running fine.

I have a note asking exactly WHAT was changed, but the application is working so I'm happy with that right now.