Troubleshoot wsadmin.sh

 

 

General debugging tips

  1. Browse $WAS_HOME/logs/wsadmin.traceout for clues.

  2. Keep in mind that wsadmin.traceout is refreshed (existing log records are deleted) whenever a new wsadmin session is started.

  3. If the error returned by wsadmin does not seem to apply to the command you entered, for example, you receive WASX7023E, stating that a connection could not be created to host "myhost," but you did not specify "-host myhost" on the command line, examine the properties files used by wsadmin to determine what properties are specified. If you do not know what properties files were loaded, look for the WASX7326I messages in the wsadmin.traceout file; there will be one of these messages for each properties file loaded.

  4. Review the Tcl command language.

 

"WASX7023E: Error creating "SOAP" connection to host"

Verify an appserver is running, and if not, start one. If you are running a Network Deployment configuration, run...

$WAS_HOME/bin/startManager.sh

...then start an appserver from the console

If an appserver is running and you still get this error...

 

"com.ibm.bsf.BSFException: error while eval'ing Jacl expression: no such method command name in class com.ibm.ws.scripting.AdminConfigClient"

This error is usually caused by a misspelled command name. Note that command names are case-sensitive.

 

WASX7022E: Invalid command

On Unix, using wsadmin -c to invoke a command that includes dollar signs results in the shell attempting to do variable substitution. To confirm that this is the problem, check the command to see if it contains an unescaped dollar sign, for example:

wsadmin -c "$AdminApp install ....".

To correct this problem, escape the dollar sign with a backslash. For example:

wsadmin -c "\$AdminApp install ..."

 

com.ibm.ws.scripting.ScriptingException: WASX7025E: String "" is malformed; cannot create ObjectName

One possible cause of this error is that an empty string was specified for an object name. This can happen if you use one scripting statement to create an object name and the next statement to use that name, perhaps in an "invoke" or "getAttribute" command, but you don't check to see if the first statement really returned an object name.

To correct this error, make sure that object name strings have values before using them. For example

set serverName[$AdminControl queryNames type=Server,*] 

if {$serverName == ""} 
{
    puts "queryNames returned empty - check query argument"
} 
else 
{
    $AdminControl getAttributes $serverName
} 

 

WASX7017E: Exception received while running file "xyz.jacl";

exception information: com.ibm.websphere.management.exception.ConfigServiceException
javax.management.RuntimeMBeanException
java.lang.NullPointerException: java.lang.NullPointerException

To fix, try recycling the deployment manager.