DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34239>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34239

           Summary: Tomcat crashing with Unexpected Signal 4
           Product: Tomcat 4
           Version: 4.1.27
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


We are running documentum application on tomcat. The problem is that tomcat is 
crashing several times mostly nearby one database query only. The problem is 
taking place on productin server only and cannot be replicated anywhere on test 
or development servers. 

PFA three seperate instances of tomcat crash.

PDF Query:select 
r_object_id,object_name,r_version_label,r_lock_owner,r_object_type,r_content_siz
e, a_content_type,r_is_virtual_doc,r_link_cnt,r_modify_date from ancillary_docs
(all) where i_chronicle_id in (select i_chronicle_id  from ancillary_docs(all) 
where r_object_id ='null') and document_type='Jct PDF' order by r_version_label
110491883 [http8080-Processor37] DEBUG 
com.documentum.custom.webcomponent.rejectreason.Rejectreason  - Get 
Reason;select r_object_id,rejected_by, rejected_date, reject_reason from 
workflow_tracking where workflowid=4d00272080000520 and sent_to not in (select 
group_name from dm_group)  order by accepted_date desc 
Current Profile:JCT
Edit content:3
Package Name:InstructionSheet
Package Name:Content
Content Doc Query:select r_object_id,r_version_label, 
document_id,document_name,document_type,export_flag  from smg_docs(all) where 
r_object_type in ('jct_xml_content_docs','jct_nonxml_content_docs') and 
document_id in ( select document_id from smg_docs(all) where r_object_id 
= '090027208000415d') and i_latest_flag=1 
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdfab9774

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 4 occurred at PC=0xD2CD0
Function=[Unknown.]
Library=(N/A)

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:

Dynamic libraries:
0x10000         /usr/j2se/bin/java
0xff380000      /usr/lib/libthread.so.1
0xff3f2000      /usr/lib/libdl.so.1
0xff280000      /usr/lib/libc.so.1
0xff3b0000      /usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
0xfec00000      /usr/j2se/jre/lib/sparc/client/libjvm.so
0xff240000      /usr/lib/libCrun.so.1
0xff220000      /usr/lib/libsocket.so.1
0xff100000      /usr/lib/libnsl.so.1
0xff1d0000      /usr/lib/libm.so.1
0xff0e0000      /usr/lib/libmp.so.2
0xff0a0000      /usr/j2se/jre/lib/sparc/native_threads/libhpi.so
0xff070000      /usr/j2se/jre/lib/sparc/libverify.so
0xfebc0000      /usr/j2se/jre/lib/sparc/libjava.so
0xfeba0000      /usr/j2se/jre/lib/sparc/libzip.so
0xe5150000      /usr/j2se/jre/lib/sparc/libnet.so
0xdf800000      /export/home/dmadmin/dfc/libdmcl40.so
0xe2060000      /usr/lib/libintl.so.1
0xe2030000      /usr/lib/librt.so.1
0xe2010000      /usr/lib/libpthread.so.1
0xe1f60000      /usr/lib/libaio.so.1
0xe1f40000      /usr/lib/libmd5.so.1
0xe4300000      /usr/j2se/jre/lib/sparc/libawt.so
0xe4280000      /usr/j2se/jre/lib/sparc/libmlib_image.so
0xe4210000      /usr/j2se/jre/lib/sparc/motif21/libmawt.so
0xe3e00000      /usr/dt/lib/libXm.so.4
0xe41a0000      /usr/openwin/lib/libXt.so.4
0xe43d0000      /usr/openwin/lib/libXext.so.0
0xe44b0000      /usr/openwin/lib/libXtst.so.1
0xe3d00000      /usr/openwin/lib/libX11.so.4
0xe4140000      /usr/openwin/lib/libdps.so.5
0xe43b0000      /usr/openwin/lib/libSM.so.6
0xe4110000      /usr/openwin/lib/libICE.so.6
0xe40f0000      /usr/lib/iconv/UTF-8%8859-1.so
0xe40d0000      /usr/lib/iconv/8859-1%UTF-8.so

Local Time = Tue Feb  1 16:47:13 2005
Elapsed Time = 110506
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.1_02a-b01 mixed mode)
#
# An error report file has been saved as hs_err_pid29839.log.
# Please refer to the file for further information.



--------------------------------------------------------------------------------
---------------



PDF Query:select 
r_object_id,object_name,r_version_label,r_lock_owner,r_object_type,r_content_siz
e, a_content_type,r_is_virtual_doc,r_link_cnt,r_modify_date from ancillary_docs
(all) where i_chronicle_id in (select i_chronicle_id  from ancillary_docs(all) 
where r_object_id ='null') and document_type='Jct PDF' order by r_version_label
Java HotSpot(TM) Client VM warning: Java HotSpot(TM) Client VM warning: 
Unexpected Signal 4 occured under user-defined signal handler 
0xdc6b9774Unexpected Signal 4 occured under user-defined signal handler 
0xdc6b9774

Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
lready in use:8080
LifecycleException:  Protocol handler initialization failed: 
java.net.BindException: Address already in use:8080
        at org.apache.coyote.tomcat4.CoyoteConnector.initialize
(CoyoteConnector.java:1175)
        at org.apache.catalina.core.StandardService.initialize
(StandardService.java:579)
        at org.apache.catalina.core.StandardServer.initialize
(StandardServer.java:2246)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:511)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.stop: LifecycleException:  This server has not yet been started
LifecycleException:  This server has not yet been started
        at org.apache.catalina.core.StandardServer.stop
(StandardServer.java:2213)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.start: LifecycleException:  Protocol handler initialization failed: 
java.net.BindException: Address already in use:8080
LifecycleException:  Protocol handler initialization failed: 
java.net.BindException: Address already in use:8080
        at org.apache.coyote.tomcat4.CoyoteConnector.initialize
(CoyoteConnector.java:1175)
        at org.apache.catalina.core.StandardService.initialize
(StandardService.java:579)
        at org.apache.catalina.core.StandardServer.initialize
(StandardServer.java:2246)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:511)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.stop: LifecycleException:  This server has not yet been started
LifecycleException:  This server has not yet been started
        at org.apache.catalina.core.StandardServer.stop
(StandardServer.java:2213)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(
        
        
--------------------------------------------------------------------------------
-----------------


PDF Query:select 
r_object_id,object_name,r_version_label,r_lock_owner,r_object_type,r_content_siz
e, a_content_type,r_is_virtual_doc,r_link_cnt,r_modify_date from ancillary_docs
(all) where i_chronicle_id in (select i_chronicle_id  from ancillary_docs(all) 
where r_object_id ='090047518000e434') and document_type='Jct PDF' order by 
r_version_label
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 11 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xdc6b9774


--------------------------------------------------------------------------------
------------------


Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 4 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xac6b9774
Java HotSpot(TM) Client VM warning: Unexpected Signal 10 occured under user-
defined signal handler 0xac6b9774


Please help out in finding where the problem may lie.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to