[jbosstools-issues] [JBoss JIRA] (JBIDE-22353) TimeoutException in JettyServerRunner.start
Automated Error Reporting Bot (JIRA)
issues at jboss.org
Wed May 11 04:58:00 EDT 2016
Automated Error Reporting Bot created JBIDE-22353:
-----------------------------------------------------
Summary: TimeoutException in JettyServerRunner.start
Key: JBIDE-22353
URL: https://issues.jboss.org/browse/JBIDE-22353
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: Failed to create or start LiveReload proxy for server wildfly at OpenShift 3 (10.1.2.2)
{noformat}
java.util.concurrent.TimeoutException: Failed to start Proxy Server (50347 -> 80) within expected time (reason: timeout)
at org.jboss.tools.livereload.core.internal.server.jetty.JettyServerRunner.start(JettyServerRunner.java:72)
at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.startProxy(LiveReloadServerBehaviour.java:344)
at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.inform(LiveReloadServerBehaviour.java:304)
at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:58)
at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.serverChanged(ServerLifeCycleListener.java:120)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:745)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:653)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
at org.jboss.tools.openshift.core.server.OpenShiftServerBehaviour.setServerStarted(OpenShiftServerBehaviour.java:38)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.checkServerState(OpenShiftLaunchController.java:143)
at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:113)
at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
Bundles:
| org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 |
| org.eclipse.debug.core | 3.10.100.v20160203-1134 | 3.10.100.v20160203-1134 |
| org.eclipse.wst.server.core | 1.8.100.v201603031514 | 1.8.100.v201603031514 |
| org.jboss.ide.eclipse.as.wtp.core | 3.2.0.Alpha1-v20160505-0626-B966 | 3.2.0.Alpha1-v20160505-0626-B966 |
| org.jboss.tools.livereload.core | 1.4.0.Alpha1-v20160401-2041-B449 | 1.4.0.Alpha1-v20160401-2041-B449 |
| org.jboss.tools.openshift.core | 3.2.0.qualifier | 3.2.0.qualifier |
Operating Systems:
| MacOSX | 10.10.5 | 10.10.5 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572cf573e4b0a54983279393] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list