Problem in background session processing

Hi Experts,
I am performing BDC by batch input session method.
I acheved BDC by traditional recording method and able to create batch input session in SM35.
Whenever I process batch input session in FOREGROUND it processes successfully.But whenever I processes it in BACKGROUND it throws an exception
runtime error.
This recording is for transaction CK74.this transaction screen contains some table controls.Error is "Control Framework: fatal error: GUI cannot be reached".
Please let me know if anybody has solution for this.
Thanks,
Yogesh.

Hi yogesh,
    I think u might be using the function module upload or ws_upload to upload the data to the internal table. Try to use GUI_UPLOAD, while processing the session on background.
I think it will solve ur problem.
Regards...
Arun.
Reward points if useful.

Similar Messages

  • Error occurs in background work process.

    Respected Guru's,
    error occurs in two background work process, i have displayed the trace files of both the bgd work process.
    How to rectify this error ?
    Further, can you please help me in identifying the problem, please suggest me good material which gives steps for troubleshooting such error in the developer's and system trace.
    Thank you.
    Dayanandan.a
    Developer trace file for BGD WP 1
    trc file: "dev_w12", trc level: 1, release: "620"                                             
    ACTIVE TRACE LEVEL           1                                                             
    ACTIVE TRACE COMPONENTS      all, M                                                        
    M  systemid   560 (PC with Windows NT)                                                        
    M  relno      6200                                                                            
    M  patchlevel 0                                                                               
    M  patchno    251                                                                             
    M  intno      20020600                                                                        
    M  pid        2864                                                                            
    M                                                                               
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc12 2864) [dpxxdisp.c   1016]                      
    M  <EsNT> Memory Reset enabled as NT default                                                  
    M  calling db_connect ...                                                                     
    M  db_connect o.k.                                                                            
    M  rdisp/reinitialize_code_page -> 0                                                       
    M                                                                               
    M Tue Jul 30 10:22:53 2002                                                                    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M                                                                               
    M Tue Jul 30 10:22:55 2002                                                                    
    M  *** ERROR => SlicLockSema: sema locked [slicshm.c    89]                                   
    M  *** ERROR => SlicShmInit: SlicLockSema failed [slicshm.c    231]                           
    M  *** ERROR => SlicValBufInit: cannot initialize SHM [slicshm.c    299]                      
    M  *** ERROR => SlicValBufRead: license buffer not initialized [slicshm.c    329]             
    M  *** ERROR => SlicCheckBuf: some error reading license buffer contents [slicshm.c    419]   
    M                                                                               
    M Wed Jul 31 00:00:49 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M Thu Aug 01 00:00:49 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD                       
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                       
    M                                                                               
    M Fri Aug 02 00:00:49 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                       
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD                       
    M                                                                               
    M Fri Aug 02 00:14:09 2002                                                                               
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  235]  
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]                                           
    M  ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]                                                  
    M  in_ThErrHandle: 1                                                                               
    M  *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]              
    M                                                                               
    M  Info for wp 12                                                                               
    M                                                                               
    M    stat = 4                                                                               
    M    reqtype = 4                                                                               
    M    act_reqtype = 4                                                                               
    M    tid = 12                                                                               
    M    mode = 0                                                                               
    M    len = 24                                                                               
    M    rq_id = 6638                                                                               
    M    rq_source = 1                                                                               
    M    last_tid = 12                                                                               
    M    last_mode = 0                                                                               
    M    rfc_req = 0                                                                               
    M    report = >                                        <                                                         
    M    action = 16                                                                               
    M    tab_name = >                              <                                                                 
    M   
    M                                      
    M  Modeinfo for User T12/M0            
    M                                      
    M    tm state = 2                      
    M    uid = 13                          
    M    term type = 0x0                   
    M    display = 0x0                     
    M    cpic_no = 0                       
    M    cpic_idx = -1                     
    M    usr = >SAPUSER     <              
    M    terminal = >                    < 
    M    client = >800<                    
    M    conversation_ID = >        <      
    M    appc_tm_conv_idx = -1             
    M    imode = 3                         
    M    mode state = 0x42                 
    M    th_errno = 9                      
    M    async_receives = 0                
    M    cpic_receive = 0                  
    M    em handle = 2                     
    M    roll state = 4                    
    M    abap state = 4                    
    M    em state = 3                      
    M    eg state = 1                      
    M    lock = 0                                                                               
    Developer's trace file for BGD WP 2
    trc file: "dev_w13", trc level: 1, release: "620"                                             
    ACTIVE TRACE LEVEL           1                                                             
    ACTIVE TRACE COMPONENTS      all, M                                                        
    M  systemid   560 (PC with Windows NT)                                                        
    M  relno      6200                                                                            
    M  patchlevel 0                                                                               
    M  patchno    251                                                                             
    M  intno      20020600                                                                        
    M  pid        2872                                                                            
    M                                                                               
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc13 2872) [dpxxdisp.c   1016]                      
    M  <EsNT> Memory Reset enabled as NT default                                                  
    M                                                                               
    M Tue Jul 30 10:21:44 2002                                                                    
    M  calling db_connect ...                                                                     
    M  db_connect o.k.                                                                            
    M                                                                               
    M Tue Jul 30 10:22:25 2002                                                                    
    M  rdisp/reinitialize_code_page -> 0                                                       
    M                                                                               
    M Tue Jul 30 10:22:53 2002                                                                    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M                                                                               
    M Wed Jul 31 00:00:52 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020730.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M                                                                               
    M Thu Aug 01 00:00:49 2002                                                                    
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020731.AUD    
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                      
    M                                                                               
    M Fri Aug 02 00:00:51 2002                                                                               
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020801.AUD                      
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020802.AUD                      
    M                                                                               
    M Fri Aug 02 00:14:09 2002                                                                               
    M  *** ERROR => ThCallHooks: event handler rsts_before_commit for event BEFORE_COMMIT failed [thxxtool3.c  235] 
    M  ***LOG R38=> ThICommit3, db_commit98 ( 001024) [thxxhead.c   10641]                                          
    M  ***LOG R18=> ThPrivCommit, ThICommit () [thxxhead.c   11307]                                                 
    M  in_ThErrHandle: 1                                                                               
    M  *** ERROR => ThPrivCommit: ThICommit (step 4, th_errno 9, action 2, level 1) [thxxhead.c   8277]             
    M                                                                               
    M  Info for wp 13                                                                               
    M                                                                               
    M    stat = 4                                                                               
    M    reqtype = 4                                                                               
    M    act_reqtype = 4                                                                               
    M    tid = 13                                                                               
    M    mode = 0                                                                               
    M    len = 24                                                                               
    M    rq_id = 6643                                                                               
    M    rq_source = 1                                                                               
    M    last_tid = 13                                                                               
    M    last_mode = 0                                                                               
    M    rfc_req = 0                                                                               
    M    report = >                                        <                                                        
    M    action = 16                                                                               
    M    tab_name = >                              <                                                                
    M                                                                               
    M  Modeinfo for User T13/M0                                                                               
    M                                                                               
    M    tm state = 2                      
    M    uid = 14                          
    M    term type = 0x0                   
    M    display = 0x0                     
    M    cpic_no = 0                       
    M    cpic_idx = -1                     
    M    usr = >SAPUSER     <              
    M    terminal = >                    < 
    M    client = >800<                    
    M    conversation_ID = >        <      
    M    appc_tm_conv_idx = -1             
    M    imode = 3                         
    M    mode state = 0x42                 
    M    th_errno = 9                      
    M    async_receives = 0                
    M    cpic_receive = 0                  
    M    em handle = 3                     
    M    roll state = 4                    
    M    abap state = 4                    
    M    em state = 3                      
    M    eg state = 1                      
    M    spa state = 3                     
    M    enq state = 0                     
    M    next hook = T-1/U-1/M255          
    M    master hook = T-1/U-1/M255        
    M    slave hook = T-1/U-1/M255         
    M    debug_tid = -1                    
    M    mode type = 0x1                   
    M    debug = 0                         
    M    lock = 0                          
    M                                      
    M                                      
    M Sat Aug 03 00:00:55 2002
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
    M                                                                               
    M Sun Aug 04 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020803.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
    M                                                                               
    M Mon Aug 05 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020804.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
    M                                                                               
    M Tue Aug 06 00:00:49 2002                                                                
    M  SecAudit(check_daily_file): audit file closed E:\usr\sap\SER\DVEBMGS00\log\20020805.AUD
    M  SecAudit(check_daily_file): audit file opened E:\usr\sap\SER\DVEBMGS00\log\20020806.AUD

    Thank you, Bhaskar,
    I have performed consistency check for temse objects and all the comments are displayed in red color.
    Does it mean that objects are inconsistent. But, no comments states that object are inconsistent.
    I have attached the comments displayed,
    Consistency check of table TST01 / TemSe objects
    This comment occurs repeatedly, Unable to access the related file           Length = 0
    Incorrect number of data lines in TST03              
    Object with part number 1 missing
    Object reset                     Length = 0
    The related file has an incorrect length
    Consistency check of table TST03 / TemSe data
    No object found in TST01
    May i delete all objects, as all the comments are red in color.
    Dayanandan.A

  • How to find out number of background work processe available in the system?

    Hi All,
    I have a FM that triggers a background job using JOB_OPEN, ABAP_SUBMIT and JOB_CLOSE. But the problem is if there are no background work processes available at that moment, it does not return error. Not sure whether the job is even scheduled!
    Is there a way to find out if there are any background work processes available in the system? I know a FM SPBT_INITIALIZE which gives info about dialog work processes. Is there any other FM similar to this which gives info about background wp??
    Regards,
    Shailesh

    your Job will remain in a queue by message handler. once workprocess is free, your job gets scheduled
    by the way, you can use the functionality used in FM TH_DISPLAY_WORKPROCESS_LIST to read the workprocesses
    the command which gets you the workprocess is:
    CALL 'ThWpInfo' ID 'OPCODE' FIELD OPCODE_WP_LIST
                      ID 'TAB' FIELD LIST_STATE_WPLST-TABL
                      ID 'CPU' FIELD LIST_STATE_WPLST-CPU.
    check how its written in include LSDEBF01, form SET_LIST_WPLST
    Edited by: Soumyaprakash Mishra on Dec 12, 2011 12:17 PM

  • Problem in bdc session method for tcode FS00

    Hi Experts,
    problem in bdc session method, when i run this program no output is shown.
    Even it is not calling the transaction.
    code as follows.
    *& Report  Z_GL_MASTER
    *& CATEGORY         =  BDC.
    *& DESCRIPTION      =  UPLOADING G/L MASTER RECORDS.
    *& TECHNICAL CONST  =  FRANCIS REDDY.
    *& FUNTIONAL CONST  =  FICO.
    REPORT  Z_GL_MASTER.
    *& Internal  Table
    DATA : BEGIN OF IT_UPLOAD OCCURS 0,
           SAKNR LIKE  GLACCOUNT_SCREEN_KEY-SAKNR,          " ACCOUNT NUMBER.
           BUKRS LIKE  GLACCOUNT_SCREEN_KEY-BUKRS,          " COMPANY CODE.
           KTOKS LIKE GLACCOUNT_SCREEN_COA-KTOKS,           " ACCOUNT GROUP.
           XPLACCT LIKE GLACCOUNT_SCREEN_COA-XPLACCT,       " P&L STATEMEMENT.
           GVTYP LIKE  GLACCOUNT_SCREEN_COA-GVTYP,          " P&L STATEMENT TYPE.
           XBILK LIKE GLACCOUNT_SCREEN_COA-XBILK,           " BALANCE SHEET STATEMENT
           SHORT LIKE GLACCOUNT_SCREEN_COA-TXT20_ML,        " SHORT TEXT.
           LONG LIKE GLACCOUNT_SCREEN_COA-TXT50_ML,         " LONG TEXT.
           WAERS LIKE GLACCOUNT_SCREEN_CCODE-WAERS,         " ACCOUNT CURRENCY.
           XSALH LIKE GLACCOUNT_SCREEN_CCODE-XSALH,         " ONLY BALANCES IN LOCAL CURRENCY.
           MITKZ LIKE GLACCOUNT_SCREEN_CCODE-MITKZ,         " RECONCILATION ACCOUNT FOR ACCOUNT TYPEGLACCOUNT_SCREEN_CCODE-MITKZ
           XOPVW LIKE GLACCOUNT_SCREEN_CCODE-XOPVW,         " OPEN ITEM MANAGEMENT.
           XKRES LIKE GLACCOUNT_SCREEN_CCODE-XKRES,         " LINE ITEM DISPLAY.
           ZUAWA LIKE GLACCOUNT_SCREEN_CCODE-ZUAWA,         " SORT KEY.
           FSTAG LIKE GLACCOUNT_SCREEN_CCODE-FSTAG,         " FIELD STATUS GROUP.
           XGKON LIKE GLACCOUNT_SCREEN_CCODE-XGKON,         " RELAVENT CASH FLOW.
           END OF IT_UPLOAD.
    *& Internal  Table FOR BDC DATA.
    DATA : IT_BDCDATA TYPE  BDCDATA OCCURS 0  WITH HEADER LINE.
    *& DATA DECLARATIONS.
    DATA : V_FILE LIKE RLGRAP-FILENAME.
    *&  SELECTION SCREEN.
    PARAMETER : P_FILE LIKE V_FILE.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
         PERFORM GET_FILENAME.
    START-OF-SELECTION.
          PERFORM UPLOAD_DATA.
          PERFORM BDCDATA_OPEN.
          PERFORM BDC_POPULATE.
          PERFORM BDC_CLOSE.
    *&      Form  GET_FILENAME
    form GET_FILENAME .
      CALL FUNCTION 'F4_FILENAME'
       EXPORTING
         PROGRAM_NAME        = SYST-CPROG
         DYNPRO_NUMBER       = SYST-DYNNR
         FIELD_NAME          = 'P_FILE'
       IMPORTING
         FILE_NAME           = P_FILE.
    endform.                    " GET_FILENAME
    *&      Form  UPLOAD_DATA
    form UPLOAD_DATA .
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
       FILENAME                      =  P_FILE
       FILETYPE                      = 'DAT'
      TABLES
        data_tab                     = IT_UPLOAD.
    endform.                    " UPLOAD_DATA
    *&      Form  BDCDATA_OPEN
       FORM FOR BDC_OPEN_GROUP.
    form BDCDATA_OPEN .
    CALL FUNCTION 'BDC_OPEN_GROUP'
    EXPORTING
       CLIENT                    = SY-MANDT
       GROUP                     = 'GLMASTER'
       HOLDDATE                  = SY-DATUM
       KEEP                      = 'X'
       USER                      = SY-UNAME.
    endform.                    " BDCDATA_OPEN
    *&      Form  BDC_POPULATE
      POPULATING BDC DATA .
    form BDC_POPULATE .
    loop at it_upload.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING 'BDC_OKCODE' '=ACC_CRE'.
    PERFORM BDC_SUB2 USING 'BDC_CURSOR' 'GLACCOUNT_SCREEN_KEY-SAKNR'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_KEY-SAKNR'    IT_UPLOAD-SAKNR.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_KEY-BUKRS'    IT_UPLOAD-BUKRS.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING 'BDC_OKCODE' '=2102_GROUP'.
    PERFORM BDC_SUB2 USING 'BDC_CURSOR' 'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-KTOKS'    IT_UPLOAD-KTOKS.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-XPLACCT'  IT_UPLOAD-XPLACCT.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING 'BDC_OKCODE' '=2102_BS_PL'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-GVTYP'    IT_UPLOAD-GVTYP.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-XBILK'    IT_UPLOAD-XBILK.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING 'BDC_CURSOR' 'GLACCOUNT_SCREEN_COA-TXT20_ML'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-TXT20_ML' IT_UPLOAD-SHORT.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_COA-TXT50_ML' IT_UPLOAD-LONG.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING  'BDC_OKCODE' '=TAB02'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-WAERS'  IT_UPLOAD-WAERS.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-XSALH'  IT_UPLOAD-XSALH.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'  IT_UPLOAD-MITKZ.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'  IT_UPLOAD-XOPVW.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-XKRES'  IT_UPLOAD-XKRES.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'  IT_UPLOAD-ZUAWA.
    PERFORM BDC_SUB1 USING 'X' 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_SUB2 USING 'BDC_OKCODE' '=TAB03'.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-FSTAG' IT_UPLOAD-FSTAG.
    PERFORM BDC_SUB2 USING 'GLACCOUNT_SCREEN_CCODE-XGKON' IT_UPLOAD-XGKON.
    CALL FUNCTION 'BDC_INSERT'
      EXPORTING
        TCODE                  = 'FS00'
       TABLES
         dynprotab              = IT_BDCDATA.
    endloop.
    endform.                    " BDC_POPULATE
    *&      Form  BDC_CLOSE
    FORM FOR CLOSING BDC_GROUP
    form BDC_CLOSE .
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    endform.                    " BDC_CLOSE
    *&      Form  BDC_SUB1
       FORM FOR BDCDATA.
    form BDC_SUB1   USING  A  B  C.
    CLEAR  IT_BDCDATA.
    IT_BDCDATA-DYNBEGIN = A.
    IT_BDCDATA-PROGRAM =  B.
    IT_BDCDATA-DYNPRO =   C.
    APPEND IT_BDCDATA.
    endform.                    " BDC_SUB1
    *&      Form  BDC_SUB2
          text
    form BDC_SUB2   USING  A  B.
    CLEAR  IT_BDCDATA.
      IT_BDCDATA-FNAM = A.
      IT_BDCDATA-FVAL = B.
      APPEND IT_BDCDATA.
    endform.                    " BDC_SUB2
    Points will be  rewarded.
    Thanks in advance.
    Francis.

    Hi,
    Once the program is executed..It will a BDC session..
    THen you have to use the transaction SM35..To process the BDC session..
    Thanks,
    Naren

  • A simple problem with sateful Session beans

    Hi,
    I have a really novice problem with stateful session bean in Java EE 5.
    I have written a simple session bean which has a counter inside it and every time a client call this bean it must increment the count value and return it back.
    I have also created a simple servlet to call this session bean.
    Everything seemed fine I opened a firefox window and tried to load the page, the counter incremented from 1 to 3 for the 3 times that I reloaded the page then I opened an IE window (which I think is actually a new client) but the page counter started from 4 not 1 for the new client and it means that the new client has access to the old client session bean.
    Am I missing anything here???
    Isn�t it the way that a stateful session bean must react?
    This is my stateful session bean source.
    package test;
    import javax.ejb.Stateful;
    @Stateful
    public class SecondSessionBean implements SecondSessionRemote
    private int cnt;
    /** Creates a new instance of SecondSessionBean */
    public SecondSessionBean ()
    cnt=1;
    public int getCnt()
    return cnt++;
    And this is my simple client site servlet
    package rezaServlets;
    import java.io.*;
    import java.net.*;
    import javax.ejb.EJB;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import test.SecondSessionRemote;
    public class main extends HttpServlet
    @EJB
    private SecondSessionRemote secondSessionBean;
    protected void processRequest (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    response.setContentType ("text/html;charset=UTF-8");
    PrintWriter out = response.getWriter ();
    out.println("<html>");
    out.println("<head>");
    out.println("<title>Servlet main</title>");
    out.println("</head>");
    out.println("<body>");
    out.println("<h1>Our count is " + Integer.toString (secondSessionBean.getCnt ()) + "</h1>");
    out.println("</body>");
    out.println("</html>");
    out.close ();
    protected void doGet (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    processRequest (request, response);
    protected void doPost (HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
    processRequest (request, response);
    }

    You are injecting a reference to a stateful session bean to an instance variable in the servlet. This bean instance is shared by all servlet request, and that's why you are seeing this odd behavior.
    You can use type-leve injection for the stateful bean, and then lookup the bean inside your request-processing method. You may also save this bean ref in HttpSession.
    @EJB(name="ejb/foo", beanName="SecondBean", beanInterface="com.foo.foo.SecondBeanRemote")
    public MyServlet extends HttpServlet {
    ic.lookup("java:comp/env/ejb/foo");
    }

  • A problem with a session Access

     

    Hi Olivier,
    To connect with Forte while running distributed you must use System DNS
    instead of User DNS on the server. The ftexec.exe on your server partition
    will be launched by the NodeMgr running as UID SYSTEM. User DNS are not
    available to processes running as UID SYSTEM.
    Zenon Adamek
    Purolator
    -----Original Message-----
    From: Olivier Andrieux [SMTP:oandrieuxaxialog.fr]
    Sent: Tuesday, July 04, 2000 4:59 AM
    To: forte-userslists.xpedior.com
    Subject: (forte-users) A problem with a session Access
    Hi,
    We have defined a service object which calls a database Access, when we
    use the driver odbc of another station the service object is created and
    the application runs. But when we use the driver of the server we have an
    exception and this message :
    SYSTEM ERROR: Unable to start the partition AxiGecom_CL0_Part1 on any of
    the
    nodes to which it has been assigned. See the remainder of the error
    stack for
    more information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method InterfaceManager.PrepareLOM
    Error Time: Tue Jul 04 10:50:19
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9:0x2, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9:0x2.15]) in application
    "FTLaunch_cl0", pid 149 on node STAT10 in environment axialog.
    SYSTEM ERROR: Unable to start partition AxiGecom_CL0_Part1 on node
    SERVEUR59B.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Tue Jul 04 10:50:19
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9:0x2, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9:0x2.15]) in application
    "FTLaunch_cl0", pid 149 on node STAT10 in environment axialog.
    SYSTEM ERROR: Attempt to load partition named AxiGecom_CL0_Part1 failed.
    Class: qqsp_ResourceException
    Error #: [1001, 4]
    Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    Error Time: Tue Jul 04 10:49:15
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_cl0_Client",
    (partitionId =
    EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9:0x2, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3f9.4]) in application
    "FTLaunch_cl0", pid 149 on node STAT10 in environment axialog
    Exception occurred (remotely) on partition "Forte_Executor",
    (partitionId
    = EB3ED870-274C-11D4-8051-304F7116AA77:0x3de, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3de.61]) in application
    "AxiGecom_cl0", pid 386 on node SERVEUR59B in environment axialog.
    SYSTEM ERROR: Failed to create service object
    Axigecom_Serveur.Connection_BD.
    Class: qqsp_ResourceException
    Last TOOL statement: method qqsp_NameList.
    Error Time: Tue Jul 04 10:49:15
    Exception occurred (remotely) on partition "Forte_Executor",
    (partitionId
    = EB3ED870-274C-11D4-8051-304F7116AA77:0x3de, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3de.61]) in application
    "AxiGecom_cl0", pid 386 on node SERVEUR59B in environment axialog.
    USER ERROR: (This error was converted)
    Failed to connect to database: Axigecom, username: Administrateur.
    [Microsoft][Gestionnaire de pilotes ODBC] Source de donn&eacute;es non
    trouv&eacute;e et
    nom
    de pilote non sp&eacute;cifi&eacute;
    Class: qqdb_RemoteAccessException with ReasonCode:
    DB_ER_DBMSCONNECTION
    DBMS SQLSTATE: IM002
    Class: qqsp_ErrorDescriptor
    Detected at: qqdb_OdbcVendorInfo::DoSQLConnect at 10
    Last TOOL statement: method qqsp_NameList.
    Error Time: Tue Jul 04 10:49:15
    Exception occurred (remotely) on partition "Forte_Executor",
    (partitionId
    = EB3ED870-274C-11D4-8051-304F7116AA77:0x3de, taskId =
    [EB3ED870-274C-11D4-8051-304F7116AA77:0x3de.61]) in application
    "AxiGecom_cl0", pid 386 on node SERVEUR59B in environment axialog.
    for information, we use a server NT and the stations use Nt, the drivers
    DNS users are declared.
    We use Access2000, and the version M for Fort&eacute;
    Thanks in advance,
    Olivier Andrieux
    AXIALOG
    France

  • How to shedule an abap report to run paralely in more background session

    I wander how to shedule an abap report to run paralely in more background session.
    I am afraid of parallel locking.

    Hi,
    You can schedule different jobs with same program name.
    Use ENQUEUE_ & DEQUEUE_ to lock/unlock the records being process. The lock objects can be created in SE11.
    Best regards,
    Prashant

  • Transaction ME21n (Will not run as a BACKGROUND SESSION)

    The requirement is to generate Purchase Orders (Stock Transport Orders to be precise).
    The RFC has to create a session which will be executed...say...before midnight to generate the sto (TC -> SM35).
    I have used BDC inside my RFC calling the transaction ME21n. It runs fine as a foreground session, but will give a error if the session is run as a background session (Due to the dropdown lists in ME21n I guess).
    The solution I figured out is to use ME21. This does execute in the background successfully.
    But given the fact that ME21 is the OLD transaction and ME21n (enjoy sap transaction, right?) to be the one to be used now, my dilemma is in choosing ME21 and risk the scenario of this transaction being obsolete and not supported the SAP for technical support in the future.
    Can any body please help me on this.
    Thank you.
    Message was edited by: Sai Sanathan

    hello,
    with transaction VL10BATCH you can create new variants, and shedule background jobs. This should work.
    However, you need another user role. (on the last tab of the selection screen of VL10B)
    It is the F code profile you have to change. With this profile you can choose whether a list needs to be shown, or whether the deliveries have to be created right away (without showing the list). The second option should work in background. After delivery creation, you can check the   log using transaction V_SA.
    So you need to create a selection variant with changed user-role for the backround job.
    You can maintain user-roles via transaction VL10CUA.
    You can input-enable user-role via transaction VL10CUV.
    If you don't want the users to be able to run VL10B without showing the list, you have to create your own scenario, and use VL10X to start this scenario. Although this is not really necessary.
    I hope this makes things more clear for you.
    regards,
    Joris.
    Here is a copy of the OSS-note (310022) I was talking about:
    Symptom                                                                               
    o  For regular planning, you want to transfer the delivery creation
           in a job to the system administration. Here, you have           
           difficulties.                                                                               
    o  Background processing of Transaction VL10* does not generate    
           deliveries but only a list in the spool.                                                                               
    Additional key words                                                   
    VL10BATCH, VL10A, VL10B, VL10C, VL10D, VL10E                                                                               
    Cause and prerequisites                                                
    Solution                                                               
    For planning the delivery creation in background processing you must                                                                               
    o  activate a user role for immediate creation of deliveries (in the
           standard system, the immediate delivery creation is deactivated 
           for all user roles for reasons of safety),                                                                               
    o  create a selection variant for one of Transactions VL10*.                                                                               
    Activation of the user role for background processing                  
    The user role controls the entire processing of the delivery list.     
    Within Transactions VL10*, you can display and maintain the user role on
    the "User role" tab page. You can carry out the maintenance also via   
    Transaction VL10CUA. Note 301578 describes how to make a user role ready
    for input.                                                             
    An F-code profile is linked to the user role. The F-code profile       
    controls the internal process of the transaction. Two F-code profiles  
    are provided in the standard system:                                                                               
    o  0001 Display delivery list                                                                               
    o  5001 Supply delivery list                                                                               
    In the user role you want to use for background processing, you have to
    replace F-code profile (not "AllowedDialogFCodes") 0001 with profile   
    5001:                                                                               
    1.  Call Transaction VL10CUA for maintenance of the user roles.                                                                               
    2.  You might want to copy one of standard user roles 5001 to 5103 that
        is planned for processing in the background to a separate role in 
        the customer namespace, for example, 9001 or Z***.                                                                               
    3.  Branch to the detail view of the user role and change the entry for
        the F-code profile from "Display delivery list" to "Supply delivery
        list".                                                                               
    Creation of the selection variant                                                                               
    1.  Call the desired Transaction VL10* and branch to the "User role" ta
        page. Do not use Transaction SE38 or VL10BATCH for variant        
        maintenance of VL10*.                                                                               
    2.  Here, enter the user role that you have maintained for background 
        processing.                                                       
        Caution! If you use a user role with an F-code profile for the    
        immediate creation of deliveries, you receive no dialog with a    
        shipping due list but the deliveries are created immediately at the
        start of the selection!                                                                               
    3.  Enter the remaining selection criteria on the various other tab   
        pages.                                                                               
    4.  Select function "Goto -> Variants -> Save as variant..." and save 
        the selection criteria entered as a variant. You might classify the
        variant as "Only for background processing", in order to avoid a  
        start of the delivery creation in the dialog by mistake.                                                                               
    5.  Make sure that the objects of selection screen 1060 have been saved
        and that checkboxes "Save field without values" are not filled with
        all objects (in particular in Release 4.6B) for the desired       
        settings.                                                                               
    You can schedule the selection variant via Transaction VL10BATCH for  
    regular use in the batch.                                             
    And also the OSS-note (301578) about input-enabling user-role:
    SAP Note No. 301578                          22.08.2005           Page 1
    Number              301578                                              
    Version             4 from 08.05.2000                                   
    Status              Released for Customer                               
    Set on              08.05.2000                                                                               
    Language            EN                                                  
    Master language     DE                                                  
    Short text          VL10: Ready to input status of user role                                                                               
    Responsible         SAP AG                                              
    Component           LE-SHP-DL                                           
                        Delivery Processing                                 
    Long text                                                                               
    Symptom                                                                 
    On the selection screen of transaction family VL10*, the selection      
    criteria in the 'user role' tab are no longer ready for input of Release
    4.6C.                                                                               
    They are delivered in the standard SAP system not ready for input.                                                                               
    Additional key words                                                                               
    Cause and prerequisites                                                 
    As of Release 4.6C, the ready for input status in the 'user role' tab is
    linked to settings in the scenario and the user role.                                                                               
    1.  In order to get the ready for input status for the "Role" field, set
        "Allow assignment" to 'X' in the scenario that you are using        
        (Transaction VL10CUV or SM31, V_T186V, T186V-ALLOW_USER_ROLE = 'X').                                                                               
    The system administrator (Customizing authorization) can then       
        determine whether only the user role preset in the system is allowed
        or whether any number of other user roles may also be used for this 
        scenario.                                                                               
    2.  For the check box "Use list profile" and therefore all possible                                                                               
    settings for the "user role" tab, the ready for input status in the
        user role can be allowed in "Chang. attrbute" (changeability of the
        attributes).                                                       
        Set this field with Transaction VL10CUA for the used user role to  
        'X' (Transaction VL10CUA, or SM31, V_T186, t186-CHANGE_ALLOW = 'X').
    Background:                                                                               
    The settings in the scenario and user role have in the course of time  
    become so wide-ranging and far-reaching that an additional feature had 
    to be implemented: a system administrator must be able restrict the    
    changes by the end user at different levels .                                                                               
    You now have the option of determining for every user role whether that
    settings determined on the selection screen may be changed again.      
    You also have the option of determining in every scenario in which this
    user role is used whether the change is allowed for another user role.                                                                               
    In the context of the fixed link of the scenario to a transaction and  
    therefore to the authorization concept of mySAP.com - user-roles can be
    controlled at user level - whether the settings for the user role tab of
    the selection screen of VL10* may be changed by a user or not.                                                                               
    Solution                                                               
    Maintain setting in scenario (VL10CUV) and user role (VL10CU)          
    (Customizing authorization required).

  • Session processing in BDC

    when u r processing a session in error mode , how to come out of that session processing without processing all error recods?when iam using the ' /bend' , it is taking me out of the processing but stiill some transaction are there in background processing . how to free the all transactions?
    Thanks in advance.

    Hi,
    Do it manually, in SM35 T.code, Goto   System-servicesBatchinput---cancel.

  • Session Process

    Hi All,
    What are the problems in processing batch input sessions? 
    How is batch input process different from processing online? 
    Thanks in advance..
    Anshu,,

    Hi Anshu,
    i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains).  However if session is processed we may delete it manually.
    ii)if session processing fails data will not be transferred to SAP database table
    I think it ll help u..
    if satisfied rewards me..
    Kind Regards
    Yogesh

  • IllegalStateException: Internal Servlet Session Process Error Found!

              I keep getting the annoying error as listed, and the server also keeps reporting
              that I can only connect from 0 unique ip addresses. Has anybody else seen these
              type of frustrations on 8.1 sp2, or can explain them.
              With as much detail omitted for simplicity;
              Frustration 1.
              I have a 8sp2 server running all ok, occasionally after a redeploy of an ear file
              I attempt to load a jsp file, and the error below is thrown.
              The JSP has a bean which is session based, and as from following the stack trace
              it is around some weblogic code which tests if my license allows access to the
              http session (on a developer license). I then have to start another server instance
              and do a deployment of a v.simple war, and access this, then deploy the same war
              to the broken server and access that, then the initial jsp works fine. no code
              changes just environment stops, starts and redeploys!
              Frustration 2
              Server runs ok, tray and connect from two machines (I have an ldap server that
              wants to 'broadcast' messages to my server), error of too many connections.
              The ip connection issues can in most cases be removed with a server restart.
              EXCEPTION TRACE
              java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
              With the following stack trace:
              java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
                   at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
                   at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
                   at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
                   at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

              I have the same problem. Could any one help us?
              "David" <[email protected]> wrote:
              >
              >I keep getting the annoying error as listed, and the server also keeps
              >reporting
              >that I can only connect from 0 unique ip addresses. Has anybody else
              >seen these
              >type of frustrations on 8.1 sp2, or can explain them.
              >
              >With as much detail omitted for simplicity;
              >
              >Frustration 1.
              >I have a 8sp2 server running all ok, occasionally after a redeploy of
              >an ear file
              >I attempt to load a jsp file, and the error below is thrown.
              >
              >The JSP has a bean which is session based, and as from following the
              >stack trace
              >it is around some weblogic code which tests if my license allows access
              >to the
              >http session (on a developer license). I then have to start another
              >server instance
              >and do a deployment of a v.simple war, and access this, then deploy the
              >same war
              >to the broken server and access that, then the initial jsp works fine.
              > no code
              >changes just environment stops, starts and redeploys!
              >
              >Frustration 2
              >Server runs ok, tray and connect from two machines (I have an ldap server
              >that
              >wants to 'broadcast' messages to my server), error of too many connections.
              >The ip connection issues can in most cases be removed with a server restart.
              >
              >
              >EXCEPTION TRACE
              >
              >java.lang.IllegalStateException: Internal Servlet Session Process Error
              >Found!
              >
              >With the following stack trace:
              >
              >java.lang.IllegalStateException: Internal Servlet Session Process Error
              >Found!
              >     at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
              >     at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
              >     at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
              >     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
              >     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
              >     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
              >     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              >     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
              >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              >
              

  • Unable to connect - v$session.process property...

    I recently needed to move my DB instance - including SQL Developer - to another location (simply copied the entire Oracle Home). Everything went smoothly - DB runs fine - no issues. All client applications work fine as well - except for SQL Developer.
    SQL Developer has no problem launching or locating user preferences - however it simply can not connect to any database (not just the local db instance). The following error is thrown: "Status: Failure - Connection Property: format error: Property is 'v$session.process' and value is '[email protected]'"
    I'm using Oracle 11g on Oracle Enterprise Linux 5. SQL Developer version 1.2.0.
    Thanks.

    Hi ,
    I encountered the same issue.
    ++++++++++++++++
    Status: Failure - Connection Property: format error: Property is 'v$session.process' and value is '[email protected]'
    ++++++++++++++++
    and how do you solve the issue?
    what is the meaning of "Moving to SQL Developer 1.5 "???
    hope your quich reply.....
    Best Regards....

  • When connecting Apple devices to your iPhones wireless hotspot do those devices stop background data processes to conserve data?

    When connecting Apple devices to your iPhones wireless hotspot do those devices stop background data processes to conserve data?
    In other words if you have a limited data plan on your iPhone will your other Apple devices such as an iPad automatically cease background data transfers to conserve data usage?

    Nice trick to connect your Apple Devices to your wireless network.
    Will help the users if they are facing the problem with the apple devices.

  • Background SNP processes

    hello.
    im trying to shedule an event to run everyday. The event (deletion of records according to sysdate) is automatically executed in the background.
    i have submitted a job in the job queue using code:
    variable jobno number;
    execute DBMS_JOB.SUBMIT(:jobno, 'deleteexpiredads;', SYSDATE, 'SYSDATE + 1/96');
    im aware that the system must be altered to disable the restriction on my session to allow background SNP processes to execute the jobs in queue. This is done using:
    ALTER SYSTEM DISABLE RESTRICTED SESSION;
    For some reason the job is never executed. If i force the job to run it works fine but otherwise its not picked up.
    can anybody please help ?
    null

    thank you, got it working, much appretiated.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by jlehman ([email protected]):
    the job_queue_processes parameter must be set to a positive value in your init.ora file (bounce db reqd).
    this parameter tells oracle how many oracle background processes to keep running.
    the job_queue_interval parameter tells the processes how often to keep checking the queue for jobs to run.<HR></BLOCKQUOTE>
    null

  • Have problem in payables accounting process

    Hi all,
    i have faced a problem in the PAP process.Actually after matching with Po and made pay in full ,i ran the PAP(payables accounting process).but it is completed with warning.when i check the log file it send the following error message.please help me out to solve the problem.
    MSG MSG-00002: Check that AX is not installed before calling the accounting engine
    MSG MSG-00003: AX is not installed, Calling the accounting engine
    MSG MSG-00004: After the call to AP_Accounting_Engine_Pkg.Do_Accounting
    MSG MSG-00005: Error occured in the accounting process
    MSG MSG-00006: Error Message: ORA-20100: File o0039034.tmp creation for FND_FILE failed.
    You will find more information on the cause of the error in request log. occurred in
    &CALLING_SEQUENCE
    with parameters (&PARAMETERS)
    while performing the following operation:
    &DEBUG_INFO
    ERR REP-1419: 'beforereport': PL/SQL program aborted.
    Program exited with status 3
    Please help to solve the process and let me know what is the AX installation.
    Thanks,
    AKASH

    As you mentioned that you have recently installed Cash Management, it seems the system is unable to derive the accounts related to Cash Clearing. Please verify your setbup for Bank Accounts and Payables Documents. Also log an SR with Oracle Support.
    HTH

Maybe you are looking for