WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


TPVE

TPVE0001W: AdminBridgeImpl has no ObjectName returned from query: {0}
Explanation There is no MBean that matches the ObjectName specified.
Action Try specifying a broader ObjectName pattern.
TPVE0002W: Updating the instrumentation level string failed.
Explanation The attempt to save the new instrumentation level string to the WebSphere Config Service failed.
Action Try the operation again. If it still fails, make sure your disk is not full.
TPVE0003W: No MBeans were found for the server {0} on node {1}
Explanation Finding all the ObjectName's on the specified server returned none.
Action Make sure the server specified has started and can respond to management commands.
TPVE0005W: The Server MBean for the node agent on the specified node {0} could not be found.
Explanation An attempt to get the Server MBean for a node failed.
Action You should make sure the node agent is running for the specified node.
TPVE0007W: Could not determine if {0} and {1} are the same host.
Explanation A hostname resolution problem occurred so the Collector will connect to the destination using the AdminClient.
Action None required. If the source and destination are the same host, performance can be improved by fixing the name resolution problem.
TPVE0008W: Could not determine if the destination of the Collector was the local JVM.
Explanation An error occurred trying to determine if the destination of the Collector was local to the current JVM. Defaulting to a not local scenario still works.
Action None required. The AdminClient will be used to communicate with the destination host since it could not be verified that the destination was the local host.
TPVE0009W: Could not get the PMIService config object for: server={0}; node={1}.
Explanation The PMIService config ObjectName could not be found by the config service.
Action Make sure you are connected to the Deployment Manager instead of to an Application Server.
TPVE0010W: DataCollector.getPMIService: Could not get the node for: server={0}; node={1}.
Explanation The node config ObjectName could not be found by the config service.
Action Make sure you are connected to the Deployment Manager instead of to an Application Server.
TPVE0011W: DataCollector.getPMIService: Could not get the server for: server={0}; node={1}.
Explanation The server config ObjectName could not be found by the config service.
Action Make sure you are connected to the Deployment Manager instead of to an Application Server.
TPVE0013W: No PerfMBean is found. Make sure PMI is enabled on the system: node={0}; server={1}.
Explanation The perf MBean could not be found for the server.
Action Make sure you enabled the PMI Service in the admin console and restarted the server.
TPVE0014E: An exception occurred getting a reference to the ConfigService. The DataCollector will not be fully functional.
Explanation The connection to the ConfigService failed. Attempts to access it by the Collector will fail. PMI data will still be available.
Action Make sure you are connected to the Deployment Manager instead of to an Application Server.
TPVE0015E: Unable to get the AdminClient for: node={0}; server={1}.
Explanation The AdminClient connection to the server specified could not be made.
Action Make sure the server specified is running. If it isn't: start it. If it is, check that there are operational JMXConnectors.
TPVE0016E: Connecting to Deployment Manager from within an Application Server is not supported.
Explanation The connection to the Deployment Manager is not being made because you are running in an App Server and that configuration is not supported.
Action Use the DataCollector from a client or directly in the Deployment Manager.
TPVE0017E: Unable to start the TivoliPerfEngine MBean
Explanation The MBean Factory failed to start the TivoliPerfEngine MBean needed by the Tivoli Performance Viewer.
Action Inspect the failure data that was generated due to this failure.
TPVE0018E: Unable to start the TivoliPerfAdvisor MBean
Explanation The MBean Factory failed to start the TivoliPerfAdvisor MBean needed by the Tivoli Performance Advisor.
Action Inspect the failure data that was generated due to this failure.
Reference topic    

Terms of Use | Feedback

Last updated: May 3, 2010 12:31:27 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.tpv.engine.property.tpvengine.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)