« Return to Thread: DWR 3 Reverse AJAX: difference between localhost and remote box installation behavior

DWR 3 Reverse AJAX: difference between localhost and remote box installation behavior

by Alexander Bagerman :: Rate this Message:

Reply to Author | View in Thread

Hi,
While working on the application that is using DWR 3 for reverse ajax
I hit the following problem. My configuration is DWR, Spring, Java 6
and Tomcat 6. Locally I am running my application directly from under
Eclipse and reverse ajax works in almost real time - I can see changes
propagated from one browser to another in no time. The url I am
calling at this case is http://localhost:8080/

When I tried to deploy it to remote box and run it suddenly it started
to take a full minute to handover information from one browser to
another. I thought it might be due to Apache proxy that i have in
front of my tomcat but nothing changed when I called app server
directly on 8080 port. In this case I put http://xxx.xxx.xxx.xxx:8080/
url in my browser

Here is my spring context configuration:

        <dwr:controller id="dwrController" debug="true">
                <dwr:config-param name="activeReverseAjaxEnabled"
                        value="true" />
                <dwr:config-param name="maxWaitAfterWrite"
                        value="-1" />
                <dwr:config-param name="org.directwebremoting.extend.ScriptSessionManager"
                        value="com.somename.myScriptSessionManager" />
        </dwr:controller>


Any suggestions would be very appreciated as I tried all different
configuration options suggested on the site to no avail.

Thanks,
-Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: DWR 3 Reverse AJAX: difference between localhost and remote box installation behavior