PQ73672: Appserver fails to start | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Component: Systems management The austin SM development team is aware of the problem and the apar should be transferred to the sm team. Application server fails to start and throws the following: Exception thrown: com.ibm.ejs.sm.util.process.exception.ProcessOpException: Error creating new process. 079: Value too large for defined data type Some information of the process creation command, Working directory: /opt/WebSphere/CommerceServer Executable: /opt/WebSphere/AppServer/java/jre/bin/java Command line arguments: -server -Xbootclasspath . . . . . .Local fix 7665720f7472616e4c6f6753696d706c654f410000000b7472616e4c6f675769 726 Exception thrown: com.ibm.ejs.sm.util.process.exception.ProcessOpException: Error creating new process. 079: Value too large for defined data type This is coming from an open(path, oflag, mode) system call. The return value from this particular open() is -1, and errno is set to EOVERFLOW. LOCAL FIX: Delete entries from the log file or start with a clean log file. The above error is because OS is unable to open a file that Websphere uses for logging messages.Problem summary **************************************************************** * USERS AFFECTED: Users's of WebSphere Application Server. * **************************************************************** * PROBLEM DESCRIPTION: Starting app server fails and user * * is presented with message reporting * * a "ProcessOpException" and a message * * stating: * * * * "Error creating new process." * * * * * **************************************************************** * RECOMMENDATION: * **************************************************************** When trying to launch app server, user will see something like: >>> 4/4/03 9:47:42:097 CST 79567c ActiveServerP A ADMS0008I: Starting server: WebSphere Commerce higwww3_2 4/4/03 9:47:42:217 CST 390508 ActiveServerP W ADMS0021W: Failed to start the server: WebSphere Commerce Server . . . Some information of the process creation command, Working directory: /opt/WebSphere/CommerceServer Executable: /opt/WebSphere/AppServer/java/jre/bin/java Command line arguments: -server . . . /opt/WebSphere/AppServer/properties:/opt/WebSphere/. . . . . . IOR:0000000000000039524d493a636f6d2e69626d2e65. . . . . . com.ibm.ejs.*=all=disabled -lsdPort 9000 -moduleVisibility 1 Exception thrown: com.ibm.ejs.sm.util.process.exception.ProcessOpException: Error creating new process. 079: Value too large for defined data type <<< Key info to look for is: "Error creating new process." and "Value too large for defined data type" What is happening in this case is that a log file is exceeding an OS specified limit. Workaround is to identify the log file that is too large and either remove it or rename it so that WebSphere can use a file within OS limits.Problem conclusion This was corrected by LIDB1836 that introduced: "self-managing log files" into WebSphere. This new function is available in WebSphere 4.0.4 and later. ( line item 1836 )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 > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ73672
IBM Group: Software Group
Modified date: Jun 2, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.