jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: OutOfMemory while running tests
Date Mon, 06 Feb 2006 10:13:18 GMT
according to your logs shutdown seems to work fine.

did you try to simply increase the heap space for the jvm? maybe your 
settings are just to low for the test cases you are running...

regards
  marcel

Alexandru Popescu wrote:
> After each call to RegistryHelper.unregisterRepository(ctx, 
> repositoryName) I can see in the console:
> 
> [log]
> DEBUG: invalidated item cafebabe-cafe-babe-cafe-babecafebabe
> DEBUG: invalidated item cafebabe-cafe-babe-cafe-babecafebabe
> DEBUG: removing item cafebabe-cafe-babe-cafe-babecafebabe from cache
> DEBUG: removing item cafebabe-cafe-babe-cafe-babecafebabe from cache
>  INFO: Notification of EventListeners stopped.
>  INFO: Notification of EventListeners stopped.
> DEBUG: dispose IndexMerger
> DEBUG: dispose IndexMerger
>  INFO: IndexMerger terminated
>  INFO: IndexMerger terminated
> DEBUG: quit sent
> DEBUG: quit sent
> DEBUG: IndexMerger thread stopped
> DEBUG: IndexMerger thread stopped
> DEBUG: merge queue size: 0
> DEBUG: merge queue size: 0
>  INFO: Index closed: .\target\repository\workspaces\default/index
>  INFO: Index closed: .\target\repository\workspaces\default/index
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.SearchManager@610a39
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.SearchManager@610a39
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.lock.LockManagerImpl@112f348
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.lock.LockManagerImpl@112f348
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.RepositoryImpl@99d1df
> DEBUG: removing EventListener: 
> org.apache.jackrabbit.core.RepositoryImpl@99d1df
>  INFO: Database '.\target\repository\workspaces\default/db' shutdown.
>  INFO: Database '.\target\repository\workspaces\default/db' shutdown.
>  INFO: Database './target/repository/version/db' shutdown.
>  INFO: Database './target/repository/version/db' shutdown.
> [/log]
> 
> so I would say that the close operation is correctly triggered and even 
> better it works as expected. Still, the exception occurs.
> 
> I would say that it looks like a problem on Derby releasing the 
> resources, but I would like to be sure that this has nothing to do with 
> SimpleDbPersistenceManager.


Mime
View raw message