WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Problems starting or using the wsadmin command

What kind of problem are you having?
If you do not see your problem here:

If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If you don't find your problem listed there contact IBM support.

"WASX7023E: Error creating "SOAP" connection to host" or similar error trying to launch wsadmin command line utility

By default, the wsadmin utility attempts to connect to an application server at startup. This is because some commands act upon running application servers. This error indicates that no connection could be established.

To resolve this problem:
  • If you are not sure whether an application server is running, start it by entering startserver servername from the command prompt. If the server is already running, you will see an error similar to "ADMU3027E: An instance of the server is already running".
  • If you are running a Network Deployment configuration, you will first need to start the deployment manager by running "startManager" or "startManager.sh" from the install_dir/bin directory. Then you can launch wsadmin immediately to connect to the deployment manager, or start a node and application server to connect to.
  • If an application server is running and you still get this error:
    • If you are running remotely (that is, on a different machine from the one running WebSphere Application Server), you must use the -host hostname option to the wsadmin command to direct wsadmin to the right physical server.
    • If you are using the -host option, try pinging the server machine from the command line from the machine on which you are trying to launch wsadmin to verify there are no issues of connectivity such as firewalls.
    • verify that you are using the right port number to connect to the WebSphere Application Server process:
      • If you are not specifying a port number (using the -port option) when you start the wsadmin tool, the wsadmin tool uses the default port specified in install_dir/profiles/profile_name/properties/wsadmin.properties file, property name=com.ibm.ws.scripting.port (default value =8879).
      • The port that wsadmin should send on depends on the server process wsadmin is trying to connect to.

        For a single-server installation, wsadmin attempts to connect to the application server process by default. To verify the port number:
        • Look in the file install_dir/profiles/profile_name/config/cells/node_name/nodes/node_name/serverindex.html for a tag containing the property serverType="APPLICATION_SERVER".
        • Look for an entry within that tag with the property endPointName="SOAP_CONNECTOR_ADDRESS".
        • Look for a port property within that tag. This is the port wsadmin should send on.
        In a Network Deployment installation, wsadmin launched from the bin directory on the Network Deployment installation attempts to send requests to the deployment manager by default. To verify the port number:
        • Get the hostname of the node on which the Deployment Manager is installed.
        • Using that hostname, look in install_dir/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.html file for a tag containing the property serverType="DEPLOYMENT_MANAGER".
        • Within that tag, look for an entry with a property endPointName="SOAP_CONNECTOR_ADDRESS".
        • Within that tag, look for a "port" property. This is the port that the wsadmin tool should send on.

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

This error is usually caused by a misspelled command name. Use the $AdminConfig help command to get information about what commands are available. Note that command names are case-sensitive.

WASX7022E returned from running "wsadmin -c ..." command, indicating invalid command

If the command following -c appears to be valid, the problem may be caused by the fact that 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. For example (the following samples use basic Jacl commands in addition to the wsadmin Jacl extensions to make a sample script):
#let's misspell "Server" 
set serverName [$AdminControl queryNames type=Srever,*] 
$AdminControl getAttributes $serverName 
To correct this error, make sure that object name strings have values before using them. For example:
set serverName[$AdminControl queryNames node=mynode,type=Server,name=server1,*]
if {$serverName == ""} {puts "queryNames returned empty - check query argument"} 
else {$AdminControl getAttributes $serverName} 

For details on Jacl syntax beyond wsadmin commands, refer to the Tcl developers' site, http://www.tcl.tk.

"The input line is too long" error returned from the wsadmin command on a Windows platform

This error indicates that the Windows command line limit of 2048 characters has been exceeded, probably due to a long profile path used within the wsadmin.bat command. You may get this error when running wsadmin in a Windows command prompt or calling wsadmin from a .bat file, an ant build file, or Profile Creation Tool. If this error results in running wsadmin in a way other than from the Profile Creation Tool, you can avoid the problem by using the Windows subst command which allows you to map an entire path to a virtual drive. To see the syntax of the subst command, enter help subst from a Windows command prompt.

For example if the product resides in the c:\Program Files\IBM\WebSphere\AppServer directory, edit the c:\Program Files\IBM\WebSphere\AppServer\bin\setupCmdLine.bat file. For example:
SET CUR_DIR=%cd%
cd /d "%~dp0.."
SET WAS_HOME=%cd%
cd /d "%CUR_DIR%"

@REM add the following two lines to workaround Windows 2K command line length limit
subst w: %WAS_HOME%
set WAS_HOME=w:

...
...
Then edit the setupCmdLine.bat file which resides in the bin directory of your profile. For example:
SET WAS_USER_PROFILE=...
SET USER_INSTALL_ROOT=...
SET WAS_HOME=c:\Program Files\IBM\WebSphere\AppServer
SET JAVA_HOME=c:\Program Files\IBM\WebSphere\AppServer\java

@REM add the following three lines to workaround Windows 2K command line length limit
subst w: %WAS_HOME%
set WAS_HOME=w:
set JAVA_HOME=%WAS_HOME%\java

...
...

If this error occurred while running the Profile Creation Tool, you have to rerun the Profile Creation Tool to provide a shorter profile path with a shorter profile name. If this does not fix the problem, then you have to follow the same instruction given above to edit the setupCmdLine.bat file resided in the bin directory of your WebSphere install. After editing the file, rerun Profile Creation Tool. If the same problem persists, then you may have to reinstall WebSphere with a shorter install path.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.

WASX701E: Exception received while running file "scriptName.jacl"; exception information: com.ibm.bsf.BSFException: error while evaluating Jacl expression: missing close-bracket

This error is caused by a mix-up between the code page that the scripting client expects to see and the code page in which the Jacl script was written.

To fix this problem, set the -Dscript.encoding=script codepage option in the wsadmin.sh or wsadmin.bat file to the code page of the Jacl script. The following guideline will help you to determine the code page of the script:
  • If the script was written in the OMVS interface using the OEDIT editor, the code page is IBM-037. In this case, set the option to the following: -Dscript.encoding=Cp037
  • If the script was written in a telnet session to the OMVS interface using the VI editor, the code page is IBM-1047. In this case, set the option to the following: -Dscript.encoding=Cp1047
  • IF the script was written on a personal computer, or any other ASCII machine, and was transferred to the host as a text file, the code page is IBM-1047. In this case, set the option to the following: -Dscript.encoding=Cp1047
  • If the script was written on a personal computer, or any other ASCII machine, and transferred to the host in binary format, the code page is ISO-8859-1 (ASCII). In this case, you do not need to set the option because the default is ASCII. You should review other possible reasons for this error.



Related tasks
Troubleshooting by task
Troubleshooting by component

Reference topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_wsadminprobs.html

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