PQ59466: USING XML TO CREATE A GENERIC APP SERVER VIA IMPORT, THEN GO TO THE GUI CONSOLE TO START YOU RECEIVE A SIGSEGV 11.

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
If the Generic Application Server is created using XMLConfig
import, the Admin Server crashes when you attempt to start the n
ewly created Generic Application Server. The following error is
thrown:
.
[02.03.06 15:08:14:837 GMT+00:00] 11dedbf ActiveServerP A
ADMS0008I:thrown:.[02.03.06 15:08:14:837 GMT+00:00], 11dedbf ActiveServerP A
Starting server: "GenericAppServerTest" . SIGSEGV 11 segmentation violation si_signo [11]: SEGV si_errno [0]:ADMS0008I:Starting server: "GenericAppServerTest".SIGSEGV 11 segmentation violationsi_signo [11]: SEGVsi_errno [0]
si_code [1]: SEGV_MAPERR [addr: 0x0] stackpointer=E81BFAF8 "Thread-17" (TID:0x1e45d60, sys_thread_t:0x1e45c98, state:R, thread_t::si_code [1]: SEGV_MAPERR [addr: 0x0]stackpointer=E81BFAF8"Thread-17" (TID:0x1e45d60, sys_thread_t:0x1e45c98, state:R,
t@55, threadID:0xe8131dd8, stack_bottom:0xe8132000, stack_size:0x20000) prio=5 . If you run GDBtrace or DBXtrace against the core file you will see the following:thread_t:t@55, threadID:0xe8131dd8, stack_bottom:0xe8132000,stack_size:0x20000)prio=5.If you run GDBtrace or DBXtrace against the core file you will
. '/opt/WebSphere_355/AppServer/java/jre/bin/../bin/sparc/native_t hreads/j ava -Xmx'. Program terminated with signal 9, Killed. . This is indicating that the process was terminated (signal 9, Killed) by the Admin Server. So the JDK is not causing the core. . The generic server is expecting something (minimum space) for command line arguments.
see the following:.'/opt/WebSphere_355/AppServer/java/jre/bin/../bin/sparc/native_threads/java -Xmx'.Program terminated with signal 9, Killed..This is indicating that the process was terminated (signal 9,Killed) by the Admin Server. So the JDK is not causing the core..The generic server is expecting something (minimum space) forcommand line arguments.
Local fix
Create the Generic Server from the Admin Console.
.
OR
.
Replace following line in the XMLConfig file:
.<command-line-arguments/>
.
with below 3 lines in the import file:Replace following line in the XMLConfig file:..with below 3 lines in th
.<command-line-arguments> <arg></arg></command-line-arguments>
e import file:.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.x users     *
*                 of XMLConfig                                 *
****************************************************************
* PROBLEM DESCRIPTION: Cannot start the generic server using   *
*                      xmlconfig import to create a generic    *
*                      server.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the Generic Application Server is created using XMLConfig
import, the Admin Server crashes when you attempt to start the
newly created Generic Application Server. The following error
is thrown:
.
02.03.06 15:08:14:837 GMT+00:00  11dedbf ActiveServerP A
ADMS0008I:is thrown:.02.03.06 15:08:14:837 GMT+00:00  11dedbf ActiveServerP A
Starting server: "GenericAppServerTest" . SIGSEGV 11 segmentation violation
ADMS0008I:Starting server: "GenericAppServerTest".SIGSEGV 11 segmentation violation
Problem conclusion
The problem occurs when the user does not specify any
commandLineArgument in xml file.
Made the change in the adminServer codes
(ActiveServerProcess.java), so the XMLConfig or
other clients don't need to change the codes to make the
generic server start function work.
The code is available in next 3.5x ptf release.
Temporary fix
Comments
APAR information
APAR numberPQ59466
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-03-26
Closed date2002-04-15
Last modified date2002-04-15

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
ADMINSVR
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ59466
IBM Group: Software Group
Modified date: 2002-04-15