Skip to content
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.

IllegalArgumentException parsing date #618

Closed
nirvdrum opened this issue Feb 13, 2014 · 4 comments
Closed

IllegalArgumentException parsing date #618

nirvdrum opened this issue Feb 13, 2014 · 4 comments
Milestone

Comments

@nirvdrum
Copy link

I just upgraded to RC2. When I issue a simple query (just clicking the search button with the default of "last 5 minutes"), I get an exception:

! @6h91km26b - Internal server error, for (GET) [/search?rangetype=relative&relative=300&from=&to=&q=] ->

play.api.Application$$anon$1: Execution exception[[IllegalArgumentException: Invalid format: "2014-02-13 10:17:45.000" is malformed at " 10:17:45.000"]]
        at play.api.Application$class.handleError(Application.scala:293) ~[com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1]
        at play.api.DefaultApplication.handleError(Application.scala:399) [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1]
        at play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2$$anonfun$applyOrElse$3.apply(PlayDefaultUpstreamHandler.scala:261) [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1]
        at play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2$$anonfun$applyOrElse$3.apply(PlayDefaultUpstreamHandler.scala:261) [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1]
        at scala.Option.map(Option.scala:145) [org.scala-lang.scala-library-2.10.3.jar:na]
        at play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$2.applyOrElse(PlayDefaultUpstreamHandler.scala:261) [com.typesafe.play.play_2.10-2.2.2-RC1.jar:2.2.2-RC1]
Caused by: java.lang.IllegalArgumentException: Invalid format: "2014-02-13 10:17:45.000" is malformed at " 10:17:45.000"
        at org.joda.time.format.DateTimeFormatter.parseMillis(DateTimeFormatter.java:752) ~[joda-time.joda-time-2.2.jar:2.2]
        at org.joda.time.convert.StringConverter.getInstantMillis(StringConverter.java:65) ~[joda-time.joda-time-2.2.jar:2.2]
        at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:150) ~[joda-time.joda-time-2.2.jar:2.2]
        at org.joda.time.DateTime.<init>(DateTime.java:265) ~[joda-time.joda-time-2.2.jar:2.2]
        at models.api.responses.MessageSummaryResponse.getTimestamp(MessageSummaryResponse.java:33) ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.2.jar:0.20.0-rc.2]
        at views.html.search.results$$anonfun$apply$2.apply(results.template.scala:386) ~[graylog2-web-interface.graylog2-web-interface-0.20.0-rc.2.jar:0.20.0-rc.2]
@nirvdrum
Copy link
Author

This looks similar to #614, but I'm using the default time range and it blows up with Chrome as well.

@lennartkoopmann lennartkoopmann modified the milestones: 0.20.0-rc.3, 0.20.0 Feb 13, 2014
@nirvdrum
Copy link
Author

I'm still seeing this with 0.20.0 RC3.

@nirvdrum
Copy link
Author

Actually, it looks like somehow I was still loading an RC1 server. I guess the init script didn't update. Forcing it to be RC3 worked.

@lennartkoopmann
Copy link
Contributor

Great - Thanks for updating us! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants