Red Hat Bugzilla – Bug 752120
JON 3 branch: Failed to load meta data for resource tree
Last modified: 2014-09-29 10:38:39 EDT
Created attachment 532317 [details]
client-side text of error
Description of problem: JON 3 branch: Failed to load meta data for resource tree
Version-Release number of selected component (if applicable):
JON 3.0 branch. 11/8/2011 build.
Steps to Reproduce:
1. i was navigating to the platform resource to test drift when it occurred
2. see screenshot
resource tree failed to load
resource tree loads
attachments: screenshots, server-side log, client-side stacktraces
Created attachment 532318 [details]
client side image of where error occurred
Created attachment 532319 [details]
this doesn't happen all the time. i did see this. and have lots of evidence ...client-side and server-side call stacks, screenshots. someone in dev should look at this more closely as there were recent changes that may have manifested this.
Mike, the root case of this issue appears to be the following error in your Server log:
2011-11-08 10:40:13,042 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/coregui]] org.rhq.enterprise.gui.coregui.CoreGUI ResourceTypeGWTService: ERROR: The serialization policy file '/org.rhq.enterprise.gui.coregui.CoreGUI/8FCB27A596CBB66256CC18F554A1C6F4.gwt.rpc' was not found; did you forget to include it in this deployment?
2011-11-08 10:40:13,043 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/coregui]] org.rhq.enterprise.gui.coregui.CoreGUI ResourceTypeGWTService: WARNING: Failed to get the SerializationPolicy '8FCB27A596CBB66256CC18F554A1C6F4' for module 'http://10.0.1.200:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.
I have never seen this error myself, so I'm thinking it's something in your environment. This post suggest that the error can occur when the GWT app is behind a reverse proxy:
Is that true for you by any chance?
The URL it fails to load is http://10.0.1.200:7080/coregui/org.rhq.enterprise.gui.coregui.CoreGUI/, which is an internal (dynamic?) address. Is it possible your VPN or Internet went down when the error occurred, or that your internal IP address had changed to something other than 10.0.1.200? I typically access my Server using 127.0.0.1:7080, rather than an external IP address, which may be why I've never encountered this. Tomorrow I'll try using an external address throughout the day to see if I encounter the error.
This seems environmental. I recommend closing.
Setting back to NEW since the assignment is invalid. Also, I think it can be closed.