memory issue CL_SWF_UTL_WAPI_MESSAGE method GET_MESSAGE_LINES

[JANSSENS Koenraad]

Hi Mike

They did some defaulting which lowered their primary selection drastically... that solved the problem.

Best Regards

K

>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
>Sent: Wednesday, March 10, 2010 1:17 PM
>To: SAP Workflow Users' Group
>Subject: Re: memory issue CL_SWF_UTL_WAPI_MESSAGE method GET_MESSAGE_LINES
>
>'bigger part of all available workflows'?
>I suspect that WAPIs may only be a contributing factor, it may be wise to
>break the internal report processing into smaller pieces, processing say
>10,000 work items at a time, or chunks of one month/year.
>
>On Wed, March 10, 2010 9:42 am, JANSSENS Koenraad wrote:
>> Hi
>>
>> Seems we have a memory issue in a workflow report.
>>
>> We receive a dump "No roll storage space of length 8768 available for
>> OCCURS area." while executing the report on the bigger part of all
>> available workflows.  It seems the cause is somewhere in
>> SAP_WAPI_OBJECTS_IN_WORKITEM when it fetches the messages via
>> CL_SWF_UTL_WAPI_MESSAGE.  I'm not developing the report myself so I don't
>> have a detailed view.. but did any of you have something likewise
>> happening before?
>>
>> I said to them to use the WAPIs instead of direct reads on the table..
>> maybe not the wiser idea after all...
>>
>> Best Regards
>>
>> Koenraad
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug