APAR status
Closed as program error.
Error description
Starting in 5.0.2.8 WAS buildlevel the following sample log
entries can occur:
[11/22/04 12:06:38:532 JST] 47ff2cbc TraceNLS u No message
text associated with key Server.not.available.for.reconnect. in
bundle com.ibm.ws.wlm.resources.WLMMessages
These follow:
[11/22/04 12:06:38:587 JST] 47ff2cbc Configuration e Could not
reconnect to server, server will not be added to cluster.
org.omg.CORBA.TRANSIENT:
Connection refused:host=gabin,port=9816 minor code: 4942F301
completed: No
[11/22/04 12:06:39:195 JST] 47ff2cbc Configuration e Could not
reconnect to server, server will not be added to cluster.
org.omg.CORBA.TRANSIENT:
Connection refused:host=gabin,port=9817 minor code: 4942F301
completed: No
[11/22/04 12:07:28:378 JST] 168d2ca2 DiscoveryServ d
IOExceiption occurs while sending messages
java.io.IOException: ADMD0004E:
Can not open the TCP socket: 7,272
This warning is completely begnin, and can be ignored (for now).
WLM development has researched this issue and found that
a Tr.Service call was added in the 5.0.2.7 FixPack level:
Tr.service(tc, "Server not available for reconnect.", new
Object[] {
members[j].clusterName,members[j].nodeName,
members[j].memberName, e});
ABSTRACT: missing entry from NLS PROPERTIES file, to properly
translate a warning
PROBLEM SUMMARY (to be used upon apar closure):
The Tr.service calls are for putting entries into the activity
log, so as to avoid cluttering the System.out logs. The problem
only arises because the string has to be translated, so it goes
through the TraceNLS code, which looks for the key = "Server not
available for reconnect.", in the WLM message bundle, which is
(obviously) not there. The problem is hard coding the String
"Server not available for reconnect." - there should be a key
added to the WLM Message bundle, so that this warning can be
added to the activity logs. The warning itself is very normal
to be logged, as simply starting a DMGR will cause WLM
to deduce from the config which members are a part of the
cluster and to try to "(re)connect" with them. In the case where
only the DMGR is started, the cluster members will not be
available, hence the warning (in this case) is benign (and
expected - only it should have been tucked away in the
activity log).
Following actions were taken:
1) Add a Key and message to the WLM bundle so that this warning,
for cases where the Tr.Service call needs to be translated, can
been properly done, and placed in the activity log.
2) As this warning is totally begnin, there is nothing for the
customers to worry about, but changes will be made to 1) above
and a next fixpak should contain corrected Tr.Service call
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* WorkloadManagement (WLM), or Clustering *
****************************************************************
* PROBLEM DESCRIPTION: untranslated Tr.Service call resulted *
* in an exception, because there was no *
* key in the NLS resource bundle *
****************************************************************
* RECOMMENDATION: *
****************************************************************
untranslated Tr.Service call resulted in an exception, because
there was no key in the NLS resource bundle
Problem conclusion
replaced the Tr.service with a Tr.event, which does not
require translation
The fix for this APAR is currently targeted for inclusion in
fix pack 5.0.2.11
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK00326 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-01 |
Closed date |
2005-02-08 |
Last modified date |
2005-05-17 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|