Wednesday, September 1, 2010

GWT web app problem with Tomcat and Mod_Proxy

Hi,
I have a GWT web app that has 2 servlets in the same context.
Servlet_1 is the GWT RPC servlet. The other (Servlet_2) is a PDF
reporting Servlet.

When I save some report parameters in the httpSession using a RPC call
to Servlet_1, the AsyncCallback will open another browser window,
passing the url to the Reporting Servlet (Servlet2).

Servlet2 reads the report parameters, and creates the report.
This all works fine with just Tomcat alone.

However, I need to configure Apache httpd with mod_proxy or
mod_proxy_ajp to Proxy outside Internet request to this internal web
application.

When I configure the proxy, the parameters saved in the session are
missing, in the reporting servlet. In fact it looks like a new
session is created for servlet_2.

** Not sure if this is relevant to the problem, but I am getting a
tomcat error in my logs.

ERROR TP-Processor3 org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/WebReports] - WebReportService: WARNING: Failed to get
the SerializationPolicy 'ABEC9DB6309E99123321BAD1B79EE09A' for module
'http://192.168.1.37:8081/acme/webRpts/'; a legacy, 1.3.3 compatible,
serialization policy will be used. You may experience
SerializationExceptions as a result.

Does the serialization policy have an effect on cookie storage, or
sessions in Tomcat?
Can anyone with experience with mod_proxy and tomcat, help me out?

Thanks,
Mike.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment