Stuck on login screen

[taihung]

Our OpenKM is Version 6.2.6-DEV (build 8125) installed on Windows server 2003 with 8G RAM.
It works quite well, but stuck on login screen recently.
It stuck on "getting taxonomy root node" for minutes.
And mysqld.exe on server keeps CPU usage at 50%.

We use MySQL 5.6.
my.ini is attached.

Is there anything that I can do?

Thanks.

[jllort]

can be several things:
Go to administration OpenKM/admin and we need some information:
number of documents ( OKM_NODE_DOCUMENT ), number of folders (OKM_NODE_FOLDER), number of keywords (OKM_NODE_KEYWORD), number of mails (OKM_NODE_MAIL), number of categories (OKM_NODE_CATEGORY )

Have you recently imported a lot of documents ?
Do you see something in log ( /tomcat/logs/catalina.log )

With this data I can get you some idea.

[taihung]

Thanks for jllort's reply.
I've noticed there is a warning message in catalina.log

Line 13187: Caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (31653439 > 20971520). You can change this value on the server by setting the max_allowed_packet' variable.

I've changed MySQL max_allowed_packet's value from 20M to 40M. Then restart MySQL and OpenKM.
After changing this value, this warning didn't show up again.
But the problem still exists. I've to wait for 3 mins.

Here is the log when I log in after I restart MySQL & OpenKM.

Code: Select all

2014-05-17 21:40:39,500 [    main] INFO  org.apache.catalina.startup.Catalina - Server startup in 33690 ms
2014-05-17 21:41:01,500 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.config.GlobalSettings - Trying to find Dozer configuration file: dozer.properties
2014-05-17 21:41:01,531 [http-bio-0.0.0.0-8080-exec-6] WARN  org.dozer.config.GlobalSettings - Dozer configuration file not found: dozer.properties.  Using defaults for all Dozer global properties.
2014-05-17 21:41:01,531 [http-bio-0.0.0.0-8080-exec-5] INFO  com.openkm.module.common.CommonAuthModule - PrincipalAdapter: com.openkm.principal.DatabasePrincipalAdapter
2014-05-17 21:41:01,562 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.DozerInitializer - Initializing Dozer. Version: 5.3.2, Thread Name: http-bio-0.0.0.0-8080-exec-6
2014-05-17 21:41:01,625 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.jmx.JMXPlatformImpl - Dozer JMX MBean [org.dozer.jmx:type=DozerStatisticsController] auto registered with the Platform MBean Server
2014-05-17 21:41:01,656 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.jmx.JMXPlatformImpl - Dozer JMX MBean [org.dozer.jmx:type=DozerAdminController] auto registered with the Platform MBean Server
2014-05-17 21:41:01,703 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.DozerBeanMapper - Initializing a new instance of dozer bean mapper.
2014-05-17 21:41:01,734 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.loader.CustomMappingsLoader - Using the following xml files to load custom mappings for the bean mapper instance: [dozerBeanMapping.xml]
2014-05-17 21:41:01,765 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.loader.CustomMappingsLoader - Trying to find xml mapping file: dozerBeanMapping.xml
2014-05-17 21:41:01,781 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.loader.CustomMappingsLoader - Using URL [file:/D:/openkm6/tomcat/webapps/OpenKM/WEB-INF/classes/dozerBeanMapping.xml] to load custom xml mappings
2014-05-17 21:41:01,828 [http-bio-0.0.0.0-8080-exec-6] INFO  org.dozer.loader.CustomMappingsLoader - Successfully loaded custom xml mappings from URL: [file:/D:/openkm6/tomcat/webapps/OpenKM/WEB-INF/classes/dozerBeanMapping.xml]

number of OKM_NODE_DOCUMENT
4226

number of OKM_NODE_FOLDER
648

number of OKM_NODE_KEYWORD
25

number of OKM_NODE_MAIL
0

number of OKM_NODE_CATEGORY
0

Thanks you very much~

[taihung]

After updating OpenKM from Version 6.2.6-DEV (build 8125) to 6.2.6-DEV (build 8126), the login process didn't stuck again.
I hope this problem is really solved.
Thanks.

[jllort]

OK,

Some issues is quite difficult try to help on forum way. We can give you some ideas about what could happens. Stay tree minutes locked seems to be a soemthing in relation with database query. It's strange only upgrading to 6.2.6 will be solved because this should be a problem that will have all users in 6.2.5, and it's first time somebody report it.