|
| Problem | A WebSphere Application cluster with Models/Clones using OSERemote protocol to communicate with the WebSphere Application Server plugin fails to service requests. The plugin traces indicate that the server groups are failing to communicate with the Admin Server. The errors logged: "Failed to initialize the router object router_init returned 1
private_ose_init: Cannot communicate with Admin Server".
"get_property: Return NULL for ose.srvgrp.<servergroup_name.clone<#>
Failed to initialize the router object".
The router object is an internal OSE Plugin structure that stores a list of DNS/IP addresses for all servers [including the Admin Server] in the WebSphere domain. This internal list is created from the queues.property file and the bootstrap.property file. All hostname and IP addresses as stated previously must be correct for this router to initialized properly.
| | | | Solution | There has been a DNS change or a change in routing information, which the customer rep is not aware of. This usually happens if the customer has a separate Networking group and another group doing the WebSphere Application Server admin tasks. When the correct DNS/IP information is provided to the WebSphere Application Server again, the Application Server plugin will be able to connect with the Admin Server. | |
| | | Historical Number | PMR 69163 b344 | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Plug-in Operating system(s): Windows 2000, Windows NT Software version: 3.5.4 Software edition: Advanced Edition Reference #: 1054861 IBM Group: Software Group Modified date: 2003-06-23
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|