Symptom
- A stack happened, that suggested that the server was being shut down. However, it continued its boot uninterrupted.
Attributes JVM -Xmx500m, others -jvmlogging INFO -jvmlogfile $SYBASE/$SYBASE_ASE/rtms.log -jvmpropertyfile $SYBASE/$SYBASE_ASE/lib/rtms.properties -jvmminthreads 0 -jvmmaxthreads 10 -jvmthreadtimeout 600 -rtdsversion 4.5esd#3 -kmap 1000005c440 -shared 0xa2148f59, 10000000000, 0x9500000000, 0x1159.
Stack overflow detected: limit: 0x0000010059e92b10, guardpage: 0x0000010059e94b10, sp: 0x00000000831f663c
0x0000000081556a60 pcstkwalk+0x18(0x00000000831f61c0, 0x00000000831f4038, 0x000000000000270f, 0x0000000000000002, 0x0000000000000000)
0x00000000815568a8 ucstkgentrace+0x23c(0x0000000002910149, 0x0000000000000002, 0x000000000000270f, 0x0000000000000000, 0x0000000000000000)
0x0000000081552bb4 ucbacktrace+0xe4(0x0000000002910149, 0x0000000000000001, 0x00000000831dcc00, 0x0000000000000008, 0x0000010087e24c40)
0x0000000081555120 ucstackcrash+0x8c(0x0000000053746000, 0x000000005374616b, 0x0000000000007400, 0x0000000000000004, 0x0000010000000000)
0x000000008069301c _$o1ceynN0.upyield+0x80(0x000001021a930918, 0x00000000831f7000, 0x0000000000000000, 0x0000000000000002, 0x0000000000040000)
0x0000000080755244 _$o1ceztF0.upunsetcritical+0x3c(0x0000000002910149, 0x0000000000000001, 0x0000010087e246b0, 0x0000000000000001, 0x00000000fffbfc00)
0x000000008153b9b8 kaclk_restart+0x6c(0x0000000000005739, 0x0000000000000001, 0x00000000831f6c08, 0x000000000000000c, 0x0000000082dc7400)
0x000000008156d990 os_call_fork+0x2f4(0x0000010059ebfe34, 0x0000000000000000, 0x00000000831f6800, 0x0000000000005739, 0x000000000000001f)
0x0000000081586adc _coldstart(0x0000010059ebfe34, 0x000000008156d68c, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
end of stack trace, spid 1088, kpid 43057481, suid 0
*** Stack corrupted, server aborting.
0x0000000081556a60 pcstkwalk+0x18(0x00000000831f5f00, 0x00000000831f3d78, 0x000000000000270f, 0x0000000000000002, 0x0000000000000000)
0x00000000815568a8 ucstkgentrace+0x23c(0x0000000002910149, 0x0000000000000002, 0x000000000000270f, 0x0000000000000000, 0x0000000000000000)
0x0000000081552bb4 ucbacktrace+0xe4(0x0000000002910149, 0x0000000000000001, 0x00000000831dcc00, 0x0000000000000008, 0x0000010087e24c40)
0x0000000081555358 keipanic+0x88(0x000000000000753b, 0x0000010087e24c40, 0x00000000831f6368, 0x00000000831f65f8, 0x0000000000000000)
0x0000000081555128 ucstackcrash+0x94(0x0000000053746000, 0x000000005374616b, 0x0000000000007400, 0x0000000000000004, 0x0000010000000000)
0x000000008069301c _$o1ceynN0.upyield+0x80(0x000001021a930918, 0x00000000831f7000, 0x0000000000000000, 0x0000000000000002, 0x0000000000040000)
0x0000000080755244 _$o1ceztF0.upunsetcritical+0x3c(0x0000000002910149, 0x0000000000000001, 0x0000010087e246b0, 0x0000000000000001, 0x00000000fffbfc00)
0x000000008153b9b8 kaclk_restart+0x6c(0x0000000000005739, 0x0000000000000001, 0x00000000831f6c08, 0x000000000000000c, 0x0000000082dc7400)
0x000000008156d990 os_call_fork+0x2f4(0x0000010059ebfe34, 0x0000000000000000, 0x00000000831f6800, 0x0000000000005739, 0x000000000000001f)
0x0000000081586adc _coldstart(0x0000010059ebfe34, 0x000000008156d68c, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
end of stack trace, spid 1088, kpid 43057481, suid 0
ueshutdown: exiting - Yet the server continued to boot and the spid 1088 is sleeping.
- spid 1088 is for the IBM_MQ, and messaging is working as expected.
- The whole server appears to be working as expected.
- The $SYBASE/$SYBASE_ASE/rtms.log shows that it booted, with nothing much in the log:
JRTMS: INFO [main] (?:?) - JRTMS Server Version: 4.5esd#3
JRTMS: INFO [main] (?:?) - shmemrtds Version: 4.5esd#3
JRTMS: INFO [main] (?:?) - ASE JRTMS/15.0.0/P/1.6.0_71/generic/OPT/August 14 2019
JRTMS: INFO [main] (?:?) - Starting logging into $SYBASE/$SBASE_ASE/rtms.log
JRTMS: INFO [main] (?:?) - Confidential property of Sybase, Inc.
Copyright 1987, 2007
Sybase, Inc. All rights reserved.
Unpublished rights reserved under U.S. copyright laws.This software contains confidential and trade secret information of Sybase,
Inc. Use, duplication or disclosure of the software and documentation by
agreement between the Government and Sybase, Inc. or other written
agreement specifying the Government's rights to use the software and any
applicable FAR provisions, for example, FAR 52.227-19.
Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA - Questions:
- Should the server be rebooted immediately?
- What can be used to monitor the Active Messaging?
Read more...
Environment
- SAP Adaptive Server Enterprise ASE
- Real Time Messaging
Product
Keywords
KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.