Open Source Document Management System | OpenKM

I'm using 5.1.11 version on Windows Server HyperV with 6GB RAM of which 3GB are assigned on JBoss. Every time I login I experience a very slow response on creating the application mainframe. I used an http monitoring tool and it seems as if JBoss takes a lot of time before starting to send the images and the other objects. Could it be something that slows down JBoss on responsing or is it just a caching issue? I don't think that it's an ldap authentication issue, because I have already tried your advice for inserting DNS addresses in hosts file. I attach the loading page where I get stacked for about 30 seconds and an image from the monitoring tool... Please do not tell me to upgrade in version 6, I will do it some time eventually

OpenKM is configured with LDAP? Anyway 5.1 branch support is deprecated and you should upgrade.

How much users do you list in openkm from ldap ? which browser are you using ? how much memory do you got on computer which you're using browser ?

Browser -> firefox(v.18)
PC -> dual core, 2GB RAM.
Network-> 100Mb LAN
When I press the login button I am immediately transfered in the loading page (so I have a quite fast authentication). In the loading page is where the delay is observed and as you can see in the picture, it's before even starting loading user parameters.I'ts like server having a delay before starting serving the objects to my browser.
OpenKM is configured with active directory but this is not the case because when I press the user's button from administration console it takes me just 5 seconds to get all the user list from the server(on the other hand, the delay in loading page is more than 30 secs).
user.item.cache is enabled.
I will upgrade in version 6 but it's not the easies thing, because the repository is not totally compatible as I can see from the migration guide.

Basically from 5.x to 6.x are able to migrate all information except imported mails. Do you have a lot of keywords ?

No I do not have any keywords. I was talking about the changes at the metadata of the files:
"If you got metadata date values then you should change from older 5.1.x format to new 6.x date format values, otherside you will get some error. The 5.1.x format to store data is "yyyy-MM-ddTHH:mm:ss.SSSZZZ", new 6.x format is "yyyyMMddHHmmss". In version 6.x values are stored in table OKM_NODE_PROPERTY, simply update older values format to new values format in this database"

I'm not sure if that problem has already solved in importing documents automtically, should be needed after migration. Anyway if the format into version 6.x is not correctly stored ( case you see with simple query table OKM_NODE_PROPERTIES ) -> Can be easilly tranformed with sql query. As you see really new storage value are several substring from 5.x value substring(0,2) + substring(3,5) etc... ( I think you can easilly understand the idea, simply make a select for each row and the result of it be the update query).

Ok, not a big deal, I will do it