Hello All,
i work on windows XP sp2 with
VW7.4.1 .
I'have load Gemstone
GbsTools 6.2.003
and SeasideFprWebToolKit 2.6b 1.30 and SeasideBase 2.6b 1.30
and SeasideScriptaculous
1.108.
When i'd'ont open gemstone session al work
fine.
For understand:
First setting:
A) all Gemstone session are
close.
B) from Explorer i open
http://localhost/...../browse and click on the link config
C) the http://localhost/...../config is browser and i can
config all application link
Second setting
A) one Gemstone session is open
and relative transaction work fine.
B) from Explorer i open
http://localhost/...../browse and click on the link config
C) now the
system load many objects from OODB and the http://localhost/...../config isn't browser
D) the system after load many
objects from OODB , open the Processor Monitor window with 'Memory space error'
.
E) If i save the image after
this, and reload the system become instable.
(
Gemstone session if open, is mystery close when i redo step B.
)
I have work around it to define the problem as
detailed.
I think the problem is
on: SeasidePlatformSupport
class vmStatisticsReportString
and/ or ObjectMemory
numOopsNumBytes.
I
remain in everyway on disposal for eventual explanations. Dario Trussardi Romano |
Hi Dario:
What is probably happening is that you are inadvertently setting an instVar of one of your domain objects you have from GemStone to the wrong thing. An example would be accidently setting an iVar to a ValueHolder rather than the ValueHolder's value. When you do this, you end up importing an enormous class hierarchy into GemStone, then clogging up the memory in your image. I've done this, it is an easy mistake to make. That image is now junk, build a new one. I have two suggestions: 1. *Never* save your image while logged in to GemStone. This *will* trash your image. GemStone is designed to hold and manipulate Hundreds of gigabytes; your VW image is not. 2. *Always* change your GBS configuration to "turn off" auto class generation in both the client and the server. If you have to "push" a client class into GemStone, change the setting to allow the class generation, do the <create class in GemStone> then disable the auto- generation again. Good luck and let us know if the suggestions don't fix the problem. On Aug 10, 2006, at 8:43 AM, Dario Trussardi wrote: > Hello All, > > i work on windows XP sp2 with VW7.4.1 . > > I'have load Gemstone GbsTools 6.2.003 > and SeasideFprWebToolKit 2.6b 1.30 > and SeasideBase 2.6b 1.30 > and SeasideScriptaculous 1.108. > > > When i'd'ont open gemstone session al work fine. > > For understand: > > First setting: > > A) all Gemstone session are close. > B) from Explorer i open http://localhost/...../browse and > click on the link config > C) the http://localhost/...../config is browser and i can > config all application link > > > Second setting > > A) one Gemstone session is open and relative transaction work > fine. > B) from Explorer i open http://localhost/...../browse and > click on the link config > C) now the system load many objects from OODB and the http:// > localhost/...../config isn't browser > D) the system after load many objects from OODB , open the > Processor Monitor window with 'Memory space error' . > > E) If i save the image after this, and reload the system > become instable. > ( Gemstone session if open, is mystery close when i redo > step B. ) > > > I have work around it to define the problem as detailed. > > I think the problem is on: SeasidePlatformSupport class > vmStatisticsReportString > and/ or ObjectMemory > numOopsNumBytes. > > > I remain in everyway on disposal for eventual explanations. > > Yours faithfully > > Dario Trussardi Romano > > > > Thanks!! Joseph Bacanskas [|] --- I use Smalltalk. My amp goes to eleven. |
Joseph Bacanskas wrote:
> > 1. *Never* save your image while logged in to GemStone. This *will* > trash your image. GemStone is designed to hold and manipulate Hundreds > of gigabytes; your VW image is not. Hmm. I frequently save my image while logged in to GemStone. I wouldn't recommend it as standard practice, but it shouldn't cause any particular problems. [...] > Good luck and let us know if the suggestions don't fix the problem. > Yes, Dario, please let us know if these problems continue. If the discussion continues to be more about GemStone than about VW, it might be better to move it to the GemStone customer forum. If you're not familiar with the customer forum, you can find more information at http://support.gemstone.com/gemstone_s/community/index.jsp. You need to register to use the support site, but registration is free and immediate. Regards, -Martin |
Martin McClure wrote: > Joseph Bacanskas wrote: >> >> 1. *Never* save your image while logged in to GemStone. This *will* >> trash your image. GemStone is designed to hold and manipulate >> Hundreds of gigabytes; your VW image is not. > > Hmm. I frequently save my image while logged in to GemStone. I > wouldn't recommend it as standard practice, but it shouldn't cause any > particular problems. Depends on what objects are over on GS and stubbed on the client, and how they are then accessed on startup or after startup. We basically never save while logged into GS. > > > [...] > >> Good luck and let us know if the suggestions don't fix the problem. >> > > Yes, Dario, please let us know if these problems continue. > > If the discussion continues to be more about GemStone than about VW, > it might be better to move it to the GemStone customer forum. If > you're not familiar with the customer forum, you can find more > information at > http://support.gemstone.com/gemstone_s/community/index.jsp. You need > to register to use the support site, but registration is free and > immediate. > > Regards, > > -Martin > -- Dennis Smith [hidden email] Cherniak Software Development Corporation +1 905.771.7011 400-10 Commerce Valley Dr E Fax: +1 905.771.6288 Thornhill, ON Canada L3T 7N7 http://www.CherniakSoftware.com |
In reply to this post by dario trussardi
You won't be able to restart your image if you save it while logged in.
The problem existed prior to around GBS 5.1.3 for both VA and VW. The problem was re-introduced in the first GBS releases to support VW 7. We haven't upgraded to the latest GBS yet, but I recall reading the problem is now fixed. It isn't a problem with the number of objects in an image. It is a problem with re-initialization of the GCI layer. Defunct proxies that were cached in a saved image might cause problems too, but it was GCI initialization that hosed people here. Paul Baumann IntercontinentalExchange | ICE 2100 RiverEdge Pkwy | 5th Floor | Atlanta, GA 30328 Tel: 770.738.2137 | Fax: 770.951.1307 | Cel: 505.780.1470 [hidden email] 24-hour ice helpdesk 770.738.2101 www.theice.com -----Original Message----- From: Martin McClure [mailto:[hidden email]] Sent: Friday, August 11, 2006 1:25 PM To: Joseph Bacanskas Cc: vwnc List; Dario Trussardi Subject: Re: Seaside config management and Gemstone session Joseph Bacanskas wrote: > > 1. *Never* save your image while logged in to GemStone. This *will* > trash your image. GemStone is designed to hold and manipulate > Hundreds of gigabytes; your VW image is not. Hmm. I frequently save my image while logged in to GemStone. I wouldn't recommend it as standard practice, but it shouldn't cause any particular problems. [...] > Good luck and let us know if the suggestions don't fix the problem. > Yes, Dario, please let us know if these problems continue. If the discussion continues to be more about GemStone than about VW, it might be better to move it to the GemStone customer forum. If you're not familiar with the customer forum, you can find more information at http://support.gemstone.com/gemstone_s/community/index.jsp. You need to register to use the support site, but registration is free and immediate. Regards, -Martin -------------------------------------------------------- This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. |
Free forum by Nabble | Edit this page |