WebLogic Downtime crash problem solving sharing

Source: Internet
Author: User

More irritable in the near future. The system is prone to downtime. The WebLogic console prints such as the following:

# Afatal error has been detected by the Java Runtime environment:

#

# SIGSEGV (0XB) at pc=0x0000003373c89afc,pid=21500, tid=139781136643840

#

# JREVERSION:6.0_45-B06

# Javavm:java HotSpot (TM) 64-bit Server VM (20.45-b01 mixed mode linux-amd64compressed oops)

#Problematic Frame:

# C [LIBC.SO.6+0X89AFC] unsigned LONG+0X2DC

#

# anerror report file with more information is saved as:

#/webhome/bea/user_projects/domains/crm_domain/hs_err_pid21500.log

#

# If Youwould to submit a bug report, please visit:

# http://java.sun.com/webapps/bugreport/crash.jsp

# Thecrash happened outside the Java Virtual machine in native code.

# seeproblematic frame for where to report the bug.

#

/webhome/bea/user_projects/domains/crm_domain/bin/startweblogic.sh:line 180:21500 Aborted (core dumped) ${ Java_home}/bin/java ${JAVA_VM} ${mem_args}-dweblogic.name=${server_name}-djava.security.policy=${wl_home}/server /lib/weblogic.policy ${java_options}${proxy_settings} ${server_class}


From the console log, you can see an outage error report file, Hs_error_pid****.log file, and crash report.


Error content such as the following, for several days query the cause of the problem. There are also crash reasons for how the system is optimized.


Finally learned that this can be solved, this share out to everyone, so that peers less detours. Can save a lot of other time, knowledge sharing.

This problem occurs because:

1. The jar or class file is currently being updated dynamically.

2. The current jar is greater than 4G and is JDK6 or earlier, JDK6 or earlier can only accept the version number below the 4G size.


Problem solving:

1. There is a property in the JDK 1.6.23 or above that prevents this problem from occurring crash. Configure dynamic read Jar or class

In WebLogic's startup script. Adding a parameter to the JVM's set address resolves this issue.

-dsun.zip.disablememorymapping=true;

I tried it. Very practical. Also please colleagues to maintain a good system on-line habits. First stop WebLogic, then change the class file. Then restart the WebLogic.

Or it can be changed to a hot deployment mode.



A fatal error has been detected by the Java Runtime environment:
#
# SIGSEGV (0XB) at PC=0X0000003E6A089B03, pid=19647, tid=140309875619584
#
# JRE VERSION:6.0_45-B06
# Java Vm:java HotSpot (TM) 64-bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)
# Problematic Frame:
# C [libc.so.6+0x89b03] unsigned long+0x2e3
#
# If you would as to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual machine in native code.
# See problematic frame for where to report the bug.
#


---------------T H R E A D---------------


Current thread (0x00007f9cf4018800): Javathread "pool-1-thread-201" [_thread_in_native, id=15488, Stack ( 0x00007f9c703b7000,0x00007f9c704b8000)]


Siginfo:si_signo=sigsegv:si_errno=0, Si_code=1 (segv_maperr), si_addr=0x00007f9c78f0c000


Registers:
RAX=0X657477782F6D6F63, rbx=0x6c2f6570622f6863, rcx=0x0000000000000176, rdx=0x000000000000bb29
Rsp=0x00007f9c704b4e48, rbp=0x00007f9c78f0427d, RSI=0X00007F9C78F0BFF0, rdi=0x00007f9dc85cb115
R8 =0x000000000000bb00, R9 =0x031402014b507373, r10=0x552900080800000a, R11=0x0c9f95f95b0646ef
r12=0x00390000207a0000, r13=0x0000000000000000, r14=0x001cd35781a40000, R15=0x0000000000005a65
RIP=0X0000003E6A089B03, eflags=0x0000000000010202, csgsfs=0x0000000000000033, err=0x0000000000000004
trapno=0x000000000000000e


