db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Kurley" <mark.kur...@activant.com>
Subject RE: Derby - sysinfo call hangs
Date Tue, 07 Feb 2006 19:02:05 GMT

-----Original Message-----
From: Stanley Bradbury [mailto:Stan.Bradbury@gmail.com] 
Sent: Tuesday, February 07, 2006 12:00 PM
To: derby-dev@db.apache.org
Subject: Re: Derby - sysinfo call hangs

Mark Kurley wrote:

>I was able to narrow it down some more.  If I put this call in a loop 
>it will eventually hang.
>org.apache.derby.drda.NetworkServerControl ping
>Does anyone have any ideas why this would sometimes hang?
>-----Original Message-----
>From: Mark Kurley [mailto:mark.kurley@activant.com]
>Sent: Tuesday, February 07, 2006 11:06 AM
>To: derby-dev@db.apache.org
>Subject: RE: Derby - sysinfo call hangs
>We are running this on AIX.  
>When the process hangs I try to send "kill -QUIT <pid>" to the process 
>but it just hangs.  I get an entry in the file /tmp/javacore_locations.
>For example it added the entry
>	/tmp/javacore45520.1139323327.txt
>But this core dump file does not exist.  The process continues to hang
>until I send "kill -9 <pid>".   So for some reason it seems like the
>process never receives the "kill -QUIT".
>Any suggestions on how I can figure out when the call to the "sysinfo"
>script hangs sometimes?
>-----Original Message-----
>From: Bryan Pendleton [mailto:bpendleton@amberpoint.com]
>Sent: Thursday, February 02, 2006 5:35 PM
>To: derby-dev@db.apache.org
>Subject: Re: Derby - sysinfo call hangs
>>I have noticed that sometimes when I call the "sysinfo" script the 
>>process hangs.
>You didn't mention what platform you are running, but you should be 
>able to get a Java Stack Trace showing all the threads in the sysinfo 
>process, and what they are waiting on:
>- On Windows, use Control-Break: Hold down the Control key and press
>   the Break key.
>- On Unix systems, send "kill -QUIT" to the process which is running
>   sysinfo, from some other window on that machine.
>Then, capture the output from the Java Stack Trace, and send it along.
>That will provide more information about where in the sysinfo script it

>is hanging.
It would be very helpful to know what messages are in the derby.log file
and to get the information provided by 'NetworkServerControl sysinfo' 
(when it does execute properly).  Once it hangs please try issuing
'NetworkServerControl runtimeinfo' - if this returns there may be useful
information - please post that  as well.  Lastly, when a hang happens is
the CPU quiet or very active?

Here is more information when I run the "NetworkServerControl ping"
command in a loop.  The process eventually hangs.  The CPU is quiet when
the process hangs.

1) Derby.log

Connection number: 2506.
Connection number: 2507.
Connection number: 2508.
Connection number: 2509.

2) Output from runtimeinfo when process hangs.

--- Cloudscape Network Server Runtime Information ---
---------- Session Information ---------------
Session # :2511

# Connection Threads : 3
# Active Sessions : 1
# Waiting  Sessions : 0

Total Memory : 5110272  Free Memory : 2476784

3) Here is the sysinfo when it executes properly....

--------- Cloudscape Network Server Information --------
Version: CSS10000/  Build: 30301  DRDA Product Id: CSS10000
-- listing properties --
------------------ Java Information ------------------
Java Version:    1.3.1
Java Vendor:     IBM Corporation
Java home:       /usr/java131/jre
Java classpath:
OS name:         AIX
OS architecture: ppc
OS version:      4.3
Java user name:  tomcat
Java user home:  /home/tomcat
Java user dir:   /turns/local/tpcx/bin
--------- Derby Information --------
[/turns/local/derby/lib/derby.jar] - (30301)
[/turns/local/derby/lib/derbynet.jar] - (30301)
[/turns/local/tomcat/webapps/spokeshopcs/WEB-INF/classes] -
----------------- Locale Information -----------------

Notice: This transmission is for the sole use of the intended recipient(s) and may contain
information that is confidential and/or privileged.  If you are not the intended recipient,
please delete this transmission and any attachments and notify the sender by return email
immediately.  Any unauthorized review, use, disclosure or distribution is prohibited.

View raw message