[jbosstools-issues] [JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup
[
https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin....
]
Rob Stryker commented on JBDS-4095:
-----------------------------------
It was thought we could find a way to not read logs and make this less error prone.
tl;dr: there isn't, really.
http://eclipsesource.com/blogs/2013/01/23/how-to-track-lifecycle-changes-...
i can file for events after my plugin is started, but most errors will occur during
resolution (which is before my checkup bundle is started). Only way to get around that is
to use BundleWatcher, which requires vm props / config.ini changes to be installed when
osgi is first starting up... and so is not suitable for JBT.
so i guess we're stuck with reading logs ;)
unparseable date in o.j.t.foundation.checkup
--------------------------------------------
Key: JBDS-4095
URL: https://issues.jboss.org/browse/JBDS-4095
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: foundation
Affects Versions: 10.2.0.AM1
Environment: {code}
Red Hat JBoss Developer Studio
Version: 10.2.0.AM1
Build id: AM1-v20160923-1714-B6096
Build date: 20160923-1714
$➔ uname -a
Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
[14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1
$➔ java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}
Reporter: Nick Boldt
Assignee: Rob Stryker
Fix For: 10.2.0.AM2
Attachments: unparesable-date.png
Just started up devstudio 10.2.0.AM1-v20160923-1714-B6096 and got this error:
{code}
Unparseable date: "Thu Oct 06 13:55:38 EDT 2016"
java.text.ParseException: Unparseable date: "Thu Oct 06 13:55:38 EDT 2016"
at java.text.DateFormat.parse(DateFormat.java:366)
at
org.jboss.tools.foundation.checkup.JVMProblemDetector.getSessionDate(JVMProblemDetector.java:677)
at
org.jboss.tools.foundation.checkup.JVMProblemDetector.scanLine(JVMProblemDetector.java:240)
at
org.jboss.tools.foundation.checkup.JVMProblemDetector.readLogFile(JVMProblemDetector.java:186)
at
org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:118)
at
org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:77)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:53)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2829)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)