zoneid欧洲/柏林nullpointerexception

mtb9vblg  于 2021-08-20  发布在  Java
关注(0)|答案(2)|浏览(499)

我编写了一个dateutil类,它将java.time.localdatetime转换为java.util.date并向后转换。当尝试获取系统默认时区或特定时区(欧洲/柏林)时,我得到一个异常。我检查了jvm时区的配置是否正确,是否正确。
以下是我的简单代码:

  1. import java.time.LocalDate;
  2. import java.time.LocalDateTime;
  3. import java.time.ZoneId;
  4. import java.util.Date;
  5. public class DateUtil {
  6. public static Date toDate(LocalDateTime dateTime) {
  7. System.out.println(System.getProperty("user.timezone"));
  8. ZoneId zone = ZoneId.of("Europe/Berlin");
  9. return Date.from(dateTime.atZone(zone).toInstant());
  10. }
  11. public static Date toDate(LocalDate date) {
  12. return Date.from(date.atStartOfDay(ZoneId.systemDefault()).toInstant());
  13. }
  14. }

这是一个例外:

  1. java.time.zone.ZoneRulesException: Invalid binary time-zone data: TZDB:Europe/Berlin, version: 2019c
  2. at java.time.zone.TzdbZoneRulesProvider.provideRules(TzdbZoneRulesProvider.java:141)
  3. at java.time.zone.ZoneRulesProvider.getRules(ZoneRulesProvider.java:227)
  4. at java.time.ZoneRegion.ofId(ZoneRegion.java:120)
  5. at java.time.ZoneId.of(ZoneId.java:411)
  6. at java.time.ZoneId.of(ZoneId.java:359)
  7. at de.swkbank.camunda.ks.smarta.util.DateUtil.toDate(DateUtil.java:11)
  8. at de.swkbank.camunda.ks.smarta.delegate.WorkingHoursCalculator.getNextDate(WorkingHoursCalculator.java:16)
  9. at de.swkbank.camunda.ks.smarta.delegate.WorkingHoursCalculatorTest.test(WorkingHoursCalculatorTest.java:37)
  10. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  11. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  12. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  13. at java.lang.reflect.Method.invoke(Method.java:498)
  14. at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
  15. at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
  16. at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
  17. at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
  18. at org.springframework.test.context.junit4.statements.RunBeforeTestExecutionCallbacks.evaluate(RunBeforeTestExecutionCallbacks.java:74)
  19. at org.springframework.test.context.junit4.statements.RunAfterTestExecutionCallbacks.evaluate(RunAfterTestExecutionCallbacks.java:84)
  20. at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
  21. at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
  22. at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
  23. at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
  24. at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
  25. at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:251)
  26. at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:97)
  27. at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
  28. at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
  29. at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
  30. at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
  31. at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
  32. at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
  33. at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
  34. at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
  35. at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
  36. at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
  37. at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
  38. at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
  39. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542)
  40. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770)
  41. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464)
  42. at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210)
  43. Caused by: java.lang.NullPointerException
  44. at java.time.zone.ZoneOffsetTransition.getDateTimeAfter(ZoneOffsetTransition.java:287)
  45. at java.time.zone.ZoneRules.<init>(ZoneRules.java:292)
  46. at java.time.zone.ZoneRules.readExternal(ZoneRules.java:456)
  47. at java.time.zone.Ser.readInternal(Ser.java:194)
  48. at java.time.zone.Ser.read(Ser.java:188)
  49. at java.time.zone.TzdbZoneRulesProvider.provideRules(TzdbZoneRulesProvider.java:136)
  50. ... 40 more

我的电脑有什么配置错误吗?它是一个带有win 10的microsoft surface。jvm是redhat jdk 1.8.0.242
已解决:模拟时出现问题 LocalDateTime::now . 这将导致异常。我可以通过注射疫苗来解决嘲笑问题 java.time.Clock 到now调用并在测试中返回固定时钟。

x9ybnkn6

x9ybnkn61#

不确定到底出了什么问题。但在定义时区的tzdb(时区数据库)中似乎存在一个问题,可能是损坏。
而您的tzdb在版本2019c中已过时。我建议您在jdk中更新tzdb,或者用更高版本替换整个jdk。无论哪种方式,您都可能看到错误消失。
顺便说一句,你应该试着逐步停止使用 DateCalendar 尽可能的上课。time类旨在完全替换遗留类。在必须的地方来回转换,以便与尚未更新为java.time的旧代码进行接口。但当你可以的时候,试着继续前进。那些旧课真的那么糟糕。

mrzz3bfm

mrzz3bfm2#

模拟localdatetime::now时出现问题。这将导致异常。我可以通过向now调用注入java.time.clock并在测试中返回固定时钟来解决模拟问题。

相关问题