Error message in system log : Cannot invoke "com.glide.monitor.AbstractBucketCollector.getName()"..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2025 02:49 AM
Hi all,
we have been reviewing our system logs and we foound out that we have over a thousand ERROR logs in com.glide.ui.ServletErrorListener resource with the following message:
Cannot invoke "com.glide.monitor.AbstractBucketCollector.getName()" because "ac" is null: java.lang.NullPointerException: Cannot invoke "com.glide.monitor.AbstractBucketCollector.getName()" because "ac" is null: com.glide.ui.monitor.BucketStats.write(BucketStats.java:31)
com.glide.ux.metrics.stats.ApplicationCollector.lambda$write$2(ApplicationCollector.java:52)
java.base/java.util.HashMap.forEach(HashMap.java:1421)
com.glide.ux.metrics.stats.ApplicationCollector.write(ApplicationCollector.java:49)
com.glide.ux.metrics.stats.ClientInteractionXmlStatsProvider.write(ClientInteractionXmlStatsProvider.java:28)
com.glide.sys.stats.Statistician.write(Statistician.java:48)
com.glide.sys.stats.Statistician.createDocument(Statistician.java:101)
com.glide.ui.XMLStats.toDocumentWithInclude(XMLStats.java:68)
com.glide.ui.XMLStats.stats(XMLStats.java:42)
com.glide.processors.XMLStatsProcessor.process0(XMLStatsProcessor.java:12)
com.glide.processors.AAdminProcessor.process(AAdminProcessor.java:21)
com.glide.processors.AProcessor.runProcessor(AProcessor.java:762)
com.glide.processors.AProcessor.processTransaction(AProcessor.java:313)
com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:187)
com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:175)
com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:58)
com.glide.sys.Transaction.run(Transaction.java:2734)
com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:35)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
java.base/java.lang.Thread.run(Thread.java:840)
Have you encountered such error log before? Could anyone please help me to understand what this indicates and what can be done about that?
Thank you.
Best Regards,
Marketa
- Labels:
-
Architect
- 1,669 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2025 04:03 AM
Is your issue resolved ? I'm also facing the same issue for Dynamic content Block which is added on the dashboard. when I refresh the content block on dashboard the error appears in the system log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2025 12:32 PM
We have also seen this. Has anyone been able to determine which object is creating the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2025 08:42 AM - edited 03-05-2025 08:42 AM
Hi Marketa,
This appears to relate to a shift to calling packages in a different way. SN has referred me to this article which directly references that package and a change to how it needs to be called. There's a tool to use to help change these calls (i'm investigating the same at the moment.).
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 05:42 AM
It's not. I promise. They're wrong. Package removal tool was important like 7+ years ago at this point.
It's not your code calling the package, it's some sort of OOB code that's calling that package under the hood.
Running into the same issue. Doubt I'll solve it. If I do I'll post back here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 06:12 AM
I'm getting something very similar in my ATF test cases this morning which have manifested themselves in hundreds of test cases/results which were fine yesterday. They are not actually failing but giving me the option to resolve using the Known Errors table but I need to understand what the issue is before I decide to make them Warning or Ignore.