Apache Proxy 500 error or RPC serialization

[Kulnor]

I'm trying to proxy a GWT app running on my local Tomcat server through Apache use AJP but am getting 500 errors during RPC calls.

I simply have a standard entry in my httpd.conf file:

<Location /user/>

    ProxyPass ajp://localhost:9009/openmetadata-www-user-gwt/

</Location>

When I run the app directly on http://localhost:9090/openmetadata-www-user-gwt/ I have no problem, but when I go through the proxy, I can see the RPC call go through but then getting serialization errors while returning objects:

SEVERE: Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type 'org.openmetadata.www.user.client.UserServiceException' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer.For security purposes, this type will not be serialized.: instance = org.openmetadata.www.user.client.UserServiceException: User not found

Tried with http proxy (and on standard ports) but same issue. Seem like an RPC serialization policy problem but not sure what to do. Any suggestion would be appreciated.

best

*K

[Kulnor]

The source of the problem seem to come from the fact that the proxy site URL is different from the GWT app URL. This is discussed and nicely documented in https://groups.google.com/forum/?fromgroups#!searchin/google-web-toolkit/proxypass$20serialization/google-web-toolkit/3wE9yWLMJo4/Mebd0XgW1EIJ (thanks to the authors for this!)

The following proxy setting works properly as the URL are the same:

<Location /openmetadata-www-user-gwt/>

    ProxyPass ajp://localhost:9009/openmetadata-www-user-gwt/

</Location>

In my case, I can rename the underlying GWT app on tomcat so that should solved the issue. The post above provide excellent alternate solutions.

best

*K