org.eclipse.swt.SWTException

Failed to execute runnable (java.lang.NullPointerException)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1417

  • via Appcelerator JIRA by Ingo Muschenetz, 11 months ago
    Failed to execute runnable (java.lang.NullPointerException)
  • via Appcelerator JIRA by Joel Witt, 11 months ago
    Failed to execute runnable (java.lang.NullPointerException)
  • via Appcelerator JIRA by Joel Witt, 11 months ago
    Failed to execute runnable (java.lang.NullPointerException)
  • Stack trace

    • org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.SWT.error(Unknown Source) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source) at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) at org.pentaho.di.ui.spoon.Spoon.readAndDispatch(Spoon.java:1183) at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:6966) at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:567) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.pentaho.commons.launcher.Launcher.main(Launcher.java:134) Caused by: java.lang.NullPointerException at org.pentaho.di.core.logging.Log4jKettleLayout.format(Log4jKettleLayout.java:72) at org.pentaho.di.ui.spoon.trans.LogBrowser$1$1.run(LogBrowser.java:128) at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source) ... 11 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.