Error " Table name cannot be null ... "

dazine1
Kilo Explorer

Hello,

We have 3 Errors that are displayed uninterruptedly in our dev platform, we don't know what the root problem is..
Those are the errors:

Table name cannot be null: java.lang.IllegalStateException: Table name cannot be null: com.glide.db.TableDescriptor.<init>(TableDescriptor.java:77)

com.glide.db.TableDescriptor.get(TableDescriptor.java:82)

com.glide.db.CompositeElement.<init>(CompositeElement.java:86)

com.glide.db.conditions.SpecialCases.get(SpecialCases.java:70)

com.glide.db.meta.Query.addQuery(Query.java:109)

com.glide.db.DBQuery.addQuery(DBQuery.java:388)

com.glide.amb.cluster.AMBQueue.query(AMBQueue.java:98)

com.glide.amb.cluster.AMBQueue.poll(AMBQueue.java:86)

com.glide.amb.cluster.AMBClusterSynchronizer.processMessages(AMBClusterSynchronizer.java:164)

com.glide.amb.cluster.AMBClusterSynchronizer.run(AMBClusterSynchronizer.java:128)

Table name cannot be null: java.lang.IllegalStateException: Table name cannot be null: com.glide.db.TableDescriptor.<init>(TableDescriptor.java:77)

com.glide.db.TableDescriptor.get(TableDescriptor.java:82)

com.glide.ts.service.TSTextSearchService.isIR(TSTextSearchService.java:145)

com.glide.ts.service.TSTextSearchService.buildQueryContext(TSTextSearchService.java:121)

com.glide.db.DBQuery.getQueryContext(DBQuery.java:1958)

com.glide.db.DBQuery.execute(DBQuery.java:1928)

com.glide.amb.cluster.AMBQueue.query(AMBQueue.java:100)

com.glide.amb.cluster.AMBQueue.poll(AMBQueue.java:86)

com.glide.amb.cluster.AMBClusterSynchronizer.processMessages(AMBClusterSynchronizer.java:164)

com.glide.amb.cluster.AMBClusterSynchronizer.run(AMBClusterSynchronizer.java:128)

Recovering from an error in the AMBClusterSynchronizer: java.lang.NullPointerException:

Thank you.

Best regards,
Sohaib

3 REPLIES 3

ville2
Kilo Contributor

Hello,

 

Did you find any solution for this error?

We are facing it also and only way to fix it seems to be booting the SN app.

 

Br. Ville Kuhlman

Hello Ville,

Yes That's exactely what we have done, it is a instance problem. As I remember, we have restarted the node and it worked just fine after that.

Best regards
Sohaib

britwill
ServiceNow Employee
ServiceNow Employee

Hello Sohaib and Ville,

Your corrective actions were spot-on as restarting the nodes provides relief. See the issue summary below.

Issue Summary: 

System logs replete with the following error message: 

[Start error message]

Table name cannot be null: java.lang.IllegalStateException: Table name cannot be null: com.glide.db.TableDescriptor.<init>(TableDescriptor.java:77)

com.glide.db.TableDescriptor.get(TableDescriptor.java:82)

com.glide.db.CompositeElement.<init>(CompositeElement.java:86)

com.glide.db.conditions.SpecialCases.get(SpecialCases.java:70)

com.glide.db.meta.Query.addQuery(Query.java:109)

com.glide.db.DBQuery.addQuery(DBQuery.java:388)

com.glide.amb.cluster.AMBQueue.query(AMBQueue.java:98)

com.glide.amb.cluster.AMBQueue.poll(AMBQueue.java:86)

com.glide.amb.cluster.AMBClusterSynchronizer.processMessages(AMBClusterSynchronizer.java:164)

com.glide.amb.cluster.AMBClusterSynchronizer.run(AMBClusterSynchronizer.java:128)

[End error message]

Root Cause:

These errors are symptomatic of a known problem (referenced by PRB935863), that prevents instances from releasing unused memory. Note: Your instance version may have been Istanbul.

Investigation Details: 

Another example of the messages being logged: 

glide.amb.cluster.synchronizer SYSTEM WARNING *** WARNING *** [AMB] AMBClusterSynchronizer Did not process messages because the AMBSessionMessageQueues has reached max capacity. 

Work around/ Fix: 

A fix for this problem is already available in the following releases: 

Istanbul Patch 5 Hot Fix 1 

Istanbul Patch 6 

Kingston Patch 12/13

London Patch 4 HF2

London Patch 5

 

Additionally the fix will be available in all Jakarta releases. As you have found, a restart of your instance will momentarily provide relief. 

Best regards

Brit