Fixes are available
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.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
Users should be able to set the Single maximum rows value for the registry by using the Maximum inquiry result set size general property on the UDDI registry user interface. The actual behavior is otherwise. Regardless of any maxRows/listHead arguments supplied the IBM UDDI registry imposes a 1024 entity limit on the overall result set. This affects requests even for a subset of the overall results.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of UDDI * * * **************************************************************** * PROBLEM DESCRIPTION: When querying a UDDI Registry that * * contains a large data set an * * E_resultSetTooLarge error may occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** The maximum value for the UDDI node setting "Maximum inquiry result set size" has an upper constraint of 1000. This value is too low when the UDDI data set is large.
Problem conclusion
The constraint on the UDDI node setting "Maximum inquiry result set size" was raised from 1000 to 65536. The value of this setting is not modified itself but it can now be updated to an appropriately high value. The deployed UDDI.ear J2EE application will need to be updated for the fix to take effect. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.10. 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
PI54811
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-04
Closed date
2016-03-24
Last modified date
2016-07-12
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022