Fixes are available
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
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
When running Aries applications there is an intermittent NullPointerException if no code source is attached to the protection domain.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: When running Aries applications, a * * null pointer exception * * (NullPointerException) can occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running an Aries application, a null pointer exception (NullPointerException) can occur while attempting to retrieve a system property while handling a request to a servlet in the Aries application. The null pointer occurs because no code source attached to a protection domain which is used to obtain the system property. The system property is obtain during JNDI processing while handling a request to a servlet of the Aries application. The problem is a duplicate of the Eclipse bugzilla defect 282704, which was fixed in Equinox version 3.5.1. For more information, see the Eclipse bugzilla defect: https://bugs.eclipse.org/bugs/show_bug.cgi?id=282704 The null pointer exception will appear, for example, as follows: java.lang.NullPointerException at java.security.ProtectionDomain.getCodeSource(ProtectionDomain.ja va:116) at org.eclipse.core.launcher.Main$EclipsePolicy.getPermissions(Main .java:2139) at com.ibm.ws.security.policy.WSDynamicPolicy.getPermissions(WSDyna micPolicy.java:1007) at java.security.Policy.defaultImplies(Policy.java:443) at java.security.Policy.implies(Policy.java:433) at com.ibm.ws.security.policy.WSDynamicPolicy.implies(WSDynamicPoli cy.java:1036) at java.security.ProtectionDomain.implies(ProtectionDomain.java:159 ) at java.security.AccessController.checkPermission(AccessController. java:98) at java.lang.SecurityManager.checkPermission(SecurityManager.java:5 33) at com.ibm.ws.security.core.SecurityManager.checkPermission(Securit yManager.java:211) at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.ja va:1286) at java.lang.System.getProperty(System.java:383) at com.ibm.osgi.jndi.ContextProxy.findContext(ContextProxy.java:211 ) at com.ibm.osgi.jndi.ContextProxy.invoke(ContextProxy.java:124) at $Proxy0.lookup(Unknown Source) at javax.naming.InitialContext.lookup(InitialContext.java:455) at com.ibm.test.jpa.SubmitServlet.service(SubmitServlet.java:76) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1655) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1595) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterChain.java:131) at com.ibm.ws.osgi.web.extender.OsgiDirectoryProtectionFilter.doFil ter(OsgiDirectoryProtectionFilter.java:94) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi lterInstanceWrapper.java:188) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterChain.java:116) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAp pFilterChain.java:77) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA ppFilterManager.java:895) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:932) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:500) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest (ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java: 3810) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.j ava:276) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer. java:931) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai ner.java:1583) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin k.java:183) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr imination(HttpInboundLink.java:455) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewIn formation(HttpInboundLink.java:384) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpI nboundLink.java:272) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sen dToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.com plete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp leted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn cFuture.java:217) at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.jav a:205) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Problem conclusion
The problem was fixed by backporting the Eclipse bugzilla defect 282704 into the version of Eclipse code which is present in the IBM WebSphere Application Server installation image. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13 and 6.1.0.39. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
ZE Fix Error for 7.0, see PM30752 2011/02/11
Comments
APAR Information
APAR number
PM18002
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-07-07
Closed date
2010-08-12
Last modified date
2011-05-18
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
R700 PSY
UP
Document Information
Modified date:
24 October 2021