Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-21469

Quick access 'open via livereload' with stopped application server is misbehaving

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.4.0.Alpha1
    • 4.3.1.Beta2
    • livereload
    • None

      Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.

      If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.

      It does however add this entry to the error log:

      Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
      org.eclipse.swt.SWTException: Invalid thread access
      	at org.eclipse.swt.SWT.error(SWT.java:4491)
      	at org.eclipse.swt.SWT.error(SWT.java:4406)
      	at org.eclipse.swt.SWT.error(SWT.java:4377)
      	at org.eclipse.swt.widgets.Display.error(Display.java:1186)
      	at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
      	at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
      	at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:180)
      	at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
      	at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
      	at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
      	at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
      	at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
      	at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
      	at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
      	at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
      	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
      

            xcoulon@redhat.com Xavier Coulon
            jrichter@redhat.com Jan Richter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: