Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
After migrating from WebSphere member manager (WMM) to virtual member manager (VMM), VMM is not able to process/handle root i.e BLANK base entries from LDAP. VMM allows to configure root of the LDAP server to be configured into VMM. WMM was allows BLANK names to baseEntries and was not handled properly by VMM. After migrating from WMM to VMM, VMM was showing nothing for getIdMgrRepositoriesForRealm, output for the said command was {}; i.e nothing. And throws NullPointerException in WAS ISC. java.lang.NullPointerException at com.ibm.ws.console.security.IdMgrRealm.VirtualRealmDetailActionG en.popul ateCollectionTableRow(VirtualRealmDetailActionGen.java:213) at com.ibm.ws.console.security.IdMgrRealm.VirtualRealmController.se tupColle ctionForm(VirtualRealmController.java:300) at com.ibm.ws.console.security.IdMgrRealm.VirtualRealmController.se tupDetai lForm(VirtualRealmController.java:208) at com.ibm.ws.console.core.action.BaseDetailController.perform(Base DetailCo ntroller.java:299) at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefini tion(Unk nown Source) at org.apache.struts.tiles.TilesRequestProcessor.processForwardConf ig(Unkno wn Source) at com.ibm.isclite.container.controller.InformationController.proce ssForwar dConfig(InformationController.java:217) at org.apache.struts.action.RequestProcessor.process(Unknown Source) at org.apache.struts.action.ActionServlet.process(Unknown Source) at org.apache.struts.action.ActionServlet.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.ja va:1657) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.ja va:1597)
Local fix
No workaround.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: After migrating from WMM to VMM, VMM * * is not able to process root (that is, * * BLANK) base entries from LDAP. * **************************************************************** * RECOMMENDATION: * **************************************************************** VMM allows you to configure "root"(BLANK baseentry in VMM) of the LDAP server. But after migrating from WMM to VMM. VMM is not able to process BLANK base entries from LDAP(root baseEntry).
Problem conclusion
This fix will read BLANK baseEntry as ROOT and reflect the same back to the configuration console/panels. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.21 and 8.0.0.2. 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
PM47114
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-04
Closed date
2011-11-29
Last modified date
2011-11-29
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021