Issue with Tomcat & Webtop

Abraham001
edited October 5, 2016 in Documentum #1

Hi All,

I have deployed da and customized weptop 6.7 sp1  on tomcat-6.0.29 . I have 2 instances of tomcat running on two application servers with same webtop and da deployed on both .I am getting this below error in one of the servers .I am also running the application on same port on the 2 servers.The application hangs after some time and unable to connect :-

Sep 30, 2016 4:01:21 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/da] appears to have started a thread named [Thread-15] but has failed to stop it. This is very likely to create a memory leak.

Sep 30, 2016 4:01:21 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/da] appears to have started a thread named [Timer-7] but has failed to stop it. This is very likely to create a memory leak.

SEVERE: The web application [] created a ThreadLocal with key of type [null] (value [com.documentum.fc.client.impl.bof.classmgmt.DelayedDelegationClassLoader$2@505ce3a6]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

SEVERE: The web application [/da] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@747ab983]) and a value of type [com.documentum.web.env.app.AppServerEnvironment] (value [[Name = App Server Environment, Description = App Server Environment Implementation, Major Version = 0, Minor Version = 1, Author = Documentum, Portal Description = App Server, Portal Version = x.x, Environment Base Version = 1.0, Environment Service Version = 6.0, Supports Dispatch Contract = true, Supports Error Contract = true, Supports FormOperationListener Contract = false, Supports Theme Contract = true, Supports Locale Contract = true, Supports Tag Contract = false, Supports Session Contract = true, Supports SuperCredentials Contract = true, Supports Preference Contract = true, Supports Login Contract = false, Supports Render Contract = true, Supports Security Contract = true, Supports ContentTransfer Contract = true, Supports ActionPrecondition Contract = false, Supports MessageService Contract = false]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

20:36:02,644 ERROR [http-8003-15] com.documentum.web.common.Trace - ucf session wait timeout

java.lang.IllegalStateException: ucf session wait timeout

        at com.documentum.web.contentxfer.ucf.UcfSessionManager.newSession(UcfSessionManager.java:391)

        at com.documentum.web.contentxfer.ucf.UcfSessionManager.getSession(Uc

Am i getting this because the port for both instances of application is same . Any idea ,it runs for sometime before getting hanged.

Thanks

Tagged:

Comments

  • Francois Dauberlieu
    edited October 5, 2016 #2

    Look for threads about the UCF hanging, especially regarding IPV6 handling.... There are a lot of them in the forums.