Re: Webfacing Server connection Socket closed

["Jerry Thomas" <jerryt@xxxxxxxxxxx>]

I am assuming you have started the webfacing server on the i5. 

STRTCPSVR SERVER(*WEBFACING)

Jerry Thomas

-----Original Message-----
From: wdsci-l-bounces+jerryt=ccslink.com@xxxxxxxxxxxx
[mailto:wdsci-l-bounces+jerryt=ccslink.com@xxxxxxxxxxxx] On Behalf Of
rstearns@xxxxxxxxxxxxx
Sent: Thursday, June 07, 2007 10:52 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Webfacing Server connection Socket closed

Problem
We have built a webfaced application, installed it on WAS and started the 
app.  After launching the application and entering a logon and password, 
the app server attempts to connect to the WF server -http://local 
IP:10016/AM/WFInvocation.do  and then the error occurs.
We assumed it was the Webfacing server, checking PTF's, making sure the 
port was open, etc. and can not identify the problem. 

NETSTAT  indicates the WF server is never touched when the application 
tries to connect 

However, if we URL to  http://99.99.99.99:4004   or  http://local IP:4004
NETSTAT indicates that the WF server is listening and shows a hit on the 
server

Question:
How do I troubleshoot the connection between the Websphere app server and 
the Webfacing server?

Information:
V5R4
WAS V6.1
WF Server  BUILD VERSION 200601261300   and  PTF's applied
WF server is running
QQFVTSVR     QUSER       BCI      .0  PGM-QQFVTSVR     DEQW 
QQFWFSVR     QUSER       BCI      .0  PGM-QQFWFSVR     TIMW 
*netstat:
Connection type  . . . . . . :   *TCP 
Local address  . . . . . . . :   * 
Local port . . . . . . . . . :   4004 
Remote address . . . . . . . :   * 
Remote port  . . . . . . . . :   * 
Opt  Name        User        Number 
     QQFWFSVR    QUSER       313997 

ERROR
WF0103: An error occurred while establishing connection with the WebFacing 
server on the host.
     WFC056: While connecting to host 99.99.99.99 on port 4004 the 
following exception was thrown: 'java.net.SocketException: Socket closed'. 

Possible causes: The WebFacing server may be down, or the TCP port 4004, 
specified by the web application, is not configured and assigned to 
WebFacing TCP services on host 99.99.99.99.
Details : 
com.ibm.etools.iseries.webfacing.runtime.host.core.WFConnectionException: 
WFC056: While connecting to host 99.99.99.99 on port 4004 the following 
exception was thrown: 'java.net.SocketException: Socket closed'. 
Possible causes: The WebFacing server may be down, or the TCP port 4004, 
specified by the web application, is not configured and assigned to 
WebFacing TCP services on host 99.99.99.99.