Thoughts and Tutorials about Continuous Integration, Application Integration, SOA, IT Architecture, WebSphere and Liferay

Oct 25, 2014

SOAP Exception while installing application to WebSphere with wsadmin

When deploying (larger) applications to WebSphere with wsadmin scripting some times a SOAP Exception occurs. This is due to a low default SOAP timeout. wsadmin uses internally SOAP to communicate with the WebSphere instance.

Exception message:
WASX7017E: Exception received while running file "<your-path>\";
exception information:
[wsadmin] Caused by: [SOAPException: faultCode=SOAP-ENV:Client;
msg=Read timed out;
Read timed out]

To increase the timeout locate the soap.client.props file of your locale and remote profile and set the to a higher value
# SOAP Request Timeout
# - timeout (specified in seconds [default 180], 0 implies no timeout)

How to activate access and error logs for WebSphere

Webservers typically provide so called access and error logs for diagnosting incomming http requests.
This logs are activated by default for Apache webserver and IBM HTTP Server.

Java EE application servers do have a web container that also serve http content. However the access and error logs are disabled by default for Websphere.

To active the access and error logs go to
Servers > Server types > WebSphere application servers > <your-server-name> > NCSA access and HTTP error logging

Select "Enable logging service at server start-up" and make sure that "Enable access logging" and "Enable error logging" are selected. Restart the server afterwards.

The NCSA access log format specifies which format is used when logging client information.
  • Common: The log entries contain the requested resource and other some http informations. Example log entry:
    0:0:0:0:0:0:0:1 - - [25/Oct/2014:10:41:08 +0200] "GET /wasPerfTool/dtd/ HTTP/1.1" 200 -
  • Combined: In addition to the common format, the log entries contains the referral, the user agent, and cookie.
    Example log entry:
    0:0:0:0:0:0:0:1 - - [25/Oct/2014:10:48:31 +0200] "GET /wasPerfTool/dtd/ HTTP/1.1" 200 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36" "-"
The error logging level simply defines the detail of the logged information.