Customizing workflow runtime system

[Elisabeta Brown]

Hi Florin!
Thank you very much for your reply, it did help us to relax a bit. Now after reading what you said and comparing transaction SWPA in two different systems with different ECC versions, I understand what you said: in the older version buffering is not an option and also container serialization is not active. For know we will switch off the buffering so that no more short dumps occur but I believe the size of the shared memory will have to be increased.
Thank you again for your reply.
Kind regards,
Elisabeta
> Date: Thu, 15 Jan 2009 13:51:08 +0100> From: florin.wach at gmx.net> Subject: Re: Customizing workflow runtime system> To: sap-wug at mit.edu> > Hello Elisabeta,> > before ECC 6.00 this option to cache the container definition in shared memory wasn't available: The system performance was okay.> I have gone through the where-used-list of the shared-memory class and found no influence to the XSLT serialization.> > Best wishes,> Florin> > -------- Original-Nachricht --------> > Datum: Thu, 15 Jan 2009 12:30:33 +0000> > Von: Elisabeta Brown <elisabetabrown499 at hotmail.com>> > An: sap-wug at mit.edu> > Betreff: Customizing workflow runtime system> > > > > Hello again all!> > > > I have just thought maybe didn't explain properly the problem that's why I> > had no reply so here I am, trying again:> > In SWPA - Customizing Workflow Runtime System we have in Container> > Serialization/Buffering both options selected:> > > > Container Serialization using XSLT> > Buffering of Definition Enhancements in Shared Memory> > > > Recently we have started getting short dumps as detailed in my previous> > message and after reading the OSS Note 1232973 realized that there is no more> > space for buffering in the database but increasing the space at the moment> > is not an option. Is there any implication on system performance if we> > switch off Buffering of Definition Enhancements in Shared Memory and also will> > the Container Serialization continue to work? If not what are the> > implications again on system performance?> > > > Any idea will be greatly appreciated.> > Many thanks,> > Elisabeta> > > > > > > > > > > > From: elisabetabrown499 at hotmail.comTo: sap-wug at mit.eduSubject: Container> > Serialization/BufferingDate: Tue, 13 Jan 2009 18:12:16 +0000> > > > Hi All! > > Recently we have started getting runtime errors of the> > SYSTEM_NO_SHM_MEMORY type > > when running periodic job for updating the shared memory area in our CRM> > system.> > > > After checking OSS Note 1232973 have understood that our only solution> > for now is to either switch off the buffering of container definitions in> > shared memory or change "abap/shared_objects_size_MB" to a higher value (SWPA)> > . At the moment we can’t change anything in the system due to patching> > exercise and therefore the only option is to switch off the buffering.> > My question is, will the Container Serialization Using XSLT be affected if> > we switch off the buffering or this will be carried out as normal? And> > also, how will the performance be affected by switching off the buffering,> > although if I understand right this is not taking place anyway as it short> > dumps.> > > > > > Any help will be greatly appreciated.> > > > Many thanks,> > Elisabeta> > > > > > Are you a PC? Upload your PC story and show the world Click Here!> > _________________________________________________________________> > Are you a PC?  Upload your PC story and show the world> > http://clk.atdmt.com/UKM/go/122465942/direct/01/> _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug
_________________________________________________________________
Are you a PC?  Upload your PC story and show the world
http://clk.atdmt.com/UKM/go/122465942/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090115/cce7097d/attachment.htm