Transaction SM50 Shows 3 dialog process in yellow colure

Dear all,
I run transaction sm50 in that transaction 3 Dialog work process shows in yellow colure, what its mean please check the attached file for screen shot of SM50

In SM50, select that work process, then Process > Trace > Active Components. Check the value of the trace level. Put it back to "1" and the color should disappear.
http://help.sap.com/saphelp_erp2005vp/helpdata/EN/e4/981a013b2511d288d30000e83539c3/content.htm
Regards,
Jazz

Similar Messages

Dialog process hang and can not be cancelled

Hi Gurus,
In SM50, a dialog process was running with error. It was obviously hang, but I can't cancel it.
Everytime I use "cancel with core" or "cancel without core", the only thing changed was the PID. It changed a PID and kept running.
Even I logged into application server and kill the process in task manager, it would run again with a new process id?
Any idea how I can cancel it, Thanks.

You can try to logoff the user, but i am not sure if this will help.
I am a bit confused, could you please either share a screenshot, or just copy paste the text from SM50.
Something like this would be very helpful:
| No.|Ty.|PID |Status |Reasn|Start|Err|Sem|CPU| Time|Report                     |Cl.|User    |Action|Table|
|   5 |DIA|21149|Waiting|     |Yes |   |   |   |      |                           |   |        |      |     |
|   6 |DIA|5708 |Running|     |Yes |   |   |   |     1|GP4JPFULQXLNZRBMX8BN0FHIERD|603|User2   |      |     |
|   7 |DIA|964 |On Hold|Debug|Yes |   |   |   |   193|Z_BI_EXTRAKT_SCHMETRIX     |603|User1   |      |     |
|   8 |DIA|10115|Waiting|     |Yes |   |   |   |      |                           |   |        |      |     |
After each restart the Err count will increase, this is usual behavior.
Cheers Michael

Work processes in SM50 showing yellow

Dear all,
We are facing one issue in SM50 where some dialog work processes are turned to yellow status one after the other.
This yellow status means i believe trace level problem which is getting changed to 2 instead of 1(default value).
In order to revert back to1 in SM50, select the highlighted work process with yellow status then go to process---> trace ---> active components. Now new pop-up will occur with value as 2, select default values and then save which will remove yellow status against the highlighted work process.
Another way to get rid of this issue is with Application restart which we can't do every time / not recommended.
I have checked dev_disp & dev_wp<no> log files, but of no useful information in them and i have gone through various posts.
Now my query is why this trace level got changed to yellow with value of 2 instead of default value 1 and what will be the root cause behind this in order to avoid future issues.
Rgds,
Durga.

Hi Michael,
Thank you very much for those 2 SAP notes and few of my doubts got very much cleared with 998221.
Rgds,
Durga.

Function in update task goes to dialog process(seen by sm50)

Hi Forum,
I wrote a simple test to invoke a function module in update task, and the execution of the module takes several minutes (updating database using opensql) . The test looks simply like described in the following link:
http://www.****************/Tutorials/ABAP/Debug/Index.htm
During the run, I used transaction sm50 to view the working processes and expect to find a running "UPD" process. However it is not found, instead my dialog process is always seen running. Any hints on why?
Thanks,
Yang

got the answer. The reason is that sm50 can not display UPD process so promptly. For a more thorough tracing, transaction "stad" can be used. (where I see the DB access executed in UPD process)

How do I prevent all dialog processes in SM50 from being occupied?

Hi experts,
I have set rdisp/rfc_min_wait_dia_wp = 4 and I still saw all dialog processes got occupied.
(PS: This screenshot is captured after a few minutes). Anyway, how do I prevent all dialog processes in SM50 from being occupied?
Should I increase rdisp/rfc_min_wait_dia_wp ( = 4 now ) and rdisp/wp_no_dia ( = 18 now ) to a higher value?

