cancel
Showing results for 
Search instead for 
Did you mean: 

java.lang.stackoverflowerror

Former Member
0 Kudos

Hi All,

I am running a query in Portal. When I add in several key figures and run the query I receive this error:

java.lang.StackOverflowError

[EXCEPTION]

java.lang.StackOverflowError at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:176) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) ...

Does anybody know what the cause of the issue is and how to resolve it?

Thank you.

Edited by: AYeung on Mar 23, 2010 3:56 PM

Accepted Solutions (0)

Answers (7)

Answers (7)

former_member225306
Active Contributor
0 Kudos

Please apply the note: 1343814 it should resolved your issue.

Regards,

Venkat

Former Member
0 Kudos

K M R,

I would require proof or reasoning in order to implement new support packages. It would be great if you could perhaps provide the direct cause of the error.

Thanks.

former_member185071
Contributor
0 Kudos

Hi AYeung Is it working on your bex analyzer ..? If yes and it is only giving error in portal then probably its the issue with acceptable currency symbols which not supported for your Supportpack .Obviously just check with OSS message it some thing that needs to work with Support pack issue i faced the similar kind of issue when i was with SP 17 now i am in latest so i dint get this kind of error. Hope its clear a little..! Thanks K M R

>

> Hi All,

>

> I am running a query in Portal. When I add in several key figures and run the query I receive this error:

>

> java.lang.StackOverflowError

> [EXCEPTION]

> java.lang.StackOverflowError > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:176) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) > at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsCurrencyUnitMerger.isEmpty(RsCurrencyUnitMerger.java:177) ...

>

> Does anybody know what the cause of the issue is and how to resolve it?

>

> Thank you.

>

> Edited by: AYeung on Mar 23, 2010 3:56 PM

Former Member
0 Kudos

Ralf,

I've come across that note in my searches, but I've checked our system and that note has already been applied.

Thank you.

Former Member
0 Kudos

Hi,

does note 1343814 match your problem?

Best regards,

Ralf

Former Member
0 Kudos

Des,

This note is not applicable on our system.

Thank you.

desgallagher
Contributor
0 Kudos

Hello,

I don't know your BW version but in the past this problem has been resolved by applying the SAP note

1123807 : Termination when you execute a query

Best Regards,

Des