RE: Problem with (WebSphere) admistrative console

Joe -

Keep trying - IBM will tell that you need 500MB defined to the pool
QEJBADMIN runs in and a minimum 600 CPW processor.  On a 170 we have it took
over 90 minutes for QEJBADMIN to return the "ready" message the first time
and I was never able to get the admin console to connect.  If you have
QPFRADJ set to 2 or 3, try starting the admin console then moving 500MB into
the pool.  Be aware that the performance of the PC matters also, it
routinely takes me 10-15 minutes to connect with the admin console installed
on a 300 mhz PC.

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group
(515) 267-2485
SIngvaldson@guidemail.com

-----Original Message-----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <midrange-l@midrange.com>
Subject: Problem with admistrative console
Date: Fri, 14 Jun 2002 10:59:52 -0500
Reply-To: midrange-l@midrange.com

Has anyone installed WebSphere Advanced Edition 3.5.6 and gotten the
administrative console to load?  Has anyone even tried, and perhaps had it
hang?  At a client site, adminclient.bat comes up, it says "attempting to
establish connection", and thne just hangs.  NETSTAT says communication on
Port 900 is established.  QEJBMNTR is in EVTW, and QEJBADMIN is at JVAW
having said (in the joblog) that "WebSphere application server job started."

Any thoughts?

Joe