Sunday, January 24, 2016

OTM 6.3.4 Login Issue. Weblogic Is taking long to start


Error while starting the weblogic server for OTM 6.3.4 version  in the logs:

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

Thread-182 "[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {
    -- Blocked trying to get lock: glog.util.datasource.AppServerConnectionPool@1e2be7c0[fat lock]
    glog.util.datasource.AppServerConnectionPool.getInstance(AppServerConnectionPool.java:68)
    glog.util.datasource.AppServerConnectionPool.verify(AppServerConnectionPool.java:59)
    glog.util.datasource.DataSource.verify(DataSource.java:173)
    glog.util.jdbc.noserver.T2SharedConnection.checkDataSource(T2SharedConnection.java:346)
    glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:466)
    glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:440)
    glog.util.jdbc.noserver.T2SharedConnection.open(T2SharedConnection.java:70)
    glog.server.problem.ProblemSessionBean.getAllProbCount(ProblemSessionBean.java:407)
    glog.server.problem.ProblemSessionServerSideEJBWrapper.getAllProbCount(ProblemSessionServerSideEJBWrapper.java:273)
    glog.server.problem.ProblemSessionHome_h2m0bh_EOImpl.__WL_invoke(Unknown Source)
    weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
    glog.server.problem.ProblemSessionHome_h2m0bh_EOImpl.getAllProbCount(Unknown Source)
    glog.server.problem.ProblemSessionHome_h2m0bh_EOImpl_WLSkel.invoke(Unknown Source)
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
    weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
    weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Solution:

Please check the hostname details in /etc/hosts file.

Also check the hostname is same in DNS configuration also.

In my case the hostname was servername.domain.com but in DNS it was servername only.

I configured the DNS with fully qualified domain name and rebooted the application and tomcat services and I can login to OTM.  

No comments:

Post a Comment