ZoneRulesException - running Gatling 2.0.0-RC6 through jenkins

Gatling (Open-Source)
1

I am running Gatling through Jenkins and seeing the following ERROR:

org.threeten.bp.zone.ZoneRulesException: Unknown time-zone ID: US/Pacific-New
	at org.threeten.bp.zone.ZoneRulesProvider.getProvider(ZoneRulesProvider.java:188)
	at org.threeten.bp.zone.ZoneRulesProvider.getRules(ZoneRulesProvider.java:143)
	at org.threeten.bp.ZoneRegion.ofId(ZoneRegion.java:143)
	at org.threeten.bp.ZoneId.of(ZoneId.java:357)
	at org.threeten.bp.ZoneId.of(ZoneId.java:285)
	at org.threeten.bp.ZoneId.systemDefault(ZoneId.java:244)
	at org.threeten.bp.Clock.systemDefaultZone(Clock.java:137)
	at org.threeten.bp.LocalDateTime.now(LocalDateTime.java:152)
	at io.gatling.core.result.writer.ConsoleSummary$.apply$default$6(ConsoleSummary.scala:44)
	at io.gatling.core.result.writer.ConsoleDataWriter.display(ConsoleDataWriter.scala:54)
	at io.gatling.core.result.writer.ConsoleDataWriter$$anonfun$initialized$1.applyOrElse(ConsoleDataWriter.scala:60)
	at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:166)
	at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
	at io.gatling.core.akka.BaseActor.aroundReceive(BaseActor.scala:23)
	at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
	at akka.actor.ActorCell.invoke(ActorCell.scala:487)
	at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
	at akka.dispatch.Mailbox.run(Mailbox.scala:220)
	at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393)
	at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
	at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
	at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
	at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)



tried with 2.0.0-RC5, 2.0.0-RC4 Errors become:
2

Wow, I learnt a very funny one here!

Please read this. Basically, US/Pacific-New is a ZoneId that shouldn’t exist. It was wrongly included in Java supported ZoneIds, but the new Java 8 DateTime API decided to drop this support.

Basically, the solution is to fix the ZoneId you’re using (change to something like America/Los-Angeles I guess).

3

Hi, Thank you for your reply. Sadly I don’t have control over setting the timezone to something else… the full Error message is:

[ERROR] [10/02/2014 13:54:27.109] [GatlingSystem-akka.actor.default-dispatcher-45] [akka://GatlingSystem/user/$+b] Unknown time-zone ID: US/Pacific-New
org.threeten.bp.zone.ZoneRulesException: Unknown time-zone ID: US/Pacific-New
	at org.threeten.bp.zone.ZoneRulesProvider.getProvider(ZoneRulesProvider.java:188)
	at org.threeten.bp.zone.ZoneRulesProvider.getRules(ZoneRulesProvider.java:143)
	at org.threeten.bp.ZoneRegion.ofId(ZoneRegion.java:143)
	at org.threeten.bp.ZoneId.of(ZoneId.java:357)
	at org.threeten.bp.ZoneId.of(ZoneId.java:285)
	at org.threeten.bp.ZoneId.systemDefault(ZoneId.java:244)
	at org.threeten.bp.Clock.systemDefaultZone(Clock.java:137)
	at org.threeten.bp.LocalDateTime.now(LocalDateTime.java:152)
	at io.gatling.core.result.writer.ConsoleSummary$.apply$default$6(ConsoleSummary.scala:44)
	at io.gatling.core.result.writer.ConsoleDataWriter.display(ConsoleDataWriter.scala:54)
	at io.gatling.core.result.writer.ConsoleDataWriter$$anonfun$initialized$1.applyOrElse(ConsoleDataWriter.scala:60)
	at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:166)
	at akka.actor.Actor$class.aroundReceive(Actor.scala:465)
	at io.gatling.core.akka.BaseActor.aroundReceive(BaseActor.scala:23)
	at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
	at akka.actor.ActorCell.invoke(ActorCell.scala:487)
	at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
	at akka.dispatch.Mailbox.run(Mailbox.scala:220)
	at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393)
	at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
	at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
	at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
	at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
4

You don’t get it: there’s nothing I can do about it!
This ZoneID was a failed attempt and should have never been used. Java 8 has dropped support for it, period!
This is not a Gatling issue, this is an issue on the platform you use.

If you can’t fix it yourself, you have the report/complain to your client/provider and get this fixed.

5

newer RHEL6 might have that Pacific-New under /usr/share/zoneinfo/US
you may just remove it and voila…

Stéphane Landelle於 2014年10月3日星期五UTC+8下午2時08分00秒寫道：

6

or check your /etc/sysconfig/clock
change your zone to UTC
looks like PDT might do that… picking up Pacific-New

Shao-Chieh Chiang於 2014年10月22日星期三UTC+8下午4時51分39秒寫道：