Sponsored Content
Operating Systems Solaris Java application getting killed automatically in Solaris Post 302200552 by ashish.nijai on Thursday 29th of May 2008 10:58:15 AM
Old 05-29-2008
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?
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Application getting killed after one day ??? Help !!!!

Hai , I am working on a system with unix and solaris 5.8 loaded. The problem is when I leave an application open for more than one day .. it gets killed .. and my one day work goes waste and I have to start all over again .. ??? Is there any way I can find out the maximum number of... (6 Replies)
Discussion started by: ajphaj
6 Replies

2. Shell Programming and Scripting

Doubt with How to run an application automatically?

Dear sir, I want to know if i shut-down my system and while starting it next time automatically one application starts running, Is there any way? I an using Suse linux OS. PLz Help me! (4 Replies)
Discussion started by: salil2012
4 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. Programming

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. ... (2 Replies)
Discussion started by: sm9ai
2 Replies

6. 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
init.wbem(1M)						  System Administration Commands					     init.wbem(1M)

NAME
init.wbem - start and stop the CIM Boot Manager SYNOPSIS
/etc/init.d/init.wbem start | stop | status DESCRIPTION
The init.wbem utility is run automatically during installation and each time the system is rebooted. This utility manipulates the CIM Object Manager (CIMOM) and the Solaris Management Console server, both of which run combined in a single process. init.wbem can be used to start, stop, or retrieve status from the server. CIM Object Manager The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a computer representation, or model, of a managed resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes. When a WBEM client application accesses information about a CIM object, the CIM Object Manager contacts either the appropriate provider for that object or the CIM Object Manager Repository. Providers are classes that communicate with managed objects to access data. When a WBEM client application requests data from a managed resource that is not available from the CIM Object Manager Repository, the CIM Object Manager forwards the request to the provider for that managed resource. The provider dynamically retrieves the information. At startup, the CIM Object Manager performs the following functions: o Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 5988. o Sets up a connection to the CIM Object Manager Repository. o Waits for incoming requests. During normal operations, the CIM Object Manager performs the following functions: o Performs security checks to authenticate user login and authorization to access namespaces. o Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification. o Routes requests to the appropriate provider or to the CIM Object Manager Repository. o Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications. A WBEM client application contacts the CIM Object Manager to establish a connection when it needs to perform WBEM operations, such as cre- ating a CIM class or updating a CIM instance. When a WBEM client application connects to a CIM Object Manager, it gets a reference to the CIM Object Manager, which it then uses to request services and operations. Solaris Management Console Server The Solaris Management Console server is the back end to the front end console, smc(1M). It provides tools for the console to download and performs common services for the console and its tools to use, such as authentication, authorization, logging, messaging, and persistence. System Booting The init.wbem script is installed in the /etc/init.d directory. OPTIONS
The following options are supported: start Starts the CIMOM and Solaris Management Console server on the local host. stop Stops the CIMOM and Solaris Management Console server on the local host. status Gets the status of the CIMOM and Solaris Management Console server on the local host. NOTES
When the init.wbem script is run, it does not run the CIMOM and Solaris Management Console server directly. The server process is in Java and is too heavyweight to be run immediately at system boot time. Instead, three lightweight processes listen on three different ports that the CIMOM and the Solaris Management Console server normally use. This acts similarly to inetd(1M). Because Java programs cannot inherit file descriptors as other programs can, there is a small time period from when the first connection is made until the server is fully operational where client connections may be dropped. WBEM clients are immune to this, as they will retry until the server comes online. Solaris Management Console clients are not immune, and it may be necessary to manually reconnect, though this should not happen in the common case. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWwbcor | +-----------------------------+-----------------------------+ SEE ALSO
inetd(1M), mofcomp(1M), smc(1M), smcconf(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5) SunOS 5.10 2 Jan 2002 init.wbem(1M)
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy