Re: Hornet Queue (jboss) vs sever resource shortage [message #45611 is a reply to message #45610] |
Thu, 22 March 2012 14:12 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
Andrew Vagin
Messages: 28 Registered: November 2011
|
Junior Member |
|
|
Which kernel do you use?
Could you show content of /proc/bc/CTID/resources?
On 03/22/2012 04:08 PM, Dariush Pietrzak wrote:
> Hello,
> we have encountered a very strange behaviour of HornetQueue, running it
> inside vz results in:
>
> bash: fork: Cannot allocate memory
> or
> xmalloc: cannot allocate 4008 bytes (2084864 bytes allocated)
>
> ( this is on host node, that has ~20G of free, unused RAM, inside
> containers the problem is not visible - hornet is limited to ~4G of ram,
> container is limited to ~16G of ram and 0 vSwap, rest is unlimited )
>
> UBC inside container shows no visible resource usage problem, I'd go as
> far as to call it frugal - 1600 filedescriptors, very low shm usage,
> physpages nowhere near limit, and yet, when daemon runs, HN is unable to
> even accept login from console.
>
> how can I track down what is causing this?
>
> regards, Eyck
|
|
|