cancel
Showing results for 
Search instead for 
Did you mean: 

BO4 - java out of memory

03-19-2014 10:11 AM
411 views 7 comments Go to solution
0 Likes
SAP Managed Tags
Subscribe

Hi,

user reported java out of memory error (screenshot below).

They got this doing.

Received an out of error memory when trying to copy out a report to the clipboard to paste into excel

Checked the bo4 servers and plenty spare memory on them.

Also checked the java.exe proceseses and only ones with over 600mb memory being used the dsl brideg(3.5) and tomcat (2).

We have spilt the aps as per best practice (8gb) for dsl ) and have max memory pool of 4gb for tomcat so not sure why got this error 

Any ideas and how can we determine which server/process  caused this error?

0 Likes

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes
former_member272336
Participant
0 Likes

Hi,

Thanks for message.

Is this definitely a client side memory problem rather than server-side?

User is using bi launchpad.

Thanks

Former Member
0 Likes

If issue occurs in webi rich client, then we can confirm that it is client issue.

If it is in internet rich Client ( from launch pad), then we can check it on the server side.

what is the flow of the reports,

are they using UNV/UNX or BICS connection for the webi report?

you can give a try by making the change and try.

former_member272336
Participant
0 Likes

Hi,

Cannot replicate but will ask user to increase client side jre memory.

Have also increased the xmx parameter from 2 to 4 gb on one of the aps as have enough memory.

Unx universe oracle data source.

Answers (2)

Answers (2)

jens_grotholtmann
Active Participant
0 Likes

Another option would be using the build-in export functionality to excel. Even the results might be better.

former_member272336
Participant
0 Likes

Thanks for advice.

Former Member
0 Likes

Hi Philip,

Are they getting the error in Webi rich clinet.

If report is robust and it has more tabs and a good amount of formatting in each tab, then we may get this error.

we can get past this error, however, by increasing my client-side JRE Java heap settings to something larger than the default;

set Java arguments –Xms256 –Xmx1024m –Xincgc, and no longer you will see the error after making the change in the client system.

Tune this parameters according to your requirement.