• State Not Answered
  • Replies 6 replies
  • Subscribers 10 subscribers
  • Views 5203 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Hotfix C installation on 16.2 / serialization policy file

yusufa
Certified Associate Developer
Hello,
we faced the same problem as kaushikr735 on 19.7.2016.
Tempo was not available after the Hotfix installation.
We copied the file "/tempo/D68677DEE20974ADA7AA9FDE366ECD52.gwt.rpc" from our backup folder to our new appian instance and restarted JBOSS afterwards to fix the problem.
But why we had an issue in the first place? Is there something wrong with the hotfix or with our installation ? 4 Weeks ago we made an upgrade from the version 7.8 to 16.2 without any updated in between.

Thanks
Yusuf

OriginalPostID-229855


AppianErrorTempo.txt

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    Actually that's not the right solution and can put your system in an inconsistent state.

    The right solution is described here forum.appian.com/.../kb-1058.html
  • 0
    A Score Level 2
     in reply to Eduardo Fuentes

    Hi Eduardo, we're facing the same issue after applying Hotfix H to a perfectly working 17.1 environment. The solution you gave in your post is no longer accessible due to forum migration to the new community platform.
    Can you help me out with the issue?

     

    This is the error:

    [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ajp-/0.0.0.0:8009-1) tempoSvcServlet: ERROR: The serialization policy file '/tempo/4054428C5DBBCAA1F3B77E9C975766CB.gwt.rpc' was not found; did you forget to include it in this deployment?
    13:20:28,654 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ajp-/0.0.0.0:8009-1) tempoSvcServlet: WARNING: Failed to get the SerializationPolicy '4054428C5DBBCAA1F3B77E9C975766CB' for module 'http://*****/suite/tempo/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.

     

     

    After this the Tempo interface is no longer accessible.

    Sites are working fine.

Reply
  • 0
    A Score Level 2
     in reply to Eduardo Fuentes

    Hi Eduardo, we're facing the same issue after applying Hotfix H to a perfectly working 17.1 environment. The solution you gave in your post is no longer accessible due to forum migration to the new community platform.
    Can you help me out with the issue?

     

    This is the error:

    [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ajp-/0.0.0.0:8009-1) tempoSvcServlet: ERROR: The serialization policy file '/tempo/4054428C5DBBCAA1F3B77E9C975766CB.gwt.rpc' was not found; did you forget to include it in this deployment?
    13:20:28,654 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ajp-/0.0.0.0:8009-1) tempoSvcServlet: WARNING: Failed to get the SerializationPolicy '4054428C5DBBCAA1F3B77E9C975766CB' for module 'http://*****/suite/tempo/'; a legacy, 1.3.3 compatible, serialization policy will be used. You may experience SerializationExceptions as a result.

     

     

    After this the Tempo interface is no longer accessible.

    Sites are working fine.

Children
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.