Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 174309

Summary:	starting Muse client-proxy hangs - probably due to
Product:	z_Archived	Reporter:	Michael Moser <mmo>
Component:	TPTP.monitoring	Assignee:	Andrew Eberbach <aeberbac>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P1	CC:	aeberbac
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	closed460

Description Michael Moser

2007-02-15 09:47:20 EST

When starting a Muse client-proxy application I frequently get the below exception and apparently this also is the reason why the app-startup then hangs (falsely reporting that it is waiting for the server to start up, while the "Servers" view already reports the server (Tomcat 5.5) as "Started").

This is on Eclipse 3.3M4 with btm.wsdm-TPTP-4.4.0 extensions & muse 2.1.0.

--------------------
...
!ENTRY org.eclipse.core.resources 4 1 2007-02-15 15:32:55.863
!MESSAGE Internal Error
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: P/LocalWSDMResourcesProject, does not match outer scope rule: MultiRule[P/coma_test_server,Server scheduling rule for Tomcat v5.5 Server at localhost]
	at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
	at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:116)
	at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:225)
	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:80)
	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:219)
	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1690)
	at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1398)
	at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCoreUtil.createContainer(PDCoreUtil.java:192)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.provisional.actions.LaunchWSDMManagedAgentAction.run(LaunchWSDMManagedAgentAction.java:79)
	at org.eclipse.tptp.wsdm.tooling.internal.util.DeploymentListener.launch(DeploymentListener.java:77)
	at org.eclipse.tptp.wsdm.tooling.internal.util.DeploymentListener.serverChanged(DeploymentListener.java:49)
	at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:110)
	at org.eclipse.wst.server.core.internal.Server.fireRestartStateChangeEvent(Server.java:425)
	at org.eclipse.wst.server.core.internal.Server.setServerRestartState(Server.java:1315)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerRestartState(ServerBehaviourDelegate.java:168)
	at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.handleResourceChange(TomcatServerBehaviour.java:859)
	at org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(Server.java:194)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
--------------------

Michael

Comment 1 Bhanu Prathap V

2007-03-14 03:39:10 EDT

Unable to generate Client proxy, no error in the error log
Build: tptpaide-2007-03-09-05-00-00

Comment 2 Krishna Shastry C

2007-04-27 11:40:10 EDT

This problem no longer happening.

Comment 3 Balan Subramanian

2007-04-27 12:15:01 EDT

the problem cannot be reproduced anymore

Comment 4 Paul Slauenwhite

2009-06-30 12:14:28 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.