topic Re: JVM crashed with Unexpected Signal : 11 in Operating System - Linux

JVM crashed with Unexpected Signal : 11

Roy Ngan — Mon, 05 May 2008 12:09:06 GMT

We are running WebLogic server in HP-UX 11.11, using JVM 1.3.1.09. We have the WebLogic server re-started on one Sunday, then several hours later, the WebLogic crashed with the following error:

Unexpected Signal : 11 occurred at PC=0xca53287c
Function name=runtime_resolve_virtual_method__12LinkResolverSFR8CallInfo12methodHandle11KlassHandle6HandleT3bP6Thread
Library=/opt/java1.3/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl

Current Java thread:
"ExecuteThread: '30' for queue: 'default'" daemon prio=6 tid=0x00040988 nid=42 lwp_id=8020227 runnable [0x3c660000..0x3c65e500]
at weblogic.utils.StringUtils.valueOf(StringUtils.java:331)
at jsp_servlet.__doc_list._jspService(__doc_list.java:861)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at cr.component.AuthenticateFilter.doFilter(AuthenticateFilter.java:103)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:609)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:402)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:151)
at jsp_servlet.__docs_list._jspService(__docs_list.java:586)
...

It seems that it is the first time to load the page doc_list.jsp after the WebLogic restarted. Then when WebLogic compiles this JSP, the JVM crashed.

Anyone knows how will this error occur, and how to prevent it?

Re: JVM crashed with Unexpected Signal : 11

Steven E. Protter — Mon, 05 May 2008 12:18:40 GMT

Shalom,

The usual source of this is:
1) Bad application code.
2) Improperly patched OS.
3) Old buggy version of Java.

I can see #3 as nearly definite, #2 and #1 as probable.

Have the application people look at their code.

See if your application is compatible with supported versions of java, 1.4 or 1.5(5.0).

SEP

Re: JVM crashed with Unexpected Signal : 11

Roy Ngan — Tue, 13 May 2008 08:45:38 GMT

I would like to ask can I open a support case for HP-UX JVM problems? What do I need to open a case? Is that enough if I have a hardware support agreement, or a software support agreement HP-UX Java is needed?

Re: JVM crashed with Unexpected Signal : 11

Dennis Handly — Wed, 14 May 2008 09:38:29 GMT

>I would like to ask can I open a support case for HP-UX JVM problems? What do I need to open a case? or a software support agreement HP-UX Java is needed?

You need a software support contract for HP-UX and Java is supported with that.

Do you have the latest Java patches?

Re: JVM crashed with Unexpected Signal : 11

Heironimus — Wed, 14 May 2008 13:03:34 GMT

Since you're talking about a WebLogic server crash, I'd start with BEA support instead of HP support.

Re: JVM crashed with Unexpected Signal : 11

Steven E. Protter — Wed, 14 May 2008 14:16:44 GMT

Shalom,

You are better of starting with vendor support.

But before even bothering with that go to http://www.hpux.com/go/java and get the latest version of Java supported by your application and install required OS patches.

SEP

Re: JVM crashed with Unexpected Signal : 11

IT Response — Mon, 19 May 2008 23:05:14 GMT

Hello Roy,
You will need to open a call with the HP Response Center. We will need the core file to analyze and find out why Java cored and then take an action based on the analysis.
Assuming that you have a valid support contract call 1 800 633-3600 and place a call against Java and we'll take it from there.

Re: JVM crashed with Unexpected Signal : 11

IT Response — Mon, 19 May 2008 23:09:16 GMT

A clarification here! the program that causes the core is an HP program not a BEA one. So, BEA will send you back to HP. As I mentioned you need to open a call with the HP Response Center and take it from there.