PQ63156: JAVA.RMI.REMOTEEXCEPTION: WS390SECURITYMANAGER DETECTS ILLEGAL THREAD WHEN STARTING WEBSPHERE APPLICATION SERVER ZOS V4.01 | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When starting WebSphere Application Server for zOS os/390 v4.01, customers may see java.rmi.RemoteException: WS390SecurityManager detects illegal thread at com.ibm.ws390.sec.WS390SecurityManager.getCurrentSubject at com.ibm.ws390.csi.WS390SecurityCollaborator.preInvoke at com.ibm.ejs.container.EJSContainer.preInvoke at com.ibm.ws390.wc.container.EJSRemoteStatelessRemoteWebContain at com.ibm.ws390.wc.container._RemoteWebContainerHome_Stub.creat at com.ibm.servlet.engine.webapp.WebApp.getRemoteWebContainerIns at com.ibm.servlet.engine.webapp.WebApp.loadServletManager at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:149) at com.ibm.servlet.engine.srt.WebGroup.loadWebApp at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:148) ..... Additional error symptoms: ExtendedMessage: setting unchecked exception; value 1 = com.ibm. websphere.csi.CSIException: runas problem: getCurrentSubject ; nested exception is: ExtendedMessage: runas setting is CallerLocal fix One of the following may work around the problem: 1. Run the BBOWCUPD jcl against the failing J2EE server 2. Delete and re-install the J2EE serverProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * * * **************************************************************** * PROBLEM DESCRIPTION: Servlet init method issuing a DB2 conne * * is getting a java NullPointer exception * * get390CredFromSubject method due to a n * * Subject. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** During the servlet init method call, the 'runas setting' is being setup as 'caller', when it should be 'server', causing a jdbc connection to DB2 to fail.Problem conclusion The fix is provided by the APAR PQ63156 in COMPONENT ID: 5655-A9801 (POK). With this fix if there is a no identity we run as server identity. This change affects compid 5655A9800, and is fixed in CMVC defect PQ63156.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ63156
IBM Group: Software Group
Modified date: Jan 7, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.