This usually happens if Aware IM was not stopped properly previously. JBoss may write its state info somewhere, so when you start up it tries to restore session info. This takes up a lot of memory and time and may fail. One work around is to increase memory allocated to JBoss on start up, but the better workaround is to delete the directories where it persists its state. The problem is that we are not too sure which directories these are, as they vary.
So usually we recommend overwriting the entire JBoss directory with the directory from the evaluation version or from a backup. Just backup jour JBoss directory once and then use it every time this problem happens.
