2 Replies Latest reply on Mar 26, 2010 9:44 PM by Johnking08

    Problems on installing BlazeDS on GoDaddy's shared Linux web hosting server

    Johnking08 Level 1

      GoDaddy's shared Linux hosting supports Tomcat (V 5.0.27 on JVM 1.5.0_22).

       

      I installed BlazeDS v3.2.0.3978 on the same Tomcat (5.0.27) with the same JVM (1.5.0_22) in my Laptop and it works fine. I created a

      simple Java testing class and put it in BlazeDS war file. I deployed the BlazeDS war file in the local Tomcat. I created a testing MXML file with the RemoteObject to access the Java class using localhost as the URL. Everything works fine.

       

      Now I deployed the same BlazeDS war file with a different WEB-INF/Flex/services-conf.xml (differnet host name) in the Tomcat in GoDaddy

      and using the same MXML file with the services-config.xml pointing to the URL hosted by GoDaddy. I got a long error message.

      It was too long and out of the screen and I can only see the middle part of it as following:

      ....

       

      initialDestinationId = (null)
                messageAgents = (Array)#9
                  [0] (mx.rpc::AsyncRequest)#10
                    authenticated = false
                    autoConnect = true
                    channelSet = (mx.messaging::ChannelSet)#6
                    clientId = (null)
                    connected = false
                    defaultHeaders = (null)
                    destination = "blazeds-tester"
                    id = "FA03C06F-D7F6-2CED-58F9-975C1FCE94A4"
                    reconnectAttempts = 0
                    reconnectInterval = 0
                    requestTimeout = -1
                    subtopic = ""
            connected = false
            connectTimeout = -1
            enableSmallMessages = true
            endpoint = "http://xyz.com/blazeds/messagebroker/amf"
            failoverURIs = (Array)#11
            id = "my-amf"
            mpiEnabled = false
            netConnection = (flash.net::NetConnection)#12
              client = (mx.messaging.channels::AMFChannel)#4
              connected = false
              objectEncoding = 3
              proxyType = "none"
              uri = "http://xyz.com/blazeds/messagebroker/amf"
            piggybackingEnabled = false
            polling = false
            pollingEnabled = true
            pollingInterval = 3000
            protocol = "http"
            reconnecting = false
            recordMessageSizes = false
            recordMessageTimes = false
            requestTimeout = -1
            uri = "http://xyz.com/blazeds/messagebro

      ...

       

      It seems that the BlazeDS was not running in Tomcat at GoDaddy because I got a similar error when I shutted down the local Tomcat running

      in my laptop and have the MXML file to call the localhost Tomcat's BlazeDS:

       

      ...

      (mx.messaging.channels::AMFChannel)#4
                initialDestinationId = (null)
                messageAgents = (Array)#9
                  [0] (mx.rpc::AsyncRequest)#10
                    authenticated = false
                    autoConnect = true
                    channelSet = (mx.messaging::ChannelSet)#6
                    clientId = (null)
                    connected = false
                    defaultHeaders = (null)
                    destination = "blazeds-tester"
                    id = "CE8C6CE6-5448-C6A2-2E04-9768F9E6C04C"
                    reconnectAttempts = 0
                    reconnectInterval = 0
                    requestTimeout = -1
                    subtopic = ""
            connected = false
            connectTimeout = -1
            enableSmallMessages = true
            endpoint = "http://localhost:8080/blazeds/messagebroker/amf"
            failoverURIs = (Array)#11
            id = "my-amf"
            mpiEnabled = false
            netConnection = (flash.net::NetConnection)#12
              client = (mx.messaging.channels::AMFChannel)#4
              connected = false
              objectEncoding = 3
              proxyType = "none"
              uri = "http://localhost:8080/blazeds/messagebroker/amf"
            piggybackingEnabled = false
            polling = false
            pollingEnabled = true
            pollingInterval = 3000
            protocol = "http"
            reconnecting = false

      ....

       

      Any suggestions? Has anyone successfully deployed and run BlazeDS in the Tomcat in GoDaddy's shared Linux web server?