• Issue in upgrading from OpenKM v6.3.2 to v6.3.3

  • Problems with installing OpenKM? No problemo, the solution is closer than you think.
Problems with installing OpenKM? No problemo, the solution is closer than you think.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
 #43974  by khalid2040
 
Hi,

I am trying to upgrade from OpenKM v6.3.2 to v6.3.3 (community version) following the guide at "https://docs.openkm.com/kcenter/view/ok ... o-633.html". But, I am getting the following error in catalina.log.
I appreciate any suggestion to resolve this issue... :-)
Code: Select all
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: You cannot use a spring-security-2.0.xsd or spring-security-3.0.xsd schema with Spring Security 3.1. Please update your schema declarations to the 3.1 schema.
Offending resource: URL [file:/opt/tomcat/OpenKM.xml]
And, here is the content of my OpenKM.xml
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns:security="http://www.springframework.org/schema/security"
             xmlns:task="http://www.springframework.org/schema/task"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans
                                 http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
                                 http://www.springframework.org/schema/security
                                 http://www.springframework.org/schema/security/spring-security-3.2.xsd
                                 http://www.springframework.org/schema/task
                                 http://www.springframework.org/schema/task/spring-task-3.1.xsd">
  
  <!-- Security configuration -->
  <security:authentication-manager alias="authenticationManager">
    <security:authentication-provider>
      <security:password-encoder hash="md5"/>
      <security:jdbc-user-service 
        data-source-ref="dataSource"
        users-by-username-query="select usr_id, usr_password, 1 from OKM_USER where usr_id=? and usr_active='T'"
        authorities-by-username-query="select ur_user, ur_role from OKM_USER_ROLE where ur_user=?"/>
    </security:authentication-provider>
  </security:authentication-manager>
</beans:beans>
 #43975  by khalid2040
 
Hi,

After deleting the two folder "$TOMCAT_HOME/webapps/OpenKM" and "$TOMCAT_HOME/work/Catalina/localhost", I see "hibernate.hbm2ddl=none" in the file OpenKM.cfg. So, I guess the upgrade is complete.
I can see the login page in the browser but after login "could not load profile" exception appears. Here is the extract from catalina.log. I have also attached the complete catalina.log.
Any insight?
Code: Select all
2017-06-04 01:41:16,529 [localhost-startStop-1] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- No Spring WebApplicationInitializer types detected on classpath
2017-06-04 01:41:16,785 [localhost-startStop-1] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- Initializing Spring root WebApplicationContext
2017-06-04 01:42:49,517 [http-apr-55443-exec-2] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- DashboardServlet: ERROR: The serialization policy file '/frontend/7706FBF6BF81FA3FAE5A043BB4A08EB4.gwt.rpc' was not found; did you forget to include it in this deployment?
2017-06-04 01:42:49,517 [http-apr-55443-exec-2] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- DashboardServlet: WARNING: Failed to get the SerializationPolicy '7706FBF6BF81FA3FAE5A043BB4A08EB4' for module 'https://192.168.1.2:55443/OpenKM/frontend/'; a legacy, 1.3.3 compatible, serialization policy will be used.  You may experience SerializationExceptions as a result.
2017-06-04 01:42:49,728 [http-apr-55443-exec-8] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- WorkspaceServlet: ERROR: The serialization policy file '/frontend/1B32D99D1E311A39A7921BEE96A870DA.gwt.rpc' was not found; did you forget to include it in this deployment?
2017-06-04 01:42:49,729 [http-apr-55443-exec-8] INFO  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- WorkspaceServlet: WARNING: Failed to get the SerializationPolicy '1B32D99D1E311A39A7921BEE96A870DA' for module 'https://192.168.1.2:55443/OpenKM/frontend/'; a legacy, 1.3.3 compatible, serialization policy will be used.  You may experience SerializationExceptions as a result.
2017-06-04 01:42:49,768 [http-apr-55443-exec-8] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/OpenKM]- Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type 'com.openkm.frontend.client.OKMException' 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 = com.openkm.frontend.client.OKMException: could not load an entity: [com.openkm.dao.bean.Profile#1]
Attachments
(3.82 KiB) Downloaded 175 times

About Us

OpenKM is part of the management software. A management software is a program that facilitates the accomplishment of administrative tasks. OpenKM is a document management system that allows you to manage business content and workflow in a more efficient way. Document managers guarantee data protection by establishing information security for business content.