× 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

Royce

Didn't mean to steer you in the wrong direction but in the past these have
been some things that have worked for me. In case you haven't found this
yet here is a link of troubleshooting things for WebFacing. There may be
some things in here that you haven't tried yet.

http://www-1.ibm.com/support/docview.wss?rs=3239&context=SSZND2&dc=DA400&uid=swg27005905&loc=en_US&cs=UTF-8&lang=en&rss=ct3239websphere

Cheri
<rstearns@xxxxxxxxxxxxx> wrote in message
news:OF2FBCF6DA.B76B745E-ON882572F3.006A83C5-882572F3.006C8248@xxxxxxxxxxxxxxxx
Added it through the admin console, double checked to make sure it was
saved and then cycled the server.
I noticed that I can't see it from the server properties/ server ports in
HTTPAdmin
I received the same error.

Thanks,
Royce Stearns
Manage, Inc.
(503) 353-1721 x103
www.manageinc.com



"Cheri Duchrow" <cduchrow@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/07/2007 11:14 AM
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







No you don't need to add a virtual host just the port to the WAS server.
Try:
Use the administration console and go to the servers and select the
Application servers. Find your server...it may be the only one. You may
have to scroll down but on the screen will be a Ports link. Click on it
and you
will see a list of ports. Add the 4004 port here. That might do it for
you.
Let me know if this makes sense.

Cheri

<rstearns@xxxxxxxxxxxxx> wrote in message
news:OF1AB2AB1C.62BF14FA-ON882572F3.006021BB-882572F3.00609CD4@xxxxxxxxxxxxxxx
.
This is on the i5 WAS ... do I need to add a virtual host for 4004?

Qautocfg is set to 1 = on
Qautovrt is set to *nomax


Royce Stearns
Manage, Inc.
(503) 353-1721 x103
www.manageinc.com



"Cheri Duchrow" <cduchrow@xxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/07/2007 10:21 AM
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.

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