SAP Knowledge Base Article - Preview

2092803 - SIA and Tomcat not starting after in BOE XI 3.1 SP5 upgrade after Solaris 10 upgrade

Symptom

SIA and Tomcat crashing in BOE XI 3.1 SP5 after Solaris 10 Operating system is upgraded to Solaris 11

SIA and Tomcat both generating hs_err_pidXXXX.log in respective logs directory.(SIA in <Install_DIR>/bobje/logging directory and Tomcat in <Install_DIR>/bobje/tomcat/logs)

When analized hs_err_pidXXXX.log found error message

#

# An unexpected error has been detected by HotSpot Virtual Machine:

#

# SIGSEGV (0xb) at pc=0x7fa73d48, pid=28273, tid=128

#

# Java VM: Java HotSpot(TM) Server VM (1.5.0_22-b03 mixed mode)

# Problematic frame:

# C [libc.so.1+0xc3d48]

Stack: [0x682a0000,0x682e0000), sp=0x682df920, free space=254k

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

C [libc.so.1+0xc3d48]

C [libhoard.so.1.0.7+0x198c] __1cKthreadHeapGmalloc6MkI_pv_+0xa8

V [libjvm.so+0x175e28]

V [libjvm.so+0x195d7c]

V [libjvm.so+0x19aa70]

V [libjvm.so+0x2e0bac]

V [libjvm.so+0x6851c4]

 

 


Read more...

Environment

  • SAP Business Objects Enterprise XI 3.1 SP 5
  • Solaris 10

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

Solaris 10, BOE XI 3.1 SP4, LD_PRELOAD, libhoard.so.1, 11, upgrade, crash, sia, tomcat , KBA , BI-BIP-INS , Installation, Updates, Upgrade, Patching , Problem

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.