Administration and administrative console troubleshooting
Review the list of solutions for administrative console problems.
- The application server (such as server1) process
The process must be running to use the administrative console. The wsadmin command-line utility has a local mode that you can use to perform some administrative functions, even when the server process is not running.
- Server status and messages in the console view are not current
- Role-based authorization fails
- When starting or stopping a server using a wsadmin interactive scripting session, you receive an exception indicating read timed out
- Problems starting or using the administrative console or wsadmin utility
- The AdminConfig.parents method cannot be used to obtain the valid parent types of some configuration types
Server status and messages in the console view are not current
- Under the status column in the Servers view on an administrative console panel, the status of the server does not refresh.
- Server messages are not updated in the administrative console.
- A decrease of system resources occurs as numerous ports are created and remain in the TIME_WAIT state.
The problem occurs because the SOAP connector does not support connection pooling. If the Application Server has many ongoing operations that use the SOAP connector, the Application Server quickly opens and closes many ports. Due to the nature of the underlying TCP/IP protocol, these ports remain in the TIME_WAIT state for some time prior to the operating system can reclaim them. The number of ports that WebSphere Application Server opens can exceed the limit that the operating system imposes. Under this condition, the opening of additional ports fails through the SOAP connector until the operating system reclaims ports.
- Increase the operating system limits on the number of ports.
- For Rational® Application Developer, the wsadmin utility, or Java™ applications that use the Java Management Extension (JMX) connectors, switch to the Remote Method Invocation (RMI) connector.
- Wait until few or no ports are in the TIME_WAIT state prior to performing new operations through Rational Application Developer or the administrative console.
Role-based authorization fails
SECJ0305I: Role based authorization check failed for securityname server.domain.name:3890/user.id, accessId user:server.domain.name:3890/uid=user.id,ou=xxxx,dc=yyy,dc=zzz while invoking method getNodeName on resource Server and module Server.If the caller of the application cannot be assigned one of the administrative roles, the application can log in with one of the roles on behalf of the caller. For example:
try
{
// Create a LoginContext to authenticate a user ID and password.
javax.security.auth.login.LoginContext
lc = new javax.security.auth.login.LoginContext(WSLogin
,
new com.ibm.websphere.security.auth.callback.WSCallbackHandlerImpl(adminuser
,
adminpassword
));
// perform the login
lc.login();
// Get the authenticated subject.
javax.security.auth.Subject adminSubject = lc.getSubject();
// Define the action that will take place using the authenticated Subject
// You can define this action anywhere in the code, the action
// is reference in the WSSubject.doAs that follows.
java.security.PrivilegedAction adminAction = new java.security.PrivilegedAction()
{
public Object run()
{
try
{
// Get the WebSphere AdminService.
AdminService adminservice = AdminServiceFactory.getAdminService();
// Get the WebSphere Admin Local Server MBean instance.
ObjectName objectname = adminservice.getLocalServer();
// Get the Node name.
String nodeName = (String)adminservice.getAttribute(objectname, nodeName
);
// Get the Application Server name.
String serverName = (String)adminservice.getAttribute(objectname, name
);
// Get the Application Server Process ID.
String serverPid = (String)adminservice.getAttribute(objectname, pid
);
// Return a result, for this example, just return the serverPid.
return serverPid;
}
catch (Exception e)
{
e.printStackTrace();
}
return null;
}
});
// Invoke an AdminClient resource using the authenticated subject.
// This example demonstrates the action of creating an
// administrative client and returning a String value to use outside
// the doAs block.
String myData = (String)
com.ibm.websphere.security.auth.WSSubject.doAs(adminSubject, adminAction);
// use myData
later on....
}
catch (javax.security.auth.login.LoginException e)
{
e.printStackTrace();
}
When starting or stopping a server using a wsadmin interactive scripting session, you receive an exception indicating read timed out
WASX7015E: Exception running command: "$AdminControl startServer server1 Node1;" exception information: com.ibm.websphere.management.exception.ConnectorException org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]
This exception occurs because the timeout value is too small. Increase the timeout value specified by the com.ibm.SOAP.requestTimeout property in the soap.client.props file in the profile_root/properties directory for a single server edition. The value you choose depends on a number of factors such as the size and the number of the applications installed on the server, the speed of your machine, and the level of usage of your machine. The default value of the com.ibm.SOAP.requestTimeout property is 180 seconds.
This exception occurs because the timeout value is too small. To fix this, increase the timeout value specified by the com.ibm.SOAP.requestTimeout property in the soap.client.props file in the profile_root/properties directory for a single server edition. The value you should choose depends on a number of factors such as the size and the number of the applications installed on the server, the speed of your machine, and the level of usage of your machine. The default value of the com.ibm.SOAP.requestTimeout property is 180 seconds.
Problems starting or using the administrative console or wsadmin utility
- For the application server process, refer to the following files:
- profile_root/logs/server_name/startServer.log for the message that indicates that the
server started successfully:
ADMU3000I: Server server1 open for e-business; process id is nnnn.
. - profile_root/logs/server_name/startServer.log for the message that indicates that the
server started successfully:
ADMU3000I: Server server1 open for e-business; process id is nnnn.
. - profile_root/logs/server_name/SystemOut.log
- profile_root/logs/server_name/SystemOut.log
- profile_root/logs/server_name/startServer.log for the message that indicates that the
server started successfully:
- Look up any error messages in these files in the message reference table. Select the
Reference
view in the documentation navigation, and clickMessages
. A message likeWASX7213I: This scripting client is not connected to a server process
when trying to start wsadmin indicates that either the server process is not running, the host machine where it is running is not accessible, or that the port or server name that the wsadmin utility uses is incorrect. - Verify that you are using the correct port number to communicate with the administrative console
or the wsadmin server:
-
Look in the SystemOut.log file.
- The line
ADMC0013I: SOAP connector available at port nnnn
indicates the port that the server is using to listen for wsadmin functions. - The com.ibm.ws.scripting.port property in the profile_root/properties/wsadmin.properties file controls the port used by the wsadmin utility to send requests to the server.
- The com.ibm.ws.scripting.port property in the profile_root/properties/wsadmin.properties file controls the port used by the wsadmin utility to send requests to the server.
- The line
- If port value is different from the value shown in the
SystemOut.log file, either change the port number in the
wsadmin.properties file, or specify the correct port number when starting the
wsadmin utility by using the -port port_number property on the command
line.
The com.ibm.ws.scripting.port property in the profile_root/properties/wsadmin.properties file controls the port used by the wsadmin utility to send requests to the server.
- If the port value is different from the value shown in the
SystemOut.log file, either change the port number in the
wsadmin.properties file, or specify the correct port number when starting the
wsadmin utility by using the -port port_number property on the command
line.
The com.ibm.ws.scripting.port property in the profile_root/properties/wsadmin.properties file controls the port used by the wsadmin utility to send requests to the server.
- If the port value is different from the value shown in the server log files,
either change the port number in the wsadmin.properties file, or specify the
correct port number when starting the wsadmin utility by using the -port
port_number property on the command line.
The message
SRVE0171I: Transport http is listening on port nnnn (default 9060)
indicates the port that the server uses to listen for administrative console requests. - If the port value is different than the one specified in the web address for the administrative console, change the web address in the browser to the correct value. The default value is http://localhost:9060/ibm/console.
-
- Use the telnet command to test that the host name where the application server is running, is reachable from the system where the browser or wsadmin program is used. If you can ping the host name, no firewall or connectivity issues exist.
- If the host where the application server is running is remote to the machine from which the client browser or wsadmin command is
running, ensure that the appropriate host name parameter is correct. Verify:
- The host name in the browser web address for the console.
- The -host host name option of the wsadmin command that is used to direct the wsadmin utility to the correct server.
-
WebSphere Application Server technical support might ask you to trace the
administrative component for detailed problem determination. The trace specification for this
component is
com.ibm.websphere.management.*=all=enabled:com.ibm.ws.management.*=all=enabled"
The AdminConfig.parents method cannot be used to obtain the valid parent types of some configuration types
AdminConfig.parents
method to obtain the allowed parent types for
a specific configuration type, for example, JavaVirtualMachine, an informational message may be returned instead of the desired value.
wsadmin>print AdminConfig.parents( "JavaVirtualMachine")
The following
informational message is
returned:WASX7351I: The parents command cannot be used to find the parents of type "JavaVirtualMachine"
AdminConfig.parents()
method that deals with the issue previously
mentioned:#---------------------------------------------------------------------
# Name: parentTypes()
# Role: To search for configuration types that may contain objects of
# the specified type should the result of calling
# AdminConfig.parents( Type )
# be:
# WASX7351I: The parents command cannot be used to find the parents of type ...
# Note: Unlike the AdminConfig.list() command, this routine will not
# raise an InvalidConfigDataTypeException for an unknow datatype
#---------------------------------------------------------------------
def parentTypes( Type ) :
import os
WSAStypes = AdminConfig.types().splitlines()
if Type in WSAStypes :
result = AdminConfig.parents( Type )
if result.startswith( 'WASX7351I' ) :
result = []
for thisType in WSAStypes :
if AdminConfig.attributes( thisType ).find( Type ) > -1 :
result.append( thisType )
result = (os.linesep).join( result )
else :
print 'parentTypes error: unknown / unrecognized type:', Type
result = None
return result
If none of these steps solves the problem, see if the specific problem you are having is addressed in the Installation completes but the administrative console does not start topic. Check to see if the problem has been identified and documented using the links in the Diagnosing and fixing problems: Resources for learning topic. If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
If none of these steps solves the problem, see if the specific problem you are having is addressed in the Installation completes but the administrative console does not start topic. Check to see if the problem is identified and documented using the links in the Diagnosing and fixing problems: Resources for learning topic.