RE: Problem with admistrative console

Joe,

One more thing. Supposedly the first time WAS starts (on any platform but I
am talking about server side) it goes out and retrieves a bunch of system
information, TCP/IP config info, etc. It uses this to initialize its
database. If this information is wrong the first time you attempt to start
WAS, the database will be initialized with incorrect values. If you later
correct the configuration, WAS may still fail because the database still
contains the incorrect info. You need to clean up that database before it
will get another clean start to recreate. In 4.0 the collection to clean up
is EJSADMIN4. Perhaps this concept also applies to your release.

-Marty


--__--__--

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



--__--__--