Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9369

Apache tomcat for BI4 service entered the stopped state - BOBJ 4.1 SP2

$
0
0

Hi there,

We have installed BOBJ 4.1 SP2 and running the server for about a month or so successfully.

On May 1st, We noticed that the Tomcat server suddenly stops without any manual intervention.

In the Event Viewer we see this logged at that time:

"Apache tomcat for BI4 service entered the stopped state"

 

For example, I was working on scheduling WEBI reports, Everything was going fine and suddenly I received error on the launch pad and the page does not come up. And I could not open CMC either.

So I checked the CCM and found that Tomcat stopped. This happened suddenly as I was in the middle of working through.

We have noticed this kind of behavior 2-3 times.

After all the search for logs, I finally found this file "hs_err_pid1224" in \Program Files (x86)\SAP BusinessObjects\tomcat directory with some details like below in the file. Anyone come across situation like this, Please advise.

Thank you, Suman

 

#

# A fatal error has been detected by the SAP Java Virtual Machine:

#

# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000012848c0, pid=1224, tid=17616

# faulting address (tried to read): 0x000000002ea40000

#

# JRE version: 6.0_37-b06

# Java VM: SAP Java Server VM (6.1.044 21.1-b06 Oct 31 2012 10:44:56 - 61_REL - optU - windows amd64 - 6 - bas2:182728 (mixed mode) compressed oops)

# Problematic frame:

# C  [zip.dll+0x48c0]  Java_java_util_zip_ZipEntry_initFields+0x1e5c (sp=0x000000002ae4f010) (pc=0x00000000012848c0)

#

# Failed to write core dump. Minidumps are not enabled

#

# If you would like to submit a bug report, please visit:

#   http://service.sap.com/message

# Please save the hs_err file(s) and the written dmp file for further error analysis

# See SAP note 1500116 for further information on collecting core dumps after SAPJVM crashes

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#

 

Date: 2014-05-01 Time: 10:52:49

Process did run for 6 days, 0 hours, 20 minutes.

 

---------------  B u i l d   I n f o ---------------

 

compile date/time:     Oct 31 2012 10:41:49

sapjvm release:        6

sap_platform:          NTAMD64

platform:              windows

arch:                  amd64

codeline:              61_REL

hs bld trgt:           "product"

flags:                 !DEBUG, !ASSERT, PRODUCT

build user:            "makefact"

last change:           182728

build id:              6.1.044

_WIN32

_WIN64

_M_AMD64

Compiler (_MSC_VER): 1400

C-Runtime: multithreaded dynamic release

-_-_-_-

---------------  N a t i v e   C r a s h i n f o  ---------------


Viewing all articles
Browse latest Browse all 9369

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>