[Glass] VM temporary object memory is full (again)
Dale Henrichs via Glass
glass at lists.gemtalksystems.com
Sat Sep 26 13:59:34 PDT 2015
On 9/26/15 1:39 PM, Mariano Martinez Peck wrote:
>
>
> On Sat, Sep 26, 2015 at 5:11 PM, Dale Henrichs
> <dale.henrichs at gemtalksystems.com
> <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>
>
>
> On 9/26/15 11:59 AM, Mariano Martinez Peck wrote:
>>
>>
>> On Sat, Sep 26, 2015 at 3:08 PM, Dale Henrichs via Glass
>> <glass at lists.gemtalksystems.com
>> <mailto:glass at lists.gemtalksystems.com>> wrote:
>>
>>
>> If you are doing this in an interactive session, then it is
>> possible the the interactive gem is the culprit ...
>> login/logout from the interactive gem would solve that ... if
>> it is not an interactive session then looking for a "rogue"
>> topaz process or gem process is called for:
>>
>> ps -efw | grep topaz # find topaz sessions
>> ps -efw | grep TCP | grep sys/gem # find interactive gems
>>
>>
>> Hi Dale,
>>
>> This is a little comment to say that I do NOT get that output in
>> my Linux. I think that if gems are opened in the linked way they
>> may look different at `ps` level.
>>
> How do you run your gems "linked"? And what does the ps output
> look like?
>
>
> The way I run seaside gems:
>
> cat << EOF | nohup $GEMSTONE/bin/topaz -u "Seaside-$1-$2" -l -q -e $4
> -I $APPLICATION_DIR/.topazini 2>&1 >>
> $APPLICATION_LOG_DIR/${1}_server-${2}.log &
>
> And this is the ps output:
>
> debrist+ 6163 1 0 04:06 ? 00:00:00
> /opt/gemstone/product/bin/topaz -u Seaside-FastCGI-40110 -l -q -e
> /opt/gemstone/product/seaside/etc/seaside30.conf -I
> /quuve/sites/debrisTesting/gemstone/.topazini
>
> This is the way I open an interactive topaz:
>
> su -m $GEMSTONE_USER -c "$GEMSTONE/bin/topaz -l -e $GEMSTONE_EXE_CONF
> -I $APPLICATION_DIR/.topazini"
>
> And this is the ps output:
>
> debrist+ 7225 7224 0 14:55 ? 00:00:00
> /opt/gemstone/product/bin/topaz -l -e
> /quuve/sites/debrisTesting/gemstone/etc/gem.conf -I
> /quuve/sites/debrisTesting/gemstone/.topazini
>
>
> This is on GemStone 3.1.0.6 and CentOS 7.
>
Okay, but all of those guys will show up in the first case - scanning
for topaz processes ... a gem process is launched when you use a
non-linked topaz (in which case you get both a gem and topaz process) or
when you launch a client from tODE, gemtools, jade, or gbs ...
technically you can create a c program with the gci libraries running as
a linked session (similar to topaz -l) but then you'd know about those
processes as well ...
Dale
Dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150926/3046d77b/attachment.html>
More information about the Glass
mailing list