cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry Sales Manager Initial Load problem

rpanneel
Participant
0 Kudos

Hello,

We've implemented the Agentry Sales Manager solution, everything work well in the development and test environments, but in production we have performance issues for specific users:

We have a user with:

  1. 5900 Accounts
  2. 21900 Contact Persons

Which are very large numbers, but the person responsible for our OSS question says this is feasible in the agentry environment.

The problem occurs when we perform the initial load/transmit for this user, the Accounts are processed like it should, but during the process of the contact persons something goes wrong:

I see that the function module /SYCLO/CRMMD_DOMYCONTACT_GET is being started and completely processed (Initially we had a dump with a timeout, but this has been solved).

Then the Agentry server is processing the results of that function module:

In the log I notice these lines:

getDocumentLinks::begin

getDocumentLinks::getDocumentLinks

Afterwards the server processes the results via the steplets, after which the data is being processed on the device (iPad). Then the employeeFetch should be triggered.

In our test with a user with lesser data this happens, but in this case we notice the following:

2015/04/16 15:46:48.852:           + BackEnd=Java-1

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::endFetchRemoval::::begin

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::endFetchRemoval::::--------------------------------

2015/04/16 15:46:48.852:           + BackEnd=Java-1

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::beginFetchObjectRead::::begin

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::beginFetchObjectRead::::--------------------------------

2015/04/16 15:46:48.852:           + BackEnd=Java-1

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::endFetchObjectRead::::begin

2015/04/16 15:46:48.852:             + BackEnd=Java-1

2015/04/16 15:46:48.852:               com.syclo.sap.FetchSession::endFetchObjectRead::::--------------------------------

2015/04/16 15:49:21.108: + Thread=4172

2015/04/16 15:49:21.108:   + Server=Agentry

2015/04/16 15:49:21.108:     + BackEnd=Java-1

2015/04/16 15:49:21.108:       Java Back End: current jvm memory usage is 1682243584 bytes

2015/04/16 15:49:38.096:   + Server=Agentry

2015/04/16 15:49:38.096:     + BackEnd=Java-1

2015/04/16 15:49:38.096:       Java Back End: current jvm memory usage is 1682309120 bytes

2015/04/16 15:49:55.100:   + Server=Agentry

2015/04/16 15:49:55.100:     + BackEnd=Java-1

2015/04/16 15:49:55.100:       Java Back End: current jvm memory usage is 1682374656 bytes

After the last line nothing else happens. 

In the Agentry GUI I see also that the Connection has disappeared  without an error/exception what so ever...

Anybody has an idea what might cause this issue?

We've set the timeout and keepalive parameters to 36000 seconds (10 hours) in the agentry ini, so I think that it isn't a time out.

Thanks in advance!

Kind regards,

Robin

Accepted Solutions (0)

Answers (1)

Answers (1)

jason_latko
Active Contributor
0 Kudos

Robin,

I did not work on Sales Manager, but if you are trying to download (fetch) thousands of accounts and contact persons for a single user and these are actually object instances and not complex table data, then that is a problem.  Object collections should be kept in the hundreds for each client, not the thousands.  It is theoretically possible to download thousands, but seems you are running into a server memory limit.  It all depends on how complex the individual objects are, and how many sub-collections they contain.

Somehow allocating more memory for the SMP Server application may help, but it sounds like you are just trying to download (fetch) too much object data.  Even if the data made it down to the client, the performance would probably be really sluggish.

What client platform are you using?  Does it make a difference if you try a different platform?

Jason Latko - Senior Product Developer at SAP

0 Kudos

Can you please check Application Log (SLG1) and for short dumps (ST22) in SAP CRM to make sure everything is good in CRM. Also I would recommend monitoring the Process (SM50) to make sure it is not timing out in CRM.

thanks

Chandra

rpanneel
Participant
0 Kudos

Hi Jason,

Thanks for your answer, it is a standalone Agentry server (without SMP). It looks to me also that the amount of data being fetched is too big. But the customer wants to get it on the device as the person on OSS said it should be possible.

When I look in the AgentryGUI on the server during the fetch I notice the following (see screenshot below):

The fetch is still busy but the connection is gone. At the point of the screenshot we see the Fetch is taking more then 3 hours (9:27 AM to 12:51 PM), but the connection for that user has been gone in the AgentryGUI from around 11:00 AM.

Even stranger is that nowhere an exception is thrown. The process on the server continues until the complete data set is processed in the steplets (seen in the log). Then the server is trying to allocate more jvm heap space. But at some point process just stops. In stead of continuing with the process.

The data is also not sent to the device at that point, so the problem is somewhere on the agentry server it seems.

The server's memory is 8GB and i'v set the maxheapspace variable in the agentry.ini as following:

maxHeapSize=2048

In the log I see that the server that cap doesn't reach.

We run on an iPad, only iOS devices were in scope.

Any idea's on where we might change something else?

Kind regards,

Robin

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Robin,

If the fetch is taking more than 3 hours the first thing you should look at is the backend process to determine why it is taking that long.  I also agree that it is way too much data for an object collection but the first place to start is to improve the backend fetch performance so you can see if that much data can be handled on the client.

--Bill