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.
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 before 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.
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(); }
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 or in the profile_root/properties directory
for a network deployment installation. 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.
Look in the SystemOut.log file.
Look in the joblogs file.
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
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.