PQ76499, 5.0.2; WLMServletListener causes repository
propagation to take long
Downloadable files
Abstract
The Repository service takes excessively long in
propagating out changed configuration changes.
Download Description
Since the repository service is taking a long time to propagate changes
out to the other nodes, there are a number of problems that could exist
because of this. There is no one single problem that will stand out the
most, other then it will relate to the repository not being synchroized in
a timely fashion. This may or may not occur if the customer is using
clusters.
PROBLEM CONCLUSION:
Since there was logic being executed on the handleNotification thread in
the WLMServletListener, the notification service wasn't able to handle it
very well. So the work that was being done by the WLMServletListener had
to be unloaded onto a separate thread when a notification was thrown to
the listener.
Prerequisites
Please download the update installer before applying this interim
fix: