If you are always going to deploy the webapp on WAS on the same machine
that you are targeting with the invocations then you should be able to use
localhost as the host name and not have to specify the specific host ip
name or address. Keep in mind though that this won't work when running
in the test environment ;-)
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@xxxxxxxxxxxx
06/07/2007 08:46 PM
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
Mike Hockings and Cheri Duchrow ....
Thanks for your responses, my application is now running.
Following both of your leads, I went back to the application and the
deployment descriptor to address the problem. The ip address that I use
for RSE and remote testing wouldn't work on the inside WAS on the i5
because of DNS issues. After giving it a fully qualified name that DNS
could resolve on the inside, rebuilding the app and reinstalling on the
WAS v6.1 ... it works. Now I'm wondering about the wisdom of the
deployment descriptor containing the host name.
Thanks again.
Royce Stearns
Manage, Inc.
(503) 353-1721 x103
www.manageinc.com
Mike Hockings <hockings@xxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/07/2007 01:00 PM
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
WAS on the same machine as the WF server should NOT be trying to grab port
4004 or it will not work. That is, either WAS or the WF server will fail
to bind to the port. 4004 is the port used by the WF server, not WAS, at
least for the default config.
Port 4004 should be serviced by the WebFacing server itself. Look in your
WF project and check that the CL invocation settings for the WF'd app you
are trying to run is pointing to the right address for your i5 and that it
is configured to use port 4004. Since your WF server seems to be running
and responding to port 4004 I would expect the problem to be that the
project is not pointing to the same place.
Mike
Mike Hockings, P.Eng.
System i Application Development Tools - CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 905 413 3199
"Cheri Duchrow" <cduchrow@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/07/2007 01:21 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
wdsci-l@xxxxxxxxxxxx
cc
Subject
Re: [WDSCI-L] Webfacing Server connection Socket closed
If you are running this using the test server within WDSC check to make
sure
that test WAS server has 4004 as a port listed in it's configuration.
It used to be in previous versions of the test WAS server configurations
that I would have to add 4004 port to the test server.
Startup your test server and then right click on it and go to the admin
console. If you are familiar with the WAS admin console you should be
able
to navigate and find the port setup. Just in case:
Go to the servers and select the Application servers. You may have to
scroll down but on the screen will be a Ports link. Click on it and you
will see a list. Add one that has * as the host and port 4004 as the
port.
In a WAS 5.x test server it was a little easier to add ports to the
server.
Also verify that the iSeries has the two system values setup correctly:
Qautocfg has to be set to yes
Qautovrt has to be set to *nomax
In all of my traveling to various environments helping people setup
WebFacing these two system values had to be set this way for WebFacing to
work.
HTH
Cheri
<rstearns@xxxxxxxxxxxxx> wrote in message
news:OF6E18CA10.4DE14D34-ON882572F3.0053E9B8-882572F3.00572602@xxxxxxxxxxxxx
.
.
.
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.
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
midrange.com
