Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Although messages do exist in the associated messaging engine's message store and are not lost, some of them may not be displayed in the administrative console.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for IBM WebSphere Application Server * * version 8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Some messages are missing when they * * are browsed through the * * administrative console. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a source code bug in fetching all the messages for the destination from the message store to the administrative console and displaying them in pages. For example, if the page size is 20, first message for the 2nd page is 21st message. To display message on the second page, our code should skip first 20 messages and display messages from 21st to 40th. But the current code skips first 20 messages for each every priority and so the messages are missing. Please note that messages are physically present in the data store as you can see the missing messages in the message store dump. So messages are not lost. This problem can be reproduced when the destination has messages with mixed priorities and this problem can be seen in the second page and following.
Problem conclusion
Souce code bug has been fixed and tested. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.10 and 8.5.5.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Change the page size to the total number of messages in the destination so that all messages for the destination can be listed in first page. Please note if the destination depth is high, it may take time to load all the messages in one page.
Comments
APAR Information
APAR number
PI09219
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-09
Closed date
2014-05-05
Last modified date
2015-01-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022