APAR status |
Closed as documentation error.
| Error description
If you run startupserver.sh from any directory other than was
home/bin, a NODE RESTART message is thrown and the server will
not start because it can not load the admin.config properly.
This should be changed to allow for the file to be run
anywhere. Secondly, the NODE RESTART message from nanny.java
is not sufficient. A real message describing the problem
would be extremely helpful to both support and the customer:
for example: Could Not Load Admin.Config. would be extremely helpful to both support and the customer:for example: Could Not Load Admin.Config. Local fix
Always run startupserver.sh from the bin directory. Or modify
the script file to properly locate the admin.config file
no matter where you are on the machine when you run the script.
There is no workaround for the insufficient logging. Problem summary
The following should be removed from the 3.5.x release notes:
Full support for mutiple network adapters on a single physical
machine is not yet available for WAS.
This should be added instead:The following should be removed from the 3.5.x release notes:Full support for mutiple network adapters on a single physicalmachine is not yet available for WAS.
WebSphere Standard and Advanced tolerate the presence of more
than one network on a single platform as long as the
environment used to run WAS is configured such that the
following conditions are met.
The primary hostname refers to the default - primary - network
interface. The Domain Name Server's response to a query of the
platform's hostname returns that address of the primary network
interface.
The Domain Name Server's response to a query of the
platform's hostname
returns the address of the primary network interface
The IP for the platform resolves to the hostname and
vice versa for both formats of hostname: fully qualified
and not fully qualified.
Here is a good example of a multi-network interface card
NT platform that conforms to the above:This should be added instead:WebSphere Standard and Advanced tolerate the presence of morethan one network on a single platform as long as theenvironment used to run WAS is configured such that thefollowing conditions are met.The primary hostname refers to the default - primary - networkinterface. The Domain Name Server's response to a query of theplatform's hostname returns that address of the primary networkinterface.The Domain Name Server's response to a query of theplatform's hostnamereturns the address of the primary network interfaceThe IP for the platform resolves to the hostname andvice versa for both formats of hostname: fully qualifiedand not fully qualified.Here is a good example of a multi-network interface card
d:\work>ipconfig
Windows NT IP Configuration
Ethernet adapter ND53004:NT platform that conforms to the above:d:\work>ipconfigWindows NT IP Configuration, Ethernet
IP Address. . . . . . . . . : 208.180.235.122
(Primary IP)
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 208.180.235.1
Ethernet adapter NdisWan3:adapter ND53004:IP Address. . . . . . . . . : 208.180.235.122(Primary IP)Subnet Mask . . . . . . . . : 255.255.255.0Default Gateway . . . . . . : 208.180.235.1
IP Address. . . . . . . . . : 129.17.33.12
Subnet Mask . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . : 129.17.32.1
:\work>nslookup 208.180.235.122
erver: rose.tyler.net
ddress: 205.218.118.1
ame: cdm-235-122-pflu.cox-internet.com
Resolves to hostname)
Address: 208.180.235.122
d:\work>hostname
cdm-235-122-pflu (hostname is set correctly)
d:\work>nslookup cdm-235-122-pflu
(and resolves to the same)
d:\work>nslookup cdm-235-122-pflu.cox-internet.com
(also resolves to the same)
Server: rose.tyler.net
Address: 205.218.118.1
Name: cdm-235-122-pflu.cox-internet.com
Address: 208.180.235.122
(IP when fully qualified) Ethernet adapter NdisWan3:IP Address. . . . . . . . . : 129.17.33.12Subnet Mask . . . . . . . . : 255.255.254.0Default Gateway . . . . . . : 129.17.32.1:\work>nslookup 208.180.235.122erver: rose.tyler.netddress: 205.218.118.1ame: cdm-235-122-pflu.cox-internet.comResolves to hostname)Address: 208.180.235.122d:\work>hostnamecdm-235-122-pflu (hostname is set correctly)d:\work>nslookup cdm-235-122-pflu(and resolves to the same)d:\work>nslookup cdm-235-122-pflu.cox-internet.com(also resolves to the same)Server: rose.tyler.netAddress: 205.218.118.1Name: cdm-235-122-pflu.cox-internet.comAddress: 208.180.235.122(IP when fully qualified) Problem conclusion
Changes were made to 3.5 release notes. Temporary fixComments
APAR information | APAR number | PQ46460 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-02-23 | Closed date | 2001-04-13 | Last modified date | 2001-04-13 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|