Process not getting killed

Hi ,
I tried killing the process but still it is not getting killed.Used the below command.
kill -9 <pid>
sapkxdap10:orads2 9> ps -ef | grep sap
sidadm 25255 1 0 Sep21 ? 01:00:18 dw.sapSID_DVEBMGS68 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS68_sapkxdap10
I cannot understand what the second field means question mark is there.How to kill the process if they are hung.Thanks.

> How should i proceed even after stopping sap if the process exists?
I don't know - I have no clue under which circumstances something that like can occur. You can check using
ipcs -m
if there are any shared memory segments allocated. Also stop/kill "saposcol" and "sapstartsrv".
> And what does that question mark indicate in the output..Thanks.
Execute
man ps
The question mark means the process has no connected terminal (just read the headline when you execute ps -ef) and was started by another process.

Similar Messages

BPM Process not getting started

Dear All,
I have created a BPM Process, and have attached a webservice with the start event.After deploying the Process DC I am getting my start webservice in my wsnavigator. When I am executing the start webservice I am getting the following error.
Web service returned error. Fault Code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Process start has been triggered."
But my process is inprogress but not getting proceeded to the next step , it is stuck in start itself.
how can i make my webservice work?
Regards,
Shamila

Hi Shamila,
To me this looks like a configuration issue. You can trouble shoot it this way
First try to check if the web services is up and running
Second check your configuration, for this, in NWA Manage Processes application get all the 'failed processes'
-check if your in-progress process is listed here-
- if so then open the Error log tab for the process in the details section in Manage Process
- See the logs listed here; generally the last log will tell you if your configuration is correct or not
-if you figure out that the configuration isn't done or is improper then correct the same in provider systems and/or application communication configuration
- then once this is done, re-query the failed process and use the "Recover" option
Regards,
Harsha

Process Not Getting EXITED

BATCH FILE
LOCATION : D:\test.bat
Ex: test.bat It contains
del c:\sample.txt
JAVA FILE
LOCATION : c:\testunion.java
import java.util.*;
import java.io.*;
public class testunion
public static void main(String args[])
     try
          Runtime objRt = null;
          Process objProc = null;
          objRt = Runtime.getRuntime();
          String szIntfFile = "D:\\test.bat";
          objProc = objRt.exec(szIntfFile);
ENVIRONMENT : WINDOWS 2k
When testunion.java file is RUN, test.bat is called and sample.txt gets deleted.
BUT THE CONTROL IS NOT COMING OUT FROM THE COMMAND PROMPT.THE CURSOR STAYS IN THE
COMMAND PROMPT BLINKING.
I think the sub Process is not getting EXITED.....
I want the subprocess to execute and get exited. so that the Main Process does not hang...
How to do it ?

Even though the docs say the methods of Process are abstract you can use them because you are really using java.lang.ProcessImpl
I believe you need to provide a sink for the process's InputStream to your testunion(better practice TestUnion)
        try
            Runtime objRt = null;
            Process objProc = null;
            objRt = Runtime.getRuntime();
            String szIntfFile = "c:\\jar MathML-X.cmd";
            objProc = objRt.exec(szIntfFile);
            java.io.InputStream is=objProc.getInputStream();
            int value=0;
            StringBuffer sb=new StringBuffer();
            while((value=is.read())!=-1)
                if(value==10)
                System.out.println(sb.toString());
                sb.setLength(0);
                else
                sb.append((char)value);
            objProc.waitFor();
        catch(java.io.IOException ioe)
            System.out.println("ioe: "+ioe.getMessage());
        catch(java.lang.InterruptedException ie)
            System.out.println("ie: "+ie.getMessage());

Java engine (server0 process) not getting started.

Hi All,
I am not able to start java engine. Y'day I changed the password of SAPJSF user in portal side. Server0 process is not getting started from y'day. Error message is like below. Can any one help me in this area?
=====================================================================================
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)
        at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.getAttributes(R3JCo640Proxy.java:408)
        at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.doInitRfc(R3PersistenceBase.java:689)
        at com.sap.security.core.persistence.datasource.imp.R3Persistence.localInitialization(R3Persistence.java:277)
        at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:424)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
        at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
        at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
        at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
=====================================================================================
Thanks & Regards,
Charanjit Singh.

Hi Anil,
This time I face new problem. Error log is below.
==================================================================
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
        at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:77)
        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:402)
        at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:81)
        at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:57)
        at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:135)
        at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
============================================================================
Thanks & Regards,
Charanjit Singh,

Methodology/Processes Not getting reflected while creating a role via BRM in GRC

Hello All,
The methodology I have created is not getting reflected while creating a new Single role.
I have maintained the condition groups properly in decision table, and assigned the same to the methodology as well.
Please suggest.
Thanks
Regards,
Shruti

Methodology is updated when you press save after completing the first step.
can you please share screen shots of configuration and issue you are getting

Java API - EventHandler threads not getting killed

