× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. June 2007

Re: Webfacing Server connection Socket closed

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.


Royce
Your original message indicated http://localIP:10016/AM/WFInvocation.do as
the url
When checking to make sure this is working for the url it breaksdown as
follows:
http://[IPof
httpServerORDNSname:(port#httpserverislisteningto)/[ContextRootOfYourApplication]
This should be enough to get you to your index.jsp page of the application.
So if my http server that works with my WAS server is called webapps and was
listening on the default http port of 80 and my application context root was
taxinq....then my url to call my webfacing application would be:
http://webapps/taxinq
If my http server of webapps was listening on port 7080 then it would be
http://webapps:7080/taxinq
Both of these would bring up the index.jsp that was generated with your
WebFacing application that would have the launch button calling you CL or
invocation.
If you don't have an http server and are using the internal http server that
your WAS server has for testing purposes then instead of using this you
would substitute the WASserver:port# where the httpServer:port#
(webapps:7080 would be replaced)in the above URL.

If you wanted to call your application directly verify in the webfacing
application what invocation number you have setup in you CL command and you
could call it directy by something like the following if you CL command was
using INV1
http://webapps:7080/taxinq/WFInvocation.do?inv=INV1

You can find out what invocation parameter you application is using also by
using the project navigator, finding you project and navigating to the
following file under:
WebContent\webfacing\services\invocation\html\invocation.jsp This jsp will
list the invocations.

Again didn't mean to steer you in any wrong direction before and hope this
helps and make sense. Maybe you already know this.
Cheri

<rstearns@xxxxxxxxxxxxx> wrote in message
news:OFCF76F77D.B7F6EC99-ON882572F3.0075E857-882572F3.00764D29@xxxxxxxxxxxxxxxx
A bit of confusion...

WAS did not have 4004 config'd It was a suggestion that I tried to see if
we could get the connection made between WAS and WF servers.

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

Okay I'll dig into the app itself.

Thanks,
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@xxxxxxxxxxxxxx
.
.
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.




--
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.

--
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.

--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.