[Users] Hornet Queue (jboss) vs sever resource shortage

[Stoyan Stoyanov]

If I understand you don't have ANy failcnts in /proc/ ubc ? is that  
right?
Im using jboss (can say with 'middle load') inside vms and the  
problems (cannot allocate memory etc.) was beautifully printed in  
failcnt on /proc/user_bea...


On Mar 22, 2012, at 2: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
> -- 
> Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
> Total Existance Failure
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://openvz.org/mailman/listinfo/users

Stoyan Stoyanov
Core System Administrator

-------------- next part --------------
A non-text attachment was scrubbed...
Name: maxtelecom-logo.gif
Type: image/gif
Size: 2611 bytes
Desc: not available
Url : http://openvz.org/pipermail/users/attachments/20120322/406ba546/maxtelecom-logo.gif
-------------- next part --------------


CONFIDENTIAL
The information contained in this email and any attachment is  
confidential. It is intended only for the named addressee(s). If you  
are not the named addressee(s) please notify the sender immediately  
and do not disclose, copy or distribute the contents to any other  
person other than the intended addressee(s).