08-09-2012 05:50 AM
08-09-2012 06:50 AM
08-10-2012 02:49 AM
Hello,
you are using Derby as your database. This is not a supported database for the current Alfresco version, but I do not know, if this was the case for Alfresco 3.0.0 (which is quite old). It might by that you suffer from this: https://issues.apache.org/jira/browse/DERBY-3379
Generally, I'd advise to consider upgrading / updating your software stack. JBoss 2.x is quite old as well and who knows what other components might contain some potential, long fixed errors / bugs…
Regards
Axel
08-10-2012 03:29 AM
08-10-2012 04:47 AM
08-10-2012 05:17 AM
If you don't want to migrate or upgrade you will need to figure out what's gone wrong with your database. There's no information in your posting that helps diagnose your problem. All that can be said is that you have some sort of database problem.
08-10-2012 05:24 AM
08-10-2012 06:10 AM
Hello,
this indicates that either a) your Derby has a memory leak and runs full of memory, or b) due to size / transactional data set, the memory alloted to your Derby instance is not enough. An alternative scenario c) could be that the settings for GC are not optimal and may cause an unstable JVM in certain conditions - but this is difficult to say without extensive analysis.
You should check your Derby JVM settings and adjust the max heap size as a short term solution to a) / long term adaption to b). In order to determine wether a) is the case, you would need to profile / analyze the Derby JVM memory usage.
Regards
Axel
08-10-2012 06:39 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.