Sponsored Content
Top Forums Programming Java application dying randomly Post 302490186 by sm9ai on Monday 24th of January 2011 07:10:32 AM
Old 01-24-2011
Java application dying randomly

Hi,

(First post, please be gental!)

I have a java app that I am running on unix (centos)

But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days.

I have a cronjob running to restart it when ever it dies but I would rather this happened less often.

Is there anyway to find out the reason why it died?

Thanks

Matt
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

java application holds lot of disk space

Hi, I am running a java application in unix box to process 20000 files. Each file sizes around 300 bytes. Application keep polls the input folder and moves to the respective output folders. The disk partition sizes 5GB. df -k shows only 900 mb free while running the application. When I stop the... (0 Replies)
Discussion started by: balajilinks
0 Replies

2. Solaris

Java application getting killed automatically in Solaris

Hi to all, I have developed a Java application for Solaris 10. I am uing JDK 5. But it is getting killed after some time. And at the terminal, I got message as Killed. I am new to Solaris. Can anybody help me? (3 Replies)
Discussion started by: ashish.nijai
3 Replies

3. UNIX and Linux Applications

sun java application server 8.2

i had a confusion on the installed directory of my application server a. if I create a domain w/o putting in directory, the domain automatically goes to /var/appserver/domains directory. I need it to be under /opt/SUNWappserver/domains.. If I will include this in domain creation, may logs are... (0 Replies)
Discussion started by: lhareigh890
0 Replies

4. Programming

First Java Application

Hello all, This is my first java application since college (years ago..) What it basically needs to do, is verify that it can connect to a server, and once it is connected, run a series of AIX commands to verify that certain processes are running, and if they aren't running, it needs to start... (1 Reply)
Discussion started by: jeffs42885
1 Replies

5. Solaris

Java Application slowness with Xmanager

Hi! I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this? Thanks, Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies
ELVPRSV(8)						      System Manager's Manual							ELVPRSV(8)

NAME
elvprsv - Preserve the the modified version of a file after a crash. SYNOPSIS
elvprsv ["-why elvis died"] /tmp/filename... elvprsv -R /tmp/filename... DESCRIPTION
elvprsv preserves your edited text after elvis dies. The text can be recovered later, via the elvprsv program. For UNIX-like systems, you should never need to run this program from the command line. It is run automatically when elvis is about to die, and it should be run (via /etc/rc) when the computer is booted. THAT'S ALL! For non-UNIX systems such as MS-DOS, you can either use elvprsv the same way as under UNIX systems (by running it from your AUTOEXEC.BAT file), or you can run it separately with the "-R" flag to recover the files in one step. If you're editing a file when elvis dies (due to a bug, system crash, power failure, etc.) then elvprsv will preserve the most recent ver- sion of your text. The preserved text is stored in a special directory; it does NOT overwrite your text file automatically. elvprsv will send mail to any user whose work it preserves, if your operating system normally supports mail. FILES
/tmp/elv* The temporary file that elvis was using when it died. /usr/preserve/p* The text that is preserved by elvprsv. /usr/preserve/Index A text file which lists the names of all preserved files, and the names of the /usr/preserve/p* files which contain their preserved text. BUGS
Due to the permissions on the /usr/preserve directory, on UNIX systems elvprsv must be run as superuser. This is accomplished by making the elvprsv executable be owned by "root" and turning on its "set user id" bit. If you're editing a nameless buffer when elvis dies, then elvprsv will pretend that the file was named "foo". AUTHOR
Steve Kirkendall kirkenda@cs.pdx.edu ELVPRSV(8)
All times are GMT -4. The time now is 01:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy