Table of Contents
Advertisement
LOGFILSIZ=1024
LOGPRIMARY=13
LOGSECOND=4
The amount of space required for the DB2 transaction log is dependent on a
number of factors, including the peak rate of documents being processed by
WebSphere Partner Gateway during a given time period. If you observe that
WebSphere Partner Gateway seems to quiesce while documents are still in the
queue, check the FFDC logs for the BCGMAS server. If you find that the BGMAS
server failed with error SQL 0964C, increase the size (LOGFILESIZ) and number
(LOGPRIMARY, LOGSECOND) of transaction logs for the BCGMAS database.
IBM service log unreadable
In previous releases of WebSphere Partner Gateway logs were viewable using a
text editor or the more command. In the current release, several of the logs are in a
binary format and cannot be read with a text editor or by using the more command
at the command line. If your service log output appears garbled when using either
of these methods, convert the service log from binary format into plain text by
issuing the showlog command from the workstation where the tool resides as
shown below.
showlog -format CBE-XML-1.0.1 filename
Where filename is the file name of the service log file. Note that if the service log is
not in the default directory you must fully qualify the service log file name.
This showlog command produces output in Common Base Event XML format. For
more examples of Showlog scripts, go to http://publib.boulder.ibm.com/
infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/
aes/ae/ttrb_viewsvclog.html.
WebSphere Application Server informational messages
Some WebSphere Application Server messages recorded as errors in WebSphere
Partner Gateway system output logs are actually informational in nature and not
indicative of a WebSphere Partner Gateway problem. For more information about
interpreting WebSphere Application Server log and trace messages, see
"Interpreting WebSphere Application Server log and trace messages" on page 146.
Increasing the Receiver timeout setting
About this task
If a partner opens a connection to WebSphere Partner Gateway and receives the
error message Connection aborted by peer: socket write error, the WebSphere
Partner Gateway Receiver is initiating a timeout because of the slow transmission
rate from the partner.
From the WebSphere Application Server admin console:
1. Navigate to Applications.
2. Select the WebSphere Partner Gateway Receiver component.
3. Select Web Container > Web Container Transport Chain.
4. Modify the timeout settings for the WebSphere Partner Gateway Receiver ports.
Chapter 17. Troubleshooting
163
Advertisement
Table of Contents