Top of Stack: (sp=0x00007f9c704b4e48)
0x00007f9c704b4e48:00007f9f9308331e 00000000704b4e70
0x00007f9c704b4e58:00007f9eec831324 00007f9eec82df60
0x00007f9c704b4e68:0000000000000000 00000000a5fc4555
0x00007f9c704b4e78:00007f9c704b4ee0 0000000000000054
0X00007F9C704B4E88:00007F9F930835C4 00007f9cf4018800
0x00007f9c704b4e98:00007f9c704b4ee0 00007f9cf40189d0
0x00007f9c704b4ea8:0000000000000054 00007f9c704b5338
0x00007f9c704b4eb8:0000000000000054 0000000000000001
0x00007f9c704b4ec8:00007f9f9307b797 00007F9C704B4EE0
0x00007f9c704b4ed8:00007f9eec82df60 657477782f6d6f63
0x00007f9c704b4ee8:6c2f6570622f6863 73626f2f6369676f
0x00007f9c704b4ef8:6369767265732f68 65702f7364632f65
0x00007f9c704b4f08:697375426e6f7372 6f72422f7373656e
0x00007f9c704b4f18:6341646e61426461 797251746e756f63
0x00007f9c704b4f28:632e312453444345 000000007373616c
0x00007f9c704b4f38:00007f9f93b4e2c8 00007f9c704b4f60
0x00007f9c704b4f48:00007f9f93b5ec8d 00007f9c704b4f90
0x00007f9c704b4f58:00007f9f8c037cb0 00007f9c704b4f80
0x00007f9c704b4f68:00007f9f93aca246 00007f9f94168630
0x00007f9c704b4f78:00007f9f8c016b20 00007f9c704b4fb0
0x00007f9c704b4f88:00007f9f93b5d646 00007f9f941694f0
0x00007f9c704b4f98:00000007733e6780 00007f9f8c0388d0
0x00007f9c704b4fa8:0000000000000000 00007f9c704b4fc0
0x00007f9c704b4fb8:00007f9f93b51124 00007f9c704b5040
0x00007f9c704b4fc8:00007f9f93a69eee 00007f9c704b4ff0
0X00007F9C704B4FD8:00007F9F9391286C 0000000000000017
0x00007f9c704b4fe8:00000007733e6780 00007f9c704b5030
0x00007f9c704b4ff8:00007f9f93f160c6 00007f9eec96c708
0x00007f9c704b5008:00007f9cf4018800 0000000000000000
0x00007f9c704b5018:00007f9cf4018800 00007f9f94168630
0x00007f9c704b5028:00007f9f9414a159 00007f9f94168630
0x00007f9c704b5038:00007f9cf4018800 00007f9c704b53a0


Instructions: (PC=0X0000003E6A089B03)
0X0000003E6A089AE3:4C, 4c, 6f, 4c, 76 40
0x0000003e6a089af3:48 8d 7f C9 5d, FF, 8b, 8b, 5e 08
0X0000003E6A089B03:4C 8b 4e 4c 8b 66 4c 8b 28 5e 4c 8b
0X0000003E6A089B13:4C 8b 6e 4c 8b approx. 0f + 8f (XX)


Register to Memory Mapping:


RAX=0X657477782F6D6F63 is an unknown value
rbx=0x6c2f6570622f6863 is an unknown value
RCX=0X0000000000000176 is an unknown value
Rdx=0x000000000000bb29 is an unknown value
Rsp=0x00007f9c704b4e48 is pointing to the stack for thread:0x00007f9cf4018800
Rbp=0x00007f9c78f0427d is an unknown value
RSI=0X00007F9C78F0BFF0 is an unknown value
Rdi=0x00007f9dc85cb115 is an unknown value
R8 =0x000000000000bb00 is an unknown value
R9 =0x031402014b507373 is an unknown value
R10=0X552900080800000A is an unknown value
R11=0x0c9f95f95b0646ef is an unknown value
R12=0X00390000207A0000 is an unknown value
R13=0X0000000000000000 is an unknown value
R14=0X001CD35781A40000 is an unknown value
R15=0x0000000000005a65 is an unknown value




Stack: [0x00007f9c703b7000,0x00007f9c704b8000], sp=0x00007f9c704b4e48, free space=1015k
Native Frames: (j=compiled Java Code, j=interpreted, VV=VM Code, c=native code)
C [libc.so.6+0x89b03] unsigned long+0x2e3


Java frames: (j=compiled java code, j=interpreted, VV=VM code)
J Java.util.zip.ZipFile.getEntry (jljava/lang/string; Z) J
J java.util.zip.ZipFile.getEntry (ljava/lang/string;) ljava/util/zip/zipentry;
J Weblogic.utils.classloaders.ZipClassFinder.getSource (ljava/lang/string;) Lweblogic/utils/classloaders/source;
J Weblogic.utils.classloaders.AbstractClassFinder.getClassSource (ljava/lang/string;) lweblogic/utils/ Classloaders/source;
J Weblogic.utils.classloaders.MultiClassFinder.getClassSource (ljava/lang/string;) lweblogic/utils/classloaders/ Source;
J Weblogic.utils.classloaders.MultiClassFinder.getClassSource (ljava/lang/string;) lweblogic/utils/classloaders/ Source;
J Weblogic.application.utils.CompositeWebAppFinder.getClassSource (ljava/lang/string;) lweblogic/utils/ Classloaders/source;
J Weblogic.utils.classloaders.MultiClassFinder.getClassSource (ljava/lang/string;) lweblogic/utils/classloaders/ Source;
J Weblogic.utils.classloaders.CodeGenClassFinder.getClassSource (ljava/lang/string;) lweblogic/utils/classloaders /source;
J Weblogic.utils.classloaders.GenericClassLoader.findClass (ljava/lang/string;) Ljava/lang/class;
J Weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass (ljava/lang/string;) Ljava/lang/class;

WebLogic Downtime crash problem solving sharing

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.