Skip to main content

Salesforce System Error: 1148877694-2467 (681892207) (681892207) when using JSON generator class in apex

Today i encountered a very interesting error when i was using JSON generator .The error said FATAL_ERROR System.UnexpectedException: Salesforce System Error: 1148877694-2467 (681892207) (681892207).

Looking into the error my first thing was to run through my code again and again .I referred the following documents on JSON generator class 

The code in my eyes look pretty simple and here is the exact snippet that was throwing the exception

JSONGenerator gen = JSON.createGenerator(true);
gen.writeNumberField('abc', 1.21);
gen.writeStringField('def', 'xyz');
String pretty = gen.getAsString();//This statement use at the end only .It ends the JSON 
System.debug('STRING JSON'+pretty);
gen.writeStringField('def', 'xyz');

After the line 6 (where i am printing the log )i have the following statement in my debug log 13:24:03:048 FATAL_ERROR System.UnexpectedException: Salesforce System Error: 1148877694-2467 (681892207) (681892207)

I decided to read the document again and discovered that the when i use the method getAsString method of JSON generator class the apex automatically closes the JSON and hence attempting to start writing the Object after closing generates an error .

Though this is simple issue but the error message is not caught properly in the salesforce backend .

So the conclusion is always using getAsString of JSON generator class should be practiced .

Never use it even for the debug statements.

This is one of the rare cases where error message is misleading.Hope this helps for people trying to google and find why the error is occuring when using JSON generator.

Just commmenting Line 5 and line 6 will resolve the issue.
Happy Coding !

Popular posts from this blog

TLS 1.0 has been disabled For Sandbox - Salesforce

Salesforce has finally disabled TLS 1.0 in sandboxes .This is in preparation for disablement later in 2017 for PRODUCTION instances .

Now this would have not impacted your integrations in PRODUCTION org but if your integration is broken in your sandbox ,this means you have only few months to sort this and fix before this affects your integration for PROD live users .
Before we deep drive on how to possibly fix this and work with your external systems to figure solution ,lets first understand what is TLS and why did SFDC moved to 1.x and had to disable TLS 1.0
TLS 1.0 Explained

TLS 1.1 Improvements 
Added protection against cipher-block chaining (CBC) attacks. Support for IANA registration of parameters.

Clearly TLS 1.1 is more secure(Compared to 1.0) and protects salesforce resources against CBC attacks .
Identify if this change broke anything .The things that can be affected in your instances are as below Web requests to Salesforce URLs that require authenticationWeb requests to the login pag…

Opening Modal Using Lightning Component Framework of SFDC

One of my friend from India threw a challenge .The challenge was to open a modal by using latest and greatest lightning components framework and modals design from SLDS .For the love of community I thought of sharing the entire code base that I did .

So here we start ..

Business Use Case - Need a handy SalesLeader board component that can be used to display the Sales revenue generated by each sales rep for current year in the order of decreasing total revenue .On click of the tile ,we will show detail opportunity list aggregating the revenue .

The component can be dragged in lightning design experience or in App builder lightning Page .

Video Demonstration-

SalesLeaderBoard from Mohith Kumar Shrivastava on Vimeo.

Frameworks Used -
Lightning Design Systems (SLDS) for CSSLightning Component Framework for client side logicApex aura enabled class for backend logicApproach
The component hierarchy is very important to imagine or mindmap before we dig deeper- SalesLeaderMain

Invoking Apex Callout From Process Builder

Process builder is GA in Spring 15 and one of the queries I came across was around how to invoke apex callouts from Process builder .

Before process builder came we had two common approaches of calling webservice 

1)We have outbound messages as one of the Actions for workflows.This works if other party implements the WSDL that is generated once Outbound messaging is defined with appropriate end point .

2)Most of times future method invoked through triggers allowed to do apex callouts and invoke external web service provided the future method is annotated with @future(callout=true).This provides lot of flexibility and one of the best approaches .

3)Flow triggers was in BETA and this was also one of the ways we could invoke callouts provided the Flow implements process plugin .To understand in detail how to implement process plugin refer to the below example

The purpose of this blogpost is to demonstrate the new possibility of invoking apex callout through Process Builder 

I tried initi…