java.lang.NoSuchFieldError occurs when trying to start a nodeagent or application server
 Technote (troubleshooting)
 
Problem(Abstract)
A seclogger40.jar file exists in the AppServer/classes or DeploymentManager/classes directory of the WebSphere® Application Server V5 or V6 system.

The file, seclogger40.jar, is a debugging file that is only valid for WebSphere Application Server V4 systems. If you have this file in the classes directory on a V5 or V6 system, the nodeagent or application server will not start.
.
 
Cause
Here are two examples of the error:

[11/5/04 13:04:23:016 CST] 23393025 ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.runtime.component.ORBImpl] java.lang.NoSuchFieldError: com.ibm.ISecurityL13SupportImpl.SecurityLogger: field debugEntryEnabled
not found
at
com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientRI.pre_init(CSIClientRI.java:205)

[1/19/05 14:24:04:142 GMT+00:00] 36791a79 WsServer      E WSVR0003E: Server WebSphere_Portal failed to start
java.lang.NoSuchFieldError: com.ibm.ISecurityL13SupportImpl.SecurityLogger: field debugEntryEnabled
not found
at
com.ibm.rmi.pi.InterceptorManager.runPreInit(InterceptorManager.java:156)
 
Resolving the problem
Make sure the application server, nodeagent and dmgr are stopped.

  1. Remove seclogger40.jar from both the classes directory and completely out of any WebSphere directories.

  2. Restart dmgr, nodeagent, and application server, in that order.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 6.0.1
Software edition:
Reference #: 1197223
IBM Group: Software Group
Modified date: May 20, 2005