Getting Data In

Why does service.export REST API fail when _raw is not excluded?

dsmith14
New Member

Using Java API and requesting a streaming export from Splunk a search like this:

search index="client_ndx" sourcetype="client_source" (field1 =  "*"  )   | regex field1 !=  "val1|val2|val3"   | fields field1, field2,field3,field4 , _time|fields - _raw

(NOTE: ending with "|fields - _raw") returns the labeled fields, but ending it without that exclusion fails with the following error:

java.lang.RuntimeException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[124683119,213]
Message: JAXP00010004: The accumulated size of entities is "50,000,001" that exceeded the "50,000,000" limit set by "FEATURE_SECURE_PROCESSING".
        at com.splunk.ResultsReaderXml.getNextEventInCurrentSet(ResultsReaderXml.java:128)
        at com.splunk.ResultsReader.getNextElement(ResultsReader.java:87)
        at com.splunk.ResultsReader.getNextElement(ResultsReader.java:29)
        at com.splunk.StreamIterableBase.cacheNextElement(StreamIterableBase.java:87)
        at com.splunk.StreamIterableBase.access$000(StreamIterableBase.java:28)
        at com.splunk.StreamIterableBase$1.hasNext(StreamIterableBase.java:37)
        at com.insightrocket.summaryloaders.splunk.SplunkParser.run(SplunkParser.java:112)
        at java.lang.Thread.run(Thread.java:745)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[124683119,213]
Message: JAXP00010004: The accumulated size of entities is "50,000,001" that exceeded the "50,000,000" limit set by "FEATURE_SECURE_PROCESSING".
        at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:596)
        at com.sun.xml.internal.stream.XMLEventReaderImpl.nextEvent(XMLEventReaderImpl.java:83)
        at com.splunk.ResultsReaderXml.readSubtree(ResultsReaderXml.java:423)
        at com.splunk.ResultsReaderXml.getResultKVPairs(ResultsReaderXml.java:325)
        at com.splunk.ResultsReaderXml.getNextEventInCurrentSet(ResultsReaderXml.java:124)
        ... 7 more

I specifically used the system.export to get a stream and bypass the maximum record count, but a change in the system now requires the use of the _raw field

0 Karma

to4kawa
Ultra Champion

NOT is search first, and then, exclude.
you should search specifically.

0 Karma

dsmith14
New Member

That does not appear relevant to the issue, and since the range of values in that field is much larger (and changing) than the ones that need to be excluded, I don't think a specific search is suitable in this case

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...

Index This | What has goals but no motivation?

June 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Deep Dive: Accelerate threat investigation with Splunk’s AI Assistant in Security

AI is one of the biggest topics in the market today, and for security teams, its value goes far beyond the ...