NPE in BusinessTagModelDao

未关闭
#69 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
java
领域
backend

调研方向

Start with BusinessTagModelDao.java at line 132, where the stack trace reports the NullPointerException, and trace the constructor call from BusinessAccountTagModelDao.java and BusinessTagModelDao.create(). The report says the failure was seen in production but is unsure how to reproduce it. Done means identifying the null value and addressing the failure; the issue does not specify a reproducible case or expected behavior.

由索引模型根据 Issue 内容生成。

描述

bug

Seen in the field (unsure how to reproduce it):

2017-02-23T10:47:00,184+0000 lvl='ERROR', log='KillbillLogWriter', th='Thread-26', xff='', rId='', aRId='14616', tRId='2125', Fatal NotificationQ dispatch error, data corruption...
org.apache.felix.log.LogException: org.killbill.notificationq.NotificationQueueException: java.lang.NullPointerException
	at org.killbill.notificationq.NotificationQueueDispatcher.handleNotificationWithMetrics(NotificationQueueDispatcher.java:205)
	at org.killbill.notificationq.dispatching.NotificationCallableCallback.dispatch(NotificationCallableCallback.java:51)
	at org.killbill.notificationq.dispatching.NotificationCallableCallback.dispatch(NotificationCallableCallback.java:32)
	at org.killbill.queue.dispatching.Dispatcher$CallableQueue.call(Dispatcher.java:103)
	at org.killbill.queue.dispatching.Dispatcher$CallableQueue.call(Dispatcher.java:86)
	at org.killbill.commons.concurrent.WrappedCallable.call(WrappedCallable.java:42)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.killbill.commons.concurrent.WrappedRunnable.run(WrappedRunnable.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException: null
	at org.killbill.billing.plugin.analytics.dao.model.BusinessTagModelDao.<init>(BusinessTagModelDao.java:132)
	at org.killbill.billing.plugin.analytics.dao.model.BusinessAccountTagModelDao.<init>(BusinessAccountTagModelDao.java:39)
	at org.killbill.billing.plugin.analytics.dao.model.BusinessTagModelDao.create(BusinessTagModelDao.java:54)
	at org.killbill.billing.plugin.analytics.dao.factory.BusinessTagFactory.createBusinessTags(BusinessTagFactory.java:67)
	at org.killbill.billing.plugin.analytics.dao.BusinessTagDao.update(BusinessTagDao.java:45)
	at org.killbill.billing.plugin.analytics.dao.AllBusinessObjectsDao.update(AllBusinessObjectsDao.java:65)
	at org.killbill.billing.plugin.analytics.AnalyticsListener.handleAnalyticsJob(AnalyticsListener.java:252)
	at org.killbill.billing.plugin.analytics.AnalyticsListener.access$100(AnalyticsListener.java:66)
	at org.killbill.billing.plugin.analytics.AnalyticsListener$1.handleReadyNotification(AnalyticsListener.java:137)
	at org.killbill.notificationq.NotificationQueueDispatcher.handleNotificationWithMetrics(NotificationQueueDispatcher.java:203)
	... 10 common frames omitted
主要语言
Java
星标
13
派生
33
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

killbill/killbill-analytics-plugin 的其他 Issue

查看 killbill/killbill-analytics-plugin 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。