Hi Gaurav & Nick,
If I understand correctly, there are 4 dialog processes running and 14 RFC running at the same time.
If I want to resolve this problem, I need to reduce paralellism of RFCs and increase dialog work processes, right? Here is my new configuration. Any thoughts?
new parameters:
rdisp/wp_no_dia = 20
rdisp/rfc_min_wait_dia_wp = 10
rdisp/rfc_check = 3
old parameters in profile:
rdisp/wp_no_dia = 18
rdisp/wp_no_btc = 13
rdisp/wp_no_enq = 0
rdisp/wp_no_spo = 2
rdisp/wp_no_vb = 5
rdisp/wp_no_vb2 = 2
rdisp/rfc_min_wait_dia_wp = 4
rdisp/rfc_check = DEFAULT (DEFAULT is 2, ASYNC and SYNC RFC)

Number of dialog process in SM50 does not tally RZ10

Hi,
I am encountering the above scenario whereby the number of dialog processes shown in SM50 is not the same as the profile parameters indicated in RZ10.
I have restated SAP several times and it's still the same - both doesn't tally.
Has anyone encountered the same? How was it resolved?
Thanks

Problem resolved.
Reimported the profile and restarted SAP.

Is it possible to show a processing dialog?

hi, everyone.
Is it possible to show a processing dialog when my scripts is executing?
Because my script will spend some times, this will help the designer to understand that the scripts is working now.
Thanks very much.

You may want to use a progressbar - there is an example in the ESTK Samples/javascript folder (see SnpCreateProgressBar.jsx)
Davide

Dialog process (loading)

Hello,
We have upgraded the system to BW2004s. Now when loading fom cube to cube. We get 2 dialog processes. Before we got only 1 dialog process.
Does anybody know how to select only 1 dialog proces during loading?
regards,
Jos.

<b>Rules -</b>
You cannot change the number of dialog processes directly. The number of dialog processes is calculated automatically from the total number of work processes minus all the other work processes.
There must always be at least 2 dialog processes. The number of other work process types can only be increased if there are more than two dialog processes.
<b>Transactions</b>
SM50 - To check how many DIA processes are available for you.
RZ04 - Is the transaction to configure the number of DIA processes need to be increased,done by BASIS ...
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a5ef8505211d189550000e829fbbd/content.htm
Hope it Helps
Chetan
@CP..

Dialog process

Hi ,
1) If dialog process show in priv mode status in sm50 ,how to trouble shoot and what action u need take?
2) If control files is crashed what will u do for that?
can anybody explan the issue asap
Regards
Sheeba

Hi
1) If MANY dialog process show in PRIV mode, that means the memory you configured is not sufficient. You need to review the memory configuration based your what kind of programs are running in the system. This is just a start point of troubleshooting memory. http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCSTMM/BCCSTMM.pdf is a start point for this.
2) I hope you are aware where to see that a control file is corrupted (Alert log). You can see where the control files located from init<SID>.ora and copy the corrupted with the one that is not corrupted. You may need to stop database to do that. I haven't encounted any such until now.
All the best,

All BW dialog processes occupied while loading

Hi,
All dialog processes (9) in BW are occupied at loading from the SCAPPTSEG table in CRM.
We do not have any problem with other loads.
Has anybody a solution for this?
rgds,
Marcel

Hi Van,
Its not a good practice to kill the job in production.
First check if the PID for that particular process is progressing or waiting for the gate way of some other reason.
this you can check in SM50 - local work process overview of the systems.
Also check for the system log in SM21 transaction...
check if there are any short dumps...
capture all the inforamtion and check with BASIS if the PID is processing or not and if not processing and HUNG you can take help of BASIS to Kill the PID. the process will be terminated.
Regards
KP

Number of dialog processes at any host

Hi Friends,
I need to find how many dialog processes are in use at any time at any host. My desire is the programatically of sm51.
How do I do?
Thanks.

Hi!
It's better, if you check the transaction SM50. You can see all dialog (DIA) proceses here.
Regards
Tamá