Hello everybody,
I didn't know whether to post this in the PI forum or in the MDM forum. I use the following scenario:
We run an EJB session bean in the Java Proxy environment of PI 7.1. In this bean we create an MDM session, log on to a repository and then attach a RecordListener that reacts to any change of the records. When an interesting change took place, the record is distributed to PI.
The code looks like this:
EventDispatcher evDis = new EventDispatcher(servername);
RecordListener recLis = new RecordListener();
evDis.registerDataNotifications(username, password, repIdent, regions[0]);
evDis.addListener(recLis);
The problem arises when we try to undeploy or stop the application. You would assume that it would stop everything connected to the application. However, it does not. The mentioned EventDispatcher creates a thread object when invoked, and this thread is never killed. The consequence: Records keep getting distributed as if nothing had happened, although the application is gone (even undeploying doesn't help). But when we redeploy the application, a new thread is created. So after some development you get 10 or more threads firing every change to PI. The only thing that helps is a restart of the J2EE engine.
So, my question: Has anybody here made a similar experience? Is this common for MDM or is rather PI the cause of this issue?
Any comments on that are very welcome.
Best regards,
Jörg

Hi Veera,
thanks a lot, that pot me on the right track! In fact, it's the @PreDestroy annotation which has to be used for some cleanup method. When we execute this and included the coding you mentioned the threads are killed properly.
Currently we're facing the issue that somehow the commit status of the bean is not set to "Committed" and from the second message on we get exceptions. If anybody came across this, help is appreciated.
Best regards,
Jörg

Process not getting correlated and going into manual recovery stage

Hi
I have developed a bpel process which implements correlation. I have unit tested it and is working fine. But am encountering issues in case of load.
The process which should correlate to the running process is going into manual recovery and the correlation is not happening. Whenever is restart the managed server, and then recover the instance things are getting completed and correlation is happening.
Can some one suggest what might be the problem in this case
Thanks in advance

Sumit,
This occurs because your process has not dehydrated to the dehydration store yet.
The process has not failed but it is waiting for a response from some partner link in your BPEL process. This can be common when calling async ESBs and the ESB fails.
To try and debug this you will need to look at the domain.log and see if any error is generated. Have a look at your BPEL process and see what partner link cal cause a failure yet not send a response back.
Is the DB adapter the only partner link or are there others?
cheers
James

Enqueue process not getting start after failover

Hi Experts,
We are facing problem suddenly after doing failover test. This problem arrived today only. Before it was happening successfully.
Before failover everything is running fine on primary node. After doing failover the enqueue sever process on ASCS instance is not starting in secondary node.
It's also showing license will expire on 16.11.2010, but system has
already license installed.
The ASCS start logs are showing as below -
Execute Pre-Startup Commands
(12517410) Local: /usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/scs.lst
(11534542) system(/usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/scs.lst) returns 4
(12517412) Local: /usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/sapcrypto.lst
(11534542) system(/usr/sap/PRD/SYS/exe/run/sapcpe pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1 list:/usr/sap/PRD/SYS/exe/run/sapcrypto.lst) returns 255
(12517414) Local: rm -f ms.sapPRD_ASCS00
(12517416) Local: ln -s -f /usr/sap/PRD/ASCS00/exe/msg_server ms.sapPRD_ASCS00
(12517418) Local: rm -f en.sapPRD_ASCS00
(12517420) Local: ln -s -f /usr/sap/PRD/ASCS00/exe/enserver en.sapPRD_ASCS00
Starting Programs
24.10.2010 18:39:42
ShmDetach
OK
(12517424) Starting: local ms.sapPRD_ASCS00 pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1
(8585426) Starting: local en.sapPRD_ASCS00 pf=/usr/sap/PRD/SYS/profile/PRD_ASCS00_sapprd1
(11534542) Waiting for Child Processes to terminate.
(11534542) **** 2010/10/24 18:39:42 Child 8585426 terminated with Status 1 . ****
(8585426) **** 2010/10/24 18:39:42 No RestartProgram command for program 1 ****
It's unable to start enqueue server process.
Please suggest your solutions.
Regards,
Ramesh.

Hi Gagan,
The enqueue problem is resolved. Atually 2 days before we increased RAM of primary node by 1GB, and that was creating issue. we revert it back and again did a switchover and everything is running fine. It was strange that my secondary node is getting affected due to increasing the RAM in primary node.
Regarding license key, can you please provide me detail steps to resolve it. I have gone through installation doc but couldnt find it. Now Tcode slicense is showing another hardware key in my DI system. Do I need to get seperate permenant license key for DI by registering DI host and new hardware key??
Just confirm and also add some of your expert suggetsions.
Regards,
Ramesh.
Edited by: ramesh_basis on Oct 25, 2010 7:26 AM

UPMDbEngine process not getting started .

Hi
I am using LMS 3.1 . After installing the HUM 1.0 i am getting the ERROR "Cannot connect to the database.
Either the UPMDbEngine process is down or the connection pool is exhausted. " <Please find the screen shot attached >
Tried restarting the UPMDbEngine process and found the service is getting stoped automatically.
Attached the < UPMProcess.log > and < UPMDbMonitor.log >
Can any one please help me in getting the issue resolved .
Thanks in advance .
Regards
Angus

HI
I am attaching the PDshow and the Syslog output ..

Ipconfig command (ran thru the process) not getting terminated

We are working on a web based application that requires running ipconfig /all command as a process from Java class to fetch the MAC address.
Using the tool called "handle.exe", what we have found is that even after the process is destroyed, the ipconfig process exists & eventually there are lots of such handles for ipconfig.
We are using jdk 1.4.2_03 with tomcat 4.1.27. I am copying the piece of code below to give an idea of what we are doing:
Runtime runtime = Runtime.getRuntime();
proc = runtime.exec( "ipconfig /all" );
BufferedReader reader = new BufferedReader(new InputStreamReader(proc.getInputStream()));
try
String line;
// On Windows, read multiple lines until the Physical Address is found
while ((line = reader.readLine()) != null)
// logic to retrieve the MAC address from the output above
catch (IOException e)
// print the message
proc.destroy();
Any help/pointers will be appreciated.
Thanks in advance.. SDM

I've found the same problem with a similar peice of code.
One thing you can do to reduce the leakage is to explicitly close the process object's input, output & error streams, but that still leaves a leak of one handle per exec call.
This does seem to be an ipconfig thing rather than a java thing as I don't get the same leak with other commands.
I used the free process explorer from http://www.sysinternals.com/ when investigating this problem

Conky does not get killed!

If I start a terminal, run the command
conky
and then exit the terminal, then conky appears again after a few seconds?! How is this possible? All terminals do create a pseudo terminal, which should kill all processes, when it is closed!
Last edited by ying (2011-10-21 12:14:59)

Yes, but I am programming a login manager and my goal is to save time. So I don't want to restart X. All is functioning. Only this conky . I just have seen, that the output of ps -A tells me, that conky runs in a pty (ex.: pty/0). If I stop the pty, it changes to an '?'. So before I close the pseudo terminal, I could collect all processes, which do run in the pty and then kill them.
Edit: But there is a problem. How do I know, which new created ptys (New Terminals started in the DE) are belonging to the the main pseudo terminal process?
Edit2: Conky is ignoring the SIGHUP Signal, when the process session leader sends it out. But I could scan the pids and check their parent pids. That should work.
Last edited by ying (2011-10-21 19:03:31)

Process not getting long filename support

I am trying to run a makefile through the runtime.exec. I am using 1.4.0 on WinNT The error I am getting is consistent to errors caused by lack of long filename support. I have lfnload.com on the machine, so I can install long filename support.
If anyone has any suggestions I am open to them.
thanks for any help in advance,
Geoff

Does anyone have any idea about this?

Process getting killed automatically

Hi
I am using jdk 1.5 and java processes are getting killed automatically on server. Processes were working on test servers. Is anybody facing the same issue or knowledge about the same.
Regards,
Niraj

Niraj,
Can you explain your scenario a bit more clearer.?
Mandrake

Sapstart process not running

Hi all,
We were trying to stop SAP using stopsap command.But it failed saying that instance has already been stopped.
Enviroment linux red hat release 4 and oracle 10.0.2.0.5.
When checked we found out that the sapstart process is not running.Checked the work directory and there is no kill.sap file also.
Reboot would do the trick, but we wanted to know if there is a way to shutdown sap.Oracle has been shutdown using shutdown abort.
i tried using kill -2 <pid> but still the process are not getting killed.Thanks.

Hello,
normally a SAP system ist stopped by a kill -2 on the dispatcher (the parent of all work processes) which is done by sapstart or in sapstartsrv. If this does not work check the dispatcher trace or open a message on the SAP Market Place.
Please do not use kill -9. The SIGKILL closes the process directly. All open I/Os are kept open and also all child processes. A kill -6 (SIGABORT) should work as well.
Best regards,
Klaus

Killing child process, not just the shell

Killing child process, not just the shell
#241 - 07/11/03 11:30 AM
Edit post Edit Reply to this post Reply Reply to this post Quote
Hi,
I am working on a system for automatically testing student submissions on an introductory course about unix scripting. The program works by running a test script on a student submission, using Runtime.getRuntime().exec(). The Process object has a limited life span of 10 seconds (by default), and if it is still running after these 10 seconds, Process.destroy() is used to kill it.
A bug exists when one of the submissions being tested times out. When the destroy() method is used it leaves a child process running... since students can also run
some tests from the file submission client, the number of hanging processes soon adds up as they test and test again to get it right before submission. Eventually this results in too many processes and the server keels over.
Does anyone have any ideas on killing these hanging processes?

Not much help, but I think this is a known bug ...
http://developer.java.sun.com/developer/bugParade/bugs/4770092.html

Process not getting killed

Similar Messages

Maybe you are looking for