Issue 13244 - JVM crashes in shutdown hook while terminating office
Summary: JVM crashes in shutdown hook while terminating office
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows NT
: P3 Trivial
Target Milestone: ---
Assignee: ooo
QA Contact: issues@api
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-04-10 06:48 UTC by jki
Modified: 2013-02-24 21:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jki 2003-04-10 06:48:46 UTC
Hi Juergen,

Could you ask OpenOffice to investigate this issue further, please?  The 
developers in that group will be able to examine their product,
isolate the cause of the behavior, and, if necessary, provide us with a 
detailed report.  You can report problems to the OpenOffice group at
http://www.openoffice.org/project_issues.html.

Regards,
Nathanael
----------------- Original Bug Report-------------------

category : java
release : 1.3.1
subcategory : native_interface
type : bug
synopsis : JVM crashes on shutdown while terminating StarOffice via the JavaAPI
description : FULL PRODUCT VERSION :
java version "1.3.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02)
Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode)

FULL OS VERSION :
Windows NT 4.00.1381, IE 5 5.50.4522.1800

EXTRA RELEVANT SYSTEM CONFIGURATION :
Local connection (named pipe) to StarOffice via the OpenOffice Bean.

A DESCRIPTION OF THE PROBLEM :
The StarOffice GUI is included into our Java application using the OpenOffice 
Bean (which is a heavyweight component and connects to the locally running 
StarOffice via a named pipe). We do several loads and some saves of documents 
and close the application.

During the shutdown of the JVM a shutdown hook is started to terminate the 
invisible StarOffice process that is running in the background.
(The hook uses the xDesktop.terminate() method of the 
com.sun.star.frame.XDesktop object.)

This problem "smells" like JNI (as the native pipe implementation is a dll 
provided by StarOffice) and/or a general sychronization problem (as is does
not happen each time the JVM shuts down).

see error message

ERROR MESSAGES/STACK TRACES THAT OCCUR :

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6d449cef
Function name=(N/A)
Library=c:\seu\jdk131\jre\bin\hotspot\jvm.dll

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.



Current Java thread:
	at org.openoffice.NativeConnection.read(Native Method)
	at 
com.sun.star.lib.uno.bridges.java_remote.XConnectionInputStream_Adapter.read
(XConnectionInputStream_Adapter.java:90)
	at java.io.DataInputStream.readInt(DataInputStream.java:338)
	at com.sun.star.lib.uno.protocols.urp.urp.readBlock(urp.java:489)
	at com.sun.star.lib.uno.protocols.urp.urp.readMessage(urp.java:592)
	at 
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge$MessageDispatcher.in
voke(java_remote_bridge.java:184)
	at 
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge$MessageDispatcher.ru
n(java_remote_bridge.java:175)

Dynamic libraries:
0x00400000 - 0x00405000 	c:\seu\jdk131\bin\appletviewer.exe
0x77F70000 - 0x77FD0000 	C:\WINNT\System32\ntdll.dll
0x77DC0000 - 0x77DFF000 	C:\WINNT\system32\ADVAPI32.dll
0x77F00000 - 0x77F62000 	C:\WINNT\system32\KERNEL32.dll
0x77E70000 - 0x77EC5000 	C:\WINNT\system32\USER32.dll
0x77ED0000 - 0x77EFC000 	C:\WINNT\system32\GDI32.dll
0x77E10000 - 0x77E67000 	C:\WINNT\system32\RPCRT4.dll
0x78000000 - 0x78040000 	C:\WINNT\system32\MSVCRT.dll
0x6D420000 - 0x6D4F0000 	c:\seu\jdk131\jre\bin\hotspot\jvm.dll
0x77FD0000 - 0x77FFB000 	C:\WINNT\System32\WINMM.dll
0x6D220000 - 0x6D227000 	c:\seu\jdk131\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 	c:\seu\jdk131\jre\bin\verify.dll
0x6D250000 - 0x6D266000 	c:\seu\jdk131\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000 	c:\seu\jdk131\jre\bin\zip.dll
0x6D020000 - 0x6D129000 	C:\seu\jdk131\jre\bin\awt.dll
0x73060000 - 0x73078000 	C:\WINNT\System32\WINSPOOL.DRV
0x76AD0000 - 0x76AD5000 	C:\WINNT\System32\IMM32.dll
0x77B80000 - 0x77C37000 	C:\WINNT\system32\ole32.dll
0x6D340000 - 0x6D348000 	C:\seu\jdk131\jre\bin\net.dll
0x776C0000 - 0x776C8000 	C:\WINNT\system32\WSOCK32.dll
0x776A0000 - 0x776B4000 	C:\WINNT\system32\WS2_32.dll
0x77690000 - 0x77697000 	C:\WINNT\system32\WS2HELP.dll
0x74FD0000 - 0x74FDE000 	C:\WINNT\System32\rnr20.dll
0x5F7F0000 - 0x5F7F7000 	C:\WINNT\System32\rpcltc1.dll
0x77650000 - 0x7765F000 	C:\WINNT\system32\msafd.dll
0x77680000 - 0x77689000 	C:\WINNT\System32\wshtcpip.dll
0x6D1E0000 - 0x6D21B000 	C:\seu\jdk131\jre\bin\fontmanager.dll
0x10000000 - 0x10008000 	C:\PROGRA~1\MOUSEW~1\SYSTEM\LgMousHk.dll
0x71290000 - 0x71296000 	C:\WINNT\system32\MSIDLE.DLL
0x0B9B0000 - 0x0B9E4000 	C:\WINNT\system32\openofficebean.dll
0x6D270000 - 0x6D275000 	c:\seu\jdk131\jre\bin\jawt.dll
0x76AE0000 - 0x76AFD000 	C:\WINNT\System32\imagehlp.dll
0x4FB80000 - 0x4FB8A000 	C:\WINNT\System32\PSAPI.DLL

Local Time = Thu Apr 03 09:33:25 2003
Elapsed Time = 247
#
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002C4
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode)
#


REPRODUCIBILITY :
This bug can be reproduced occasionally.
workaround : 
suggested_val : 
cust_name : Juergen Kindler
cust_email : j.kindler@fiscus.info
jdcid : Nubbs
keyword : webbug
company : fiscus GmbH, Bonn
hardware : x86
OSversion : win_nt_4.0
bugtraqID : 0
dateCreated : 2003-04-08 23:31:36.4
dateEvaluated : 2003-04-09 12:40:01.52
Comment 1 utomo99 2003-09-24 09:10:41 UTC
Please try using the latest OOo 1.1 Rc5, 
Your version already old enough, and many bug fixes since your version 
and 1.1 RC5. If the problem still happend in 1.1 RC5 please report back
Comment 2 utomo99 2003-11-13 07:47:35 UTC
please try latest java VM, or at least JVM 1.4. I hope it can solve
your problem
Comment 3 jki 2004-01-05 10:27:17 UTC
With SO6.0 PP3 & JDK 1.4.1 the problem did not occur any more.
In my view the issue should be closed.

Thanks
 Juergen
Comment 4 ooo 2004-01-29 15:57:04 UTC
closing