Is there any way to run abap program in dialog process with process chain?

Hi.
I just want to run custom abap program in every 30min.
so I made process chain and connect abap program.
but it returns NOTHING when background running.
the program has ABSOLUETLY no problem when it's running DIALOG process.
custom program is modified from sap standard program for my use.
so complicated and hard to read that I cann't figure out what's problem in backgound job and even hard to debug in background process.
is there any way to run abap program in dialog process in every 30 min.?
or call BSP page or call function.
any solution will be helpful that excuting PROGRAM or FUNCTION or BSP PAGE in schedule job and should running dialog process.
thanks.
Lee.

Hi,
did you try using sm36 transaction?
1Give these values in Gereral data
Create one sample job "SAMPLE JOB"
Priority "A"
Execu target - Your application server
2Click start conditon
schedule according to ur requirements.
3.Click Step button
Give your ABAP program name.
fill variants if it has any variants.
if it is useful assign points
Regard,
Senthil Kumar.P

IDOC performance: increase amount dialog processes on XI site?

Hi everybody,
we got performance problems while sending (many) IDocs to XI.
Is it recommended to incease the amount of dialog processes?
If yes: Which transaction is to be used?
Thanks you!
Regards Jochen
null

Hi,
there are notes which discuss Idoc perfromance and how to improve the same.
Refer into them .
Note : 760993 , 709400 , 761332
Regards
Bhavesh

"DEADLOCK" when showing dialog from RMI-callback.

Hi!
Today is the 10th day (full time) that I've been searching for a solution in Java Forums and Internet, but I couldn't find anything that helps me. Help is extremely appreciated, otherwise I'll go crazy! :-)
The problem is that RMI-callback thread "somehow blocks" the Event Dispatch Thread.
I want to do following:
1) I push the button in the client (btDoSomething)
(MOUSE_RELEASED,(39,14),button=1,modifiers=Button1,clickCount=1 is automatically pushed onto EventQueue)
2) btDoSomethingActionPerformed is invoked
3) inside of it I make a call to RMI-server (server.doSomething())
4) from this server method I invoke RMI-callback back to the client (client.askUser())
5) in the callback I want to display a question to the user (JOptionPane.showConfirmDialog)
6) user should answers the question
7) callback returns to server
8) client call to the server returns
9) btDoSomethingActionPerformed returns and everybody is happy :-)
This works normally in normal Client, that means, while a button is pushed, you can show Dialogs, but with RMI callback I get problems.
I just made a small client-server sample to simulate real project. What I want to achieve is that client invokes server method, server method does something, but if server method doesn't have enough information to make the decision it needs to do call back to the client and wait for input, so the user gets an JOptionPane.
Here is my callback method:
    /** this is the remote callback method, which is invoked from the sevrer */
    public synchronized String askUser() throws java.rmi.RemoteException {
        System.out.println("askUser() thread group: " + Thread.currentThread().getThreadGroup());
        System.out.println("callback started...");
        try {
            SwingUtilities.invokeLater(new Runnable() {
                public void run() {
                    System.out.println("My event started...");
                    JOptionPane.showConfirmDialog(parentFrame, "Are you OK?", "Question", JOptionPane.YES_NO_OPTION);
                    System.out.println("My event finished.");
        }catch (Exception e) {
            e.printStackTrace();
        try {
            Thread.currentThread().sleep(10000);
        }catch (Exception e) {
            e.printStackTrace();
        System.out.println("callback finished.");
        return "Yo!"; // just return anything
    }Here in this sample I let the callback thread sleep for 10 seconds, but in real project I let it sleep infinitely and I want to wake it up after the user has answered JOptionPane. But I have the DEADLOCK, because event queue is waiting for callback to finish and doesn't schedule the "showing dialog" event which contains the command for waking up the callback thread.
I looked very precisely when the event queue starts again to process events: it is precisely then when btDoSomethingActionPerformed is finished.
When I'm not accessing GUI inside of the callback, this callback mechanism works perfectly, but as soon as I want to show the dialog from inside of the RMI-callback method, the "AWT Event Dispatch Queue" is somehow frozen until RMI-callback thread is finished (and in turn btDoSomethingActionPerformed terminates) . I cannot explain this weird behaviour!!!
If I don't use SwingUtilities.invokeLater (I know this shoudn't be done outside of Event Dispatch Thread), but access the GUI directy, my JOptionPane is shown, but is not painted (it is blank gray) until callback thread returns.
Why showing (or painting) of dialog is not done until btDoSomethingActionPerformed is finished?
I also tried to spawn a new Thread inside of main RMI-callback thread, but nothing changed.
I also tried the workaround from some older posting to use myInvokeLater:
    private final static ThreadGroup _applicationThreadGroup = Thread.currentThread().getThreadGroup();
    public void myInvokeLater(final Runnable code) {
        (new Thread(_applicationThreadGroup, new Runnable() {
            public void run() { SwingUtilities.invokeLater(code); }
        ).start();
    }but this didn't help either.
Then I tried to spawn a new Thread directly from the Client's constructor, so that I'm sure that it belongs to the main appplication thread group. I even started that thread there in the constructor and made it wait for the callback. When callback came in, it would wake up that sleeping thread which should then show the dialog. But this did't help either.
Now I think that it is IMPOSSIBLE to solve this problem this way.
Spawning a new Process could work I think, but I'm not really sure if I want do to that.
I know I could make a solution where server method is invoked and if some information is missing I can raise custom exception, provide the input on client side and call the same server mathod again with this additional data, but for that I need to change server RMI interfaces, etc... to fit in this concept. I thought callback would much easier, but after almost 10 days of trying the callback...I almost regreted it :-(
Is anyone able to help?
Thank you very much!
Please scroll down for the complete sample (with build and run batch files), in case someone wants to try it. Or for the time being for your convenience you can download the whole sample from
http://www.onlineloop.com/~tornado/download/rmi_callback_blocks_gui.zip
######### BEGIN CODE ####################################
package callbackdialog;
public interface ICallback extends java.rmi.Remote {
    public String askUser() throws java.rmi.RemoteException;
package callbackdialog;
public interface IServer extends java.rmi.Remote {
    public void doSomething() throws java.rmi.RemoteException;
package callbackdialog;
import java.rmi.Naming;
public class Server {
    public Server() {
        try {
            IServer s = new ServerImpl();
            Naming.rebind("rmi://localhost:1099/ServerService", s);
        } catch (Exception e) {
            System.out.println("Trouble: " + e);
    public static void main(String args[]) {
        new Server();
package callbackdialog;
import java.rmi.Naming;
public class ServerImpl extends java.rmi.server.UnicastRemoteObject implements IServer {
    // Implementations must have an explicit constructor
    // in order to declare the RemoteException exception
    public ServerImpl() throws java.rmi.RemoteException {
        super();
    public void doSomething() throws java.rmi.RemoteException {
        System.out.println("doSomething started...");
        try {
            // ask the client for the "missing" value via RMI callback
            ICallback client = (ICallback)Naming.lookup("rmi://localhost/ICallback");
            String clientValue = client.askUser();
            System.out.println("Got value from callback: " + clientValue);
        }catch (Exception e) {
            e.printStackTrace();
        System.out.println("doSomething finished.");
package callbackdialog;
import java.rmi.server.RemoteStub;
import java.rmi.server.UnicastRemoteObject;
import java.rmi.registry.Registry;
import java.rmi.registry.LocateRegistry;
import java.rmi.Naming;
import javax.swing.JOptionPane;
import javax.swing.SwingUtilities;
import javax.swing.JFrame;
public class Client extends javax.swing.JFrame implements ICallback {
    private final JFrame parentFrame = this;
    private Registry mRegistry = null;
    private RemoteStub remoteStub = null;
    private IServer server = null;
    private final static ThreadGroup _applicationThreadGroup = Thread.currentThread().getThreadGroup();
    /** Creates new form Client */
    public Client() {
        initComponents();
        System.out.println("Client constructor thread group: " + Thread.currentThread().getThreadGroup());
        try {
            server = (IServer)Naming.lookup("rmi://localhost/ServerService");
            // register client to the registry, so the server can invoke callback on it
            mRegistry = LocateRegistry.getRegistry("localhost", 1099);
            remoteStub = (RemoteStub)UnicastRemoteObject.exportObject((ICallback)this);
            Registry mRegistry = LocateRegistry.getRegistry("localhost", 1099);
            mRegistry.bind("ICallback", remoteStub);
        }catch (java.rmi.AlreadyBoundException e) {
            try {
                mRegistry.unbind("ICallback");
                mRegistry.bind("ICallback", remoteStub);
            }catch (Exception ex) {
                // ignore it
        }catch (Exception e) {
            e.printStackTrace();
    /** This method is called from within the constructor to
     * initialize the form.
     * WARNING: Do NOT modify this code. The content of this method is
     * always regenerated by the Form Editor.
    private void initComponents() {
        java.awt.GridBagConstraints gridBagConstraints;
        secondTestPanel = new javax.swing.JPanel();
        btDoSomething = new javax.swing.JButton();
        getContentPane().setLayout(new java.awt.GridBagLayout());
        setDefaultCloseOperation(javax.swing.WindowConstants.DISPOSE_ON_CLOSE);
        setTitle("RMI-Callback-GUI-problem sample");
        addWindowListener(new java.awt.event.WindowAdapter() {
            public void windowClosing(java.awt.event.WindowEvent evt) {
                formWindowClosing(evt);
        secondTestPanel.setLayout(new java.awt.GridBagLayout());
        btDoSomething.setText("show dialog");
        btDoSomething.addActionListener(new java.awt.event.ActionListener() {
            public void actionPerformed(java.awt.event.ActionEvent evt) {
                btDoSomethingActionPerformed(evt);
        gridBagConstraints = new java.awt.GridBagConstraints();
        gridBagConstraints.gridx = 0;
        gridBagConstraints.gridy = 3;
        gridBagConstraints.insets = new java.awt.Insets(10, 0, 0, 0);
        secondTestPanel.add(btDoSomething, gridBagConstraints);
        gridBagConstraints = new java.awt.GridBagConstraints();
        gridBagConstraints.gridx = 0;
        gridBagConstraints.gridy = 1;
        gridBagConstraints.fill = java.awt.GridBagConstraints.BOTH;
        gridBagConstraints.weightx = 1.0;
        gridBagConstraints.weighty = 1.0;
        getContentPane().add(secondTestPanel, gridBagConstraints);
        pack();
    private void btDoSomethingActionPerformed(java.awt.event.ActionEvent evt) {
        System.out.println(java.awt.EventQueue.getCurrentEvent().paramString());
        try {
            server.doSomething(); // invoke server RMI method, which will do the client RMI-Callback
                                  // in order to show the dialog
        }catch (Exception e) {
            e.printStackTrace();
    private void formWindowClosing(java.awt.event.WindowEvent evt) {
        try {
            mRegistry.unbind("ICallback");
        }catch (Exception e) {
            e.printStackTrace();
        setVisible(false);
        dispose();
        System.exit(0);
    /** this is the remote callback method, which is invoked from the sevrer */
    public synchronized String askUser() throws java.rmi.RemoteException {
        System.out.println("askUser() thread group: " + Thread.currentThread().getThreadGroup());
        System.out.println("callback started...");
        try {
            SwingUtilities.invokeLater(new Runnable() {
                public void run() {
                    System.out.println("My event started...");
                    JOptionPane.showConfirmDialog(parentFrame, "Are you OK?", "Question", JOptionPane.YES_NO_OPTION);
                    System.out.println("My event finished.");
        }catch (Exception e) {
            e.printStackTrace();
        try {
            Thread.currentThread().sleep(10000);
        }catch (Exception e) {
            e.printStackTrace();
        System.out.println("callback finished.");
        return "Yo!"; // just return anything
     * @param args the command line arguments
    public static void main(String args[]) {
        java.awt.EventQueue.invokeLater(new Runnable() {
            public void run() {
                Client client = new Client();
                client.setSize(500,300);
                client.setVisible(true);
    // Variables declaration - do not modify
    private javax.swing.JButton btDoSomething;
    private javax.swing.JPanel secondTestPanel;
    // End of variables declaration
1_build.bat
javac -cp . -d . *.java
rmic callbackdialog.ServerImpl
rmic callbackdialog.Client
pause
2_RunRmiRegistry.bat
rmiregistry
pause
3_RunServer.bat
rem java -classpath .\ Server
java callbackdialog.Server
pause
4_RunClient.bat
java callbackdialog.Client
pause
######### END CODE ####################################

I can understand that only partially, because SwingUtilities.invokeLater puts(redirects) my runnable object directly into AWT thread. The only conclusion I can draw from all things that I have tried until now , is that SwingUtilities.invokeLater(<showing the dialog>) invoked from a RMI thread somehow have lower "priority" than events coming directly from the AWT-thread and therefore it is held back until normal awt event completes (in this case BUTTON_RELEASED).
But what I don't understand is the fact that the dialog is not shown even If I create and start a new thread from the client's constructor. This thread has nothing to do with RMI as it is in the main thread group:
    private BlockingObject dialogBlocker = new BlockingObject();
    private BlockingObject blocker = new BlockingObject();
    public Client() {
        initComponents();
        (new Thread() {
            public void run() {
                try {
                    dialogBlocker.sleep(0);
                    System.out.println("My event started...");
                    JOptionPane.showConfirmDialog(parentFrame, "Are you OK?", "Question", JOptionPane.YES_NO_OPTION);
                    blocker.wake();
                    System.out.println("My event finished.");
                }catch (Exception e) {
                    e.printStackTrace();
        }).start();
        ...Callback is then only used to wake up this thread which should display the dialog:
    public Object askUser() throws java.rmi.RemoteException {
        System.out.println("callback started...");
        dialogBlocker.wake();
        blocker.sleep(0);
        System.out.println("callback finished.");
        return userChoice; // return anything I don't care for now
class BlockingObject {
    public void sleep(long timeout) {
        synchronized(this){
            try {
                wait(timeout);
            }catch (InterruptedException e) {}
    public void wake() {
        synchronized(this){
            notifyAll();
    }In this case the dialog is shown, but it is NOT painted, so I have deadlock again. Why it is not painted?!?
Haven't I uncouple it from RMI-Thread?
But perhaps I'm looking at the wrong side of the whole thing.
If I invoke server.doSomething (as ejp proposed) in a separate thread, then everything is fine (except that I cannot use this solution in my project :-( ).
It seems that the whole problem is NOT AT ALL related to callback itself, but rather to the fact that if client invokes remote call, even dialogs can't be shown until the rmi call returns to the client.
Thank you, Drindilica

RFC Dialog process

Hi Experts.
I know that RFC always runs in a dialog process.
I am slightly confused on one thing - Lets say we call an asynchronous RFC via system A and it is calling System B.
The RFC will occupy dialog process in System A or in System B or in both the systems?
Thanks in adv.

As per help.sap.com
Using Asynchronous Remote Function Calls
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
·        When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
·        Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
·        The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functionu2019s result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
I think until calling server establishes connection with called server it will be using dialog server and then it may use the same dialog process for some other task as it doesn't need to wait for results.once again after receiving the results it uses the dialog process(correct me if i am wrong)
Thanks
Bala Duvvuri

Transaction SM50 Shows 3 dialog process in yellow colure

Similar Messages

Maybe you are looking for