PK81057: COM.IBM.WS.CONSOLE.CORE.WSCPLUGIN.LOGININIT GENERATES NULLPOINTEREXCEPTION WHEN INVOKED CONCURRENTLY

Fixes are available

APAR status

Closed as program error.

Error description

The WSCPlugin provided by WAS is throwing a NullPointerException
when calling com.ibm.ws.console.core.WSCPlugIn.loginInit in a
multi-threading enviroment.

It may also cause 'Excess memory utilization' during
administrative operation. Excess memory utilization has been
seen when performing administrative operation, and where the
heap shows large allocations relation to the types
ValidationManagerImpl and MetadataHelper

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: COM.IBM.WS.CONSOLE.CORE.WSCPLUGIN.LOGININ
*                      GENERATES                               *
*                      NULLPOINTEREXCEPTION WHEN INVOKED       *
*                      CONCURRENTLY                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Tivoli Integrated Portal (TIP) performance tests
occasionally see a NullPointerException thrown by the
class com.ibm.ws.console.core.WSCPlugin.  The exception occurs
during a test that creates 100 users and that attempts
concurrent calls to login those users.  For example:

[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R
java.lang.NullPointerException
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
java.util.Hashtable.get(Hashtable.java:482)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.ws.sm.validation.impl.ValidationManagerRegistryImpl.loca
teManage
r(ValidationManagerRegistryImpl.java:115)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.ws.sm.validation.impl.ValidationManagerRegistryImpl.getV
alidatio
nManager(ValidationManagerRegistryImpl.java:129)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.ws.console.core.WSCPlugIn.loginInit(WSCPlugIn.java:224)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.isclite.runtime.action.LoginAction.initWSCConfig(LoginAc
tion.jav
a:474)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.isclite.runtime.action.LoginAction.createISCConfig(Login
Action.j
ava:440)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
com.ibm.isclite.runtime.action.LoginAction.execute(LoginAction.j
ava:209)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
org.apache.struts.action.RequestProcessor.processActionPerform(R
equestPr
ocessor.java:484)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
org.apache.struts.action.RequestProcessor.process(RequestProcess
or.java:
274)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
org.apache.struts.action.ActionServlet.process(ActionServlet.jav
a:1486)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:
510)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
[1/27/09 13:26:00:625 EST] 00000041 SystemErr     R  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

The following code fragment demonstrates a typical call that can
lead to the exception.  In this code fragment, the call to
"loginInit" is not thread-safe:

  void initWSCConfig(HttpSession session) {
    String methodName = "initWSCConfig";
    Class wscplugIn =
Class.forName("com.ibm.ws.console.core.WSCPlugIn");
    if ( wscplugIn != null ) {
      PlugIn wscPlugInInstance = (PlugIn)
wscplugIn.newInstance();
      wscPlugInInstance.init( getServlet().getServletContext()
);
      wscPlugInInstance.loginInit(
getServlet().getServletContext(), session );
    }
  }

Problem conclusion

This problem occurs because of a lack of synchronization to
code which manages the validation of server configuration
data, and because of the invalidation of a precondition that
calls to the validation manager be externally sycnronized.

The problem was resolved by adding synchronization statements
to the validation manager code.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.25 and 7.0.0.5.  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
PK81057
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-19
Closed date
2009-03-02
Last modified date
2010-03-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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK81057: COM.IBM.WS.CONSOLE.CORE.WSCPLUGIN.LOGININIT GENERATES NULLPOINTEREXCEPTION WHEN INVOKED CONCURRENTLY

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?