WebLogic Server Command Reference

VALIDATECLUSTERCONFIG

Parses the domain's configuration file and reports any errors in the configuration of cluster-related elements.

You can run this command only on a WebLogic Server host that can access the domain's configuration file through the host's file system.

Syntax

java [ SSL Arguments ] weblogic.Admin 
     [-url URL]
     [ User Credentials Arguments ]
   VALIDATECLUSTERCONFIG 
   -configPath pathname

Argument	Definition
{-url [`protocol://`]`listen-address:listen-port}`	Specify the listen address and listen port of any active server in the domain, regardless of whether it belongs to a cluster. If you specify a secure listen port, you must also specify a secure protocol. If you do not specify a value, the command assumes `t3://localhost:7001`. For more information, refer to the -url entry in Table 1-3 on page 11 and Protocol Support.
`-configPath` `pathname`	The path and file name of the domain's configuration file. A relative pathname is resolved to the directory in which you issue the VALIDATECLUSTERCONFIG command.

Argument

Definition

{-url [protocol://]listen-address:listen-port}

Specify the listen address and listen port of any active server in the domain, regardless of whether it belongs to a cluster.

If you specify a secure listen port, you must also specify a secure protocol.

If you do not specify a value, the command assumes t3://localhost:7001.

For more information, refer to the -url entry in Table 1-3 on page 11 and Protocol Support.

-configPath pathname

The path and file name of the domain's configuration file. A relative pathname is resolved to the directory in which you issue the VALIDATECLUSTERCONFIG command.

Example

The following example validates the cluster-related configuration elements for the MedRec domain. In this example, the command is issued from the WL_HOME directory:

java weblogic.Admin -url AdminHost:7001 
  -username weblogic -password weblogic 
  VALIDATECLUSTERCONFIG -configpath
  samples\domains\medrec\config.xml

For more information about the environment in which this example runs, refer to Example Environment.

If the cluster configuration contains errors, the command returns a message that describes the error. For example:
ERROR:Cluster name:MyCluster has an INVALID Multicast address:null Please pick an address between (224.0.0.1 and 255.255.255.255)

If the cluster configuration is free of errors, the command returns nothing.

Command for Purging Tasks

When the weblogic.Deployer tool is used to deploy or undeploy applications to WebLogic Server, DeploymentTaskRuntimeMBeans are created on the server side to handle each of these deployment tasks. These TaskRuntimeMBeans, created to execute deployment requests are not automatically purged after the completion of the deployment tasks. Instead, they are deleted only when they are manually purged from WebLogic Server Administration Console.

PURGETASKS

You can use the PURGETASKS command to purge DeploymentTaskRuntimeMBeans on the server side. Purging these tasks avoids any Deployer related memory leaks on the server-side.

Syntax

java [ SSL Arguments ] weblogic.Admin 
     [ Connection Arguments ] 
     [ User Credentials Arguments ]
PURGETASKS

Examples

The following example connects through a non-secured listen port.

java weblogic.Admin -url t3://localhost:7001 -username weblogic -password weblogic PURGETASKS

The following example connects through an SSL listen port on a server that is using the demonstration SSL keys and certificates.

java -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.Admin -url t3s://localhost:7002 -username weblogic -password weblogic PURGETASKS