Question
How to check the clipboard size of the requester
We have an SLA agent processing multiple flows(we have to process large size of soap responses), while processing the agent requestor is using all the heap space and giving PEGA0028 Alert in logs, as this is SLA agent, I am not able to check the clipboard size from Requestor management in SMA, i have tried profiling agent requestor but it does not give clipboard size. So I want to know memory usage of this agent processing at multiple points in flows
please suggest below points
I) is there any java method or pega functions to get clipboard size so that i log this
ii) is there any Performance Profiler tools to get Clipboard size of the agent requestor processing
iii) and how to stop processing when the requestor is consuming all JVM heap memory
iv) what is a maximum size of a clipboard can a requestor have.
Pegasystems Inc.
IN
Hi,
You can see the Clipboard size for requestors in SMA (Requestor Management page > select Requestor Name > click the Clipboard Size button). You can also see the Clipboard size using the Performance tool. I am not sure about modifying the size.
https://pdn.pega.com/how-use-sma-identify-amount-data-requestor-clipboards
There is no such limitation on the clipboard size.
Hi,
You can see the Clipboard size for requestors in SMA (Requestor Management page > select Requestor Name > click the Clipboard Size button). You can also see the Clipboard size using the Performance tool. I am not sure about modifying the size.
https://pdn.pega.com/how-use-sma-identify-amount-data-requestor-clipboards
There is no such limitation on the clipboard size.
There are already alerts in place for
- too many rows in a database query
- too many members on a page list
Clipboard will grow and shrink based on contents dynamically.
You can measure the clipboard size for requestor, refer the below link.
Also to know more about the alerts
You can refer this discussion as well
Also I believe you can you PAL to get clipboard details
https://pdn.pega.com/interpreting-performance-tool-pal-detail-display#addreading
Thank You
Machint Solutions Ltd.
IN
as I have mentioned in the question the flows are processed by SLA agent i am not able use PAL with clipboard size option or SMA requestor management.
and when the clipboard is size is increased beyond JVM heap size and the server goes down by just adding the alert in log with stopping the process so we want to stop processing to avoid a crash
Thanks.
Pegasystems Inc.
IN
Hi,
I could only find this discussion should be helpful beside that I don’t believe there is any other way.
Q.
I understand that from SMA and clipboard analyzer, we can see user requestor/clipboard size. Besides that,
1. Do we have configuration setting to set memory threshold limit on requestor level ? If is, once the requestor limit is reached, what the system will behave ?
2. For #2, will AES or other tool(s) have the feature to identify the session memory threshold is reached and alert the user ?
We want a tactical approach to limit the memory on requestor level so system will not run out of memory if one user accidentally pulled 500 MB data into clipboard. Also production support team don't want to monitor SMA 24/7 to get user clipboard sizing information, looking for an agent that can alert production support team if any user requestor have memory over threshold
Ans:
There is no alert or limit on clipboard size.
There are already alerts in place for
Hi,
I could only find this discussion should be helpful beside that I don’t believe there is any other way.
Q.
I understand that from SMA and clipboard analyzer, we can see user requestor/clipboard size. Besides that,
1. Do we have configuration setting to set memory threshold limit on requestor level ? If is, once the requestor limit is reached, what the system will behave ?
2. For #2, will AES or other tool(s) have the feature to identify the session memory threshold is reached and alert the user ?
We want a tactical approach to limit the memory on requestor level so system will not run out of memory if one user accidentally pulled 500 MB data into clipboard. Also production support team don't want to monitor SMA 24/7 to get user clipboard sizing information, looking for an agent that can alert production support team if any user requestor have memory over threshold
Ans:
There is no alert or limit on clipboard size.
There are already alerts in place for
- too many rows in a database query
- too many members on a page list
The alerts will be sent to AES. At present, AES does not consider these alerts to be 'critical' but you can probably override these rules through aescriteria ruleset.
It is possible to "automate SMA". Obviously, one can "web scrape" prsysmgmt, but better, the actual JMX Mbean operation to get requestor list with clipboard estimate is documented and may be called via any third party JMX tool. There's also an activity and service in PegaAESRemote ruleset that generically expose all the JMX Mbean operations to external monitoring tools (including AES). Would not be hard to write an agent activity on AES to poll all servers periodically to check overall clipboard page size for each user.
Thank You
Accepted Solution
Pegasystems Inc.
IN
Hi,
Also looks like you can tweak @baseclass.webwbclipboardanalyzeclipboard to get the size of requestor.
Let me know if its helpful.
Thank You
Machint Solutions Ltd.
IN
Thanks a lot Shekhar_Shubham
with pyLable property in this activity, i am able to get the snapshot of the clipboard page names and there sizes of the agent requestor at multiple stages of flow
this helps as big debugging aid
Pegasystems Inc.
IN
Hello Prasad,
As your saying your able to see PEGA0028 alerts which is nothing but GC not able to reclaim it's free memory .
Is the requestor passivation is happening properly ?
Do you see any threadumps or exception when the agent is running .
Even if we know the size of the clipboard for a requestor i don't think so we can modify it .
Provide the Pega rules log file to have a look if there are anything suspicious .
Thanks,
Arun