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

Bug 173635

Summary: Could not connect MAX when started Eclipse with IBMJava142
Product: z_Archived Reporter: Bhanu Prathap V <bhanu.prathap>
Component: TPTP.monitoringAssignee: Balan Subramanian <bsubram>
Status: CLOSED FIXED QA Contact: Bhanu Prathap V <bhanu.prathap>
Severity: major    
Priority: P1 CC: bhanu.prathap, bsubram
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Changes to manifest file to explicitly include xml parsing classes from xerces none

Description Bhanu Prathap V CLA 2007-02-09 08:31:03 EST
Steps To Reproduce:
1.Started Eclipse with IBMJava142
2.Created new default MRT with capabilities like Identity, ManageabilityCharacteristics,MatadataExchange, Get, Set, Query   
3. Using the MRT file, Generated Code Successfully 
4. and deployed in Tomcat and when trying to connect Deployed endpoint using Managed agent below error throws up

Candidate Build: TPTP-4.4.0-200702050100
WTP: wtp-I-I200702011746-200702011746
Java_version: build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20060824 (SR6)


java.lang.Exception: [ID = 'PropertyNotInSchema'] There is no property named '{http://docs.oasis-open.org/wsdm/muws2-2.xsd}Relationship' defined in the schema. A property should not have any operations or metadata applied to it if it is not in the WS-RP document.org.apache.muse.ws.addressing.soap.SoapFault: [ID = 'PropertyNotInSchema'] There is no property named '{http://docs.oasis-open.org/wsdm/muws2-2.xsd}Relationship' defined in the schema. A property should not have any operations or metadata applied to it if it is not in the WS-RP document.
	at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254)
	at org.apache.muse.ws.resource.remote.WsResourceClient.getResourceProperty(WsResourceClient.java:134)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.internal.muse.RelationshipsHelper.getRelationships(RelationshipsHelper.java:34)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.internal.muse.MuseRuntime.getRelationships(MuseRuntime.java:159)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.provisional.agents.WSDMAgent.getRelationships(WSDMAgent.java:134)
	at org.eclipse.tptp.monitoring.managedagent.provisional.ManagedResourceAgent.invokeCustomCommand(ManagedResourceAgent.java:432)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.execute(ManagedAgentCommandHelper.java:582)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.execute(ManagedAgentCommandHelper.java:610)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.getRelationships(ManagedAgentCommandHelper.java:491)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.getMetaData(ManagedAgentCommandHelper.java:222)
	at org.eclipse.tptp.monitoring.managedagent.ui.launch.provisional.common.ManagedAgentDelegate.createAgent(ManagedAgentDelegate.java:102)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.provisional.actions.LaunchWSDMManagedAgentAction.run(LaunchWSDMManagedAgentAction.java:87)
	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.fireServerStateChangeEvent(Server.java:439)
	at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:376)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:145)
	at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.setServerStarted(TomcatServerBehaviour.java:183)
	at org.eclipse.jst.server.tomcat.core.internal.PingThread.ping(PingThread.java:93)
	at org.eclipse.jst.server.tomcat.core.internal.PingThread$1.run(PingThread.java:53)

	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.error(ManagedAgentCommandHelper.java:654)
	at org.eclipse.tptp.monitoring.managedagent.provisional.ManagedResourceAgent.throwException(ManagedResourceAgent.java:319)
	at org.eclipse.tptp.monitoring.managedagent.provisional.ManagedResourceAgent.invokeCustomCommand(ManagedResourceAgent.java:441)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.execute(ManagedAgentCommandHelper.java:582)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.execute(ManagedAgentCommandHelper.java:610)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.getRelationships(ManagedAgentCommandHelper.java:491)
	at org.eclipse.tptp.monitoring.managedagent.provisional.helper.ManagedAgentCommandHelper.getMetaData(ManagedAgentCommandHelper.java:222)
	at org.eclipse.tptp.monitoring.managedagent.ui.launch.provisional.common.ManagedAgentDelegate.createAgent(ManagedAgentDelegate.java:102)
	at org.eclipse.tptp.monitoring.managedagent.wsdm.provisional.actions.LaunchWSDMManagedAgentAction.run(LaunchWSDMManagedAgentAction.java:87)
	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.fireServerStateChangeEvent(Server.java:439)
	at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:376)
	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:145)
	at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.setServerStarted(TomcatServerBehaviour.java:183)
	at org.eclipse.jst.server.tomcat.core.internal.PingThread.ping(PingThread.java:93)
	at org.eclipse.jst.server.tomcat.core.internal.PingThread$1.run(PingThread.java:53)


An exception stack trace is not available.


More information:
Comment 1 Balan Subramanian CLA 2007-02-13 21:48:39 EST
Where does this error manifest itself - inthe Eclipse error log or the tomcat console?
Comment 2 Bhanu Prathap V CLA 2007-02-14 00:34:00 EST
Its in the error log
Comment 3 Bhanu Prathap V CLA 2007-02-14 00:34:27 EST
its in the eclipse error log
Comment 4 Balan Subramanian CLA 2007-02-14 23:09:25 EST
*** Bug 173634 has been marked as a duplicate of this bug. ***
Comment 5 Balan Subramanian CLA 2007-02-16 15:31:28 EST
Created attachment 59196 [details]
Changes to manifest file to explicitly include xml parsing classes from xerces
Comment 6 Balan Subramanian CLA 2007-02-16 16:01:43 EST
the primary problem has been fixed. the secondary problem needs to be investigated (why it is looking for relationship property etc.)
Comment 7 Balan Subramanian CLA 2007-02-16 16:01:58 EST
the primary problem has been fixed. the secondary problem needs to be investigated (why it is looking for relationship property etc.)
Comment 8 Valentina Popescu CLA 2007-03-14 23:05:05 EDT
Please update target; i1 is already closed
Comment 9 Balan Subramanian CLA 2007-03-29 23:07:09 EDT
QA, Please verify
Comment 10 Bhanu Prathap V CLA 2007-03-31 06:08:10 EDT
Verified - fixed
TPTP-4.4.0-200703300100
Comment 11 Balan Subramanian CLA 2007-04-17 10:04:39 EDT
verified by qa
Comment 12 Bhanu Prathap V CLA 2007-04-19 08:28:59 EDT
Verified - closed
tptpaide-2007-04-16-16-40-18