3 Replies Latest reply on Jul 1, 2015 5:13 PM by shawkins

Data not getting parsed in Odata SAP for the collections having large data

singhall Jun 30, 2015 2:17 AM

While getting the data from BookingCollection from SAP demo system we are getting below exception. If we are trying to fetch data for any other collections its working fine.

The query which is getting fired from BaseQueryExecution is

https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT//BookingCollection?$select=carrid,connid,fldate,bookid,CUSTOMID,CUSTTYPE,SMOKER,WUNIT,LUGGWEIGHT,INVOICE,CLASS,FORCURAM,FORCURKEY,LOCCURAM,LOCCURKEY,ORDER_DATE,COUNTER,AGENCYNUM,CANCELLED,RESERVED,PASSNAME,PASSFORM,PASSBIRTH

After getting the result

parser.parse(new InputStreamReader(blob.getBinaryStream())); in BaseQueryExecution is throwing this exception

INFO | jvm 1 | 2015/06/29 15:02:18 | ERROR [CONNECTOR] Connector worker process failed for atomic-request=jnqGr9mczINv.6.1.14

INFO | jvm 1 | 2015/06/29 15:02:18 | com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in attribute value

INFO | jvm 1 | 2015/06/29 15:02:18 | at [row,col {unknown-source}]: [1,44449092]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:677) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:1037) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.StreamScanner.getNextChar(StreamScanner.java:785) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.BasicStreamReader.parseAttrValue(BasicStreamReader.java:1890) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:3063) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2961) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2837) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072) ~[woodstox-core-asl-4.2.0.jar:4.2.0]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.codehaus.stax2.ri.Stax2EventReaderImpl.nextEvent(Stax2EventReaderImpl.java:255) ~[stax2-api-3.1.1.jar:3.1.1]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2$StaxXMLEventReader2.nextEvent(StaxXMLFactoryProvider2.java:121) ~[odata-core-0.8.6.jar:0.8.6]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.odata4j.format.xml.AtomFeedFormatParser.parseEntry(AtomFeedFormatParser.java:334) ~[odata-core-0.8.6.jar:0.8.6]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.odata4j.format.xml.AtomFeedFormatParser.parseFeed(AtomFeedFormatParser.java:168) ~[odata-core-0.8.6.jar:0.8.6]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.odata4j.format.xml.AtomFeedFormatParser.parse(AtomFeedFormatParser.java:156) ~[odata-core-0.8.6.jar:0.8.6]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.odata4j.format.xml.AtomFeedFormatParser.parse(AtomFeedFormatParser.java:44) ~[odata-core-0.8.6.jar:0.8.6]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.translator.odata.BaseQueryExecution.parse(BaseQueryExecution.java:91) ~[federation-connectors-sap-translator-translator-odata-SNAPSHOT.jar:SNAPSHOT]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.translator.odata.BaseQueryExecution.executeWithReturnEntity(BaseQueryExecution.java:123) ~[federation-connectors-sap-translator-translator-odata-SNAPSHOT.jar:SNAPSHOT]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.translator.odata.ODataQueryExecution.execute(ODataQueryExecution.java:92) ~[federation-connectors-sap-translator-translator-odata-SNAPSHOT.jar:SNAPSHOT]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:337) ~[teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at java.lang.reflect.Method.invoke(Method.java:483) ~[na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:209) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at com.sun.proxy.$Proxy235.execute(Unknown Source) [na:na]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.10.0.Final.jar:8.10.0.Final]

INFO | jvm 1 | 2015/06/29 15:02:18 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | at java.lang.Thread.run(Thread.java:745) [na:1.8.0_31]

INFO | jvm 1 | 2015/06/29 15:02:18 | WARN [PROCESSOR] TEIID30020 Processing exception for request jnqGr9mczINv.6 'TEIID30504 vdsSAPFlight-sapConnFlight-sap-nw-gateway: Unexpected EOF in attribute value

INFO | jvm 1 | 2015/06/29 15:02:18 | at [row,col {unknown-source}]: [1,44449092]'. Originally TeiidProcessingException StreamScanner.java:677. Enable more detailed logging to see the entire stacktrace.

INFO | jvm 1 | 2015/06/29 15:22:13 | ERROR [CONNECTOR] Connector worker process failed for atomic-request=jnqGr9mczINv.8.0.15

INFO | jvm 1 | 2015/06/29 15:22:13 | com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in end tag

INFO | jvm 1 | 2015/06/29 15:22:13 | at [row,col {unknown-source}]: [1,46216620]

Thanks

Amit

1. Re: Data not getting parsed in Odata SAP for the collections having large data

singhall Jun 30, 2015 3:54 AM (in response to singhall)

Seems like the response returned doesn't have the full data, i.e .not the complete XML , that's why its not able to parse the output.

Should we implement the paging around the data for this , using $TOP and $SKIP?
Actions
2. Re: Data not getting parsed in Odata SAP for the collections having large data

rareddy Jun 30, 2015 7:31 AM (in response to singhall)

Amit,

The translator already should be supporting the $TOP and $SKIP when you use LIMIT, OFFSET in your SQL query. I am not sure what you mean by "should we implement paging"?

Ramesh..
Actions
3. Re: Data not getting parsed in Odata SAP for the collections having large data

shawkins Jul 1, 2015 5:13 PM (in response to rareddy)

> Seems like the response returned doesn't have the full data, i.e .not the complete XML , that's why its not able to parse the output.

Make sure you aren't hitting a proxy limitation in between that is truncating the response.

Otherwise as Ramesh is saying just use limit/offset in your user query and in most circumstances it will get pushed down.

Ramesh how does the batching logic in the odata translator work in general - does fetchNextBatch mean that we'll ask for multiple subsets?
Actions

Go to original post