This application has been eared up and installed on WAS V6.1 on the same 
machine that the WF server is running on so there are no firewalls between 
the servers.
i5
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 
Royce Stearns
Manage, Inc.
(503) 353-1721 x103
www.manageinc.com
Mike Hockings <hockings@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/07/2007 09:45 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] Webfacing Server connection Socket closed
It is likely then that the invocation has the wrong address or port for 
the machine that the WF server is running on.  If you are running in the 
WTE in WDSC you could turn up the tracing to maybe FINE or so and I think 
it should say in the console what it is trying to connect to.   Are there 
any firewalls between the WAS and the WF server ?
Mike
Mike Hockings, P.Eng.
System i Application Development Tools  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 
voice 905 413 3199
rstearns@xxxxxxxxxxxxx 
Sent by: wdsci-l-bounces+hockings=ca.ibm.com@xxxxxxxxxxxx
06/07/2007 11:51 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
wdsci-l@xxxxxxxxxxxx
cc
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.
As an Amazon Associate we earn from qualifying purchases.