You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/07/30 20:50:40 UTC

[jira] [Resolved] (DERBY-6622) Derby server process hitting OutOfMemoryErrors and taking up 100% cpu

     [ https://issues.apache.org/jira/browse/DERBY-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-6622.
---------------------------------------

    Resolution: Cannot Reproduce

It has been a while since we have heard on this. Unless we get more details there is not much further we can do. I'm resolving as 'Cannot Reproduce'. 

> Derby server process hitting OutOfMemoryErrors and taking up 100% cpu 
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6622
>                 URL: https://issues.apache.org/jira/browse/DERBY-6622
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.8.2.2
>         Environment: Linux
>            Reporter: Vamsavardhana Reddy
>         Attachments: derby.log, derbyserver.all.out.zip
>
>
> We are using Derby Network Server in DataPower appliance.  Underlying OS is a Linux based.  Derby Server is accessed only by java processes running on the same appliance.  We are noticing that the Derby server process is running into OutOfMemoryErrors.  Post the OOM errors, connection requests to the server are failing and the CPU usage reaches 100%.  We are also noticing deadlocks reported in the logs.  Please help identify the cause and how the issue can be resolved.



--
This message was sent by Atlassian JIRA
(v6.2#6252)