java.lang.ArrayIndexOutOfBoundsException: 21 in WebI

[Former Member]

Hi Experts,

This issue has been giving us headaches for the past few days.  We aren't sure how it

started and what's causing it.  Basically, we are getting the error:

java.lang.ArrayIndexOutOfBoundsException: 21

whenever we are trying to open the Query Panel of an Existing report or creating a new webi report using a universe.

I've been trrying to look for it, but I couldn't see any article.

Som additional information:

Platform:

-SAP BusinessObjects BI Platform 4.1 Support Pack 3

-Version: 14.1.3.1257

Universe:

-HANA datasource

Error Details:

java.lang.ArrayIndexOutOfBoundsException: 21

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.getEStructuralFeatureData(BinaryResourceImpl.java:1125)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadEObject(BinaryResourceImpl.java:1415)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadEObjects(BinaryResourceImpl.java:1173)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadFeatureValue(BinaryResourceImpl.java:1449)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadEObject(BinaryResourceImpl.java:1416)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadEObjects(BinaryResourceImpl.java:1173)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadFeatureValue(BinaryResourceImpl.java:1449)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadEObject(BinaryResourceImpl.java:1416)

at org.eclipse.emf.ecore.resource.impl.BinaryResourceImpl$EObjectInputStream.loadResource(BinaryResourceImpl.java:1156)

at com.sap.sl.core.emf.serial.EObjectSerializer$CustomBinaryResourceImpl.doLoad(EObjectSerializer.java:78)

at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1445)

at com.sap.sl.core.emf.serial.EObjectSerializer.fromBinaryStream(EObjectSerializer.java:253)

at com.sap.sl.core.emf.serial.EObjectSerializer.fromBinaryBytes(EObjectSerializer.java:288)

at com.sap.sl.sdk.parser.xml.datasource.DataSourceParser.parseDSLDataSource(DataSourceParser.java:208)

at com.sap.sl.sdk.parser.xml.datasource.DataSourceParser.parseAttachments(DataSourceParser.java:182)

at com.sap.sl.sdk.parser.xml.datasource.DataSourceParser.parse(DataSourceParser.java:155)

at com.sap.sl.sdk.parser.xml.OutputParser.parseOutput(OutputParser.java:188)

at com.sap.sl.sdk.parser.xml.OutputParser.parse(OutputParser.java:149)

at com.sap.sl.sdk.parser.xml.OutputParser.parseOutputs(OutputParser.java:101)

at com.sap.sl.sdk.parser.responses.ServerResponseHelper.parseOutputResponses(ServerResponseHelper.java:54)

at com.sap.sl.sdk.workspace.service.internal.WorkspaceLoadingService.processWorkspaceRequest(WorkspaceLoadingService.java:102)

at com.sap.sl.sdk.datasource.service.internal.DataSourceLoadingService.loadDataSourceFromServer(DataSourceLoadingService.java:221)

at com.sap.sl.sdk.dataprovider.service.DataProviderServiceImpl.loadDataSource(DataProviderServiceImpl.java:167)

at com.sap.sl.sdk.dataprovider.service.DataProviderServiceImpl.getDataSource(DataProviderServiceImpl.java:92)

at com.sap.webi.ui.context.managers.DataManager.loadDataSource(DataManager.java:3218)

at com.sap.webi.ui.data.WebIQueryPanelHost.loadDataSource(WebIQueryPanelHost.java:436)

at com.sap.webi.qp.abstractlayer.AbstractLayer.getDataSource(AbstractLayer.java:378)

at com.sap.webi.ui.data.UniverseQuerySheet.createUI(UniverseQuerySheet.java:520)

at com.sap.webi.ui.workbench.datamanager.qpframe.QPFrame.showQueryPanel(QPFrame.java:393)

at com.sap.webi.ui.context.managers.DataManager.showQueryPanel(DataManager.java:2982)

at com.sap.webi.ui.context.managers.DataManager.editDataProvider(DataManager.java:585)

at com.sap.webi.ui.tasks.workflows.EditDataProviderUITask.doneProcess(EditDataProviderUITask.java:90)

at com.sap.webi.toolkit.ui.tasks.WebITask$PrivateWorker.done(WebITask.java:378)

at javax.swing.SwingWorker$5.run(Unknown Source)

at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)

at sun.swing.AccumulativeRunnable.run(Unknown Source)

at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)

at javax.swing.Timer.fireActionPerformed(Unknown Source)

at javax.swing.Timer$DoPostEvent.run(Unknown Source)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$200(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

Kind Regards,

Mark

[Former Member]

Hi All,

We have faced the same problem but finally we resolved the issue.

In our environment we have installed the tomcat in different server so please follow the below steps If your webserver in different machine.

1. 1) Stop Tomcat (External).
2. 2) Take backup of BOE folder from <installdir>\SAP BusinessObjects\tomcat\webapps and delete BOE folder.
3. 3) Copy BOE (from BO Server) and paste to External Server into <installdir_tomcat>\webapps directory.
4. 4) Navigate to tomcat/work/catalina and rename localhost to localhost_old
5. 5) Start tomcat and wait for 10-15 mins
6. 6) Now please test the issue.

If the BO and Tomcat in same machine then please follow the below steps.

1. 1) Stop Tomcat.
2. 2) Take backup of BOE folder from <installdir>\SAP BusinessObjects\tomcat\webapps and delete BOE folder.
3. 3) Copy BOE (from working environment server) and paste to BO Server into <installdir_tomcat>\webapps directory.
4. 4) Navigate to tomcat/work/catalina and rename localhost to localhost_old
5. 5) Start tomcat and wait for 10-15 mins

If this also not work then please redeploy the war files and test the issue.

Thanks,

Rajesh

[LepreuxLoic]

Hi Mark,

I see two situations where this issue can occur :

- 1st one is when WebApplications have different level of binaries than what is present on BOE processing side. This is possible if an upgrade has been done in BOE but WebApplication server has not been upgraded or else WebApplications haven't been redeployed. It can be a little tricky to check .. by looking at 'last modified date' on binary files located in BOE installation and WebApp server.

- 2nd one was caused by a problem discovered not so long ago and already fixed in recent releases, please refer to SAP Note 2190372 for more details. (please not this Note refers to BEx data source, but it's not limited to this one ...)

Regards,

Loic

[Former Member]

Hi,

On our end, we are experiencing the error in all our universes.  What happened was we upgraded from 4.1 SP3 to 4.1 SP5 Patch 6.  We have a load balancer for our 2 bobj servers(?).  We noticed that the upgrade only affected one server, and the other one with the lower version, was getting the error.

Have you done any upgrade recently?

Thanks!

Mark

[Former Member]

Hi Mark,

Yes, we recently upgraded from 4.1 SP2 to SP6.

Any luck in finding the solution. Please post if you find anything

Thanks

[Former Member]

Hi,

check the version of the bobj app server.  Check it using the direct path and not the load balancer url.  Hopefully, i can explain it correctly.  We have a load balancer and 2 app servers (?).  Access the server urls directly, then check the version in BI Launchpad.

What we found was that app server A got migrated to 4.1 SP5 Patch 6, but app server B remained 4.1 SP3.

Kind Regards,

Mark

[former_member191664]

Can you apply SAP KB 1880015 - When creating a report based on BEX query the objects are not displayed and getting error java.lang.ArrayIndexOutOfBoundsException: 9 on http://service.sap.com/sap/support/notes/1880015 and hope this works?

Regards,

Jin-Chong

[Former Member]

Hi Jin,

Thanks for referring the SAP KB - 1880015.

As per the KB we already have the below parameter configured in our APS command line hosting the DSL service.

"-Dbusinessobjects.connectivity.directory=C:/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0//dataAccess/connectionServer"

Thanks

[former_member182521]

Have you tried opening the report in your UDT/IDT and check for any anomalies?

[Former Member]

Hi Manikandan,

There are no issues with the Universe. Check Integrity shows no errors or warnings. Hope Universe is fine as able to create the report using Rich client successfully without issues.

Thanks

[former_member182521]

Just a thought. Can we try to access from a different Web/Application server other than the one which you are using now Something like accessing the Test environment from Dev. environments Tomcat. Atleast this will confirm is there any issue with your Web layer.

[Former Member]

Hi Mark,

I got this error one week before and I am still trying to find an answer.

When trying to create a new WEBI report "java.lang.ArrayIndexOutOfBoundsException: 21" error throws up. In my case it is happening only for a particular universe which we migrated after the upgrade to SP6, but working fine for the same universe in rich client.

I tried changing the preference from Applet to HTML in Launchpad and tried creating a report, this time it just shows "21"

Still searching for a solution.

Please post in case if you find any solution.

Thanks