MEMORY_NO_MORE_PAGING problem

Hi,
  I need help with this issue:
  I am facing a MEMORY_NO_MORE_PAGING problem, and I don't know how to solve it. This problem is happening often during the week.
  As an example I pasted on DUMP log. In addition, at the beginning I pasted the screen information of transaction ST02.
  I have already checked the disk space and itu2019s ok, there is plenty of free space.     
Best regards,
Fernando.
ST02 information:
System: SRV-SAPPROD_PRO_00                        Tune summary
Date & time of snapshot: 05.11.2009  11:14:41     Startup: 19.10.2009  08:15:59
       Buffer            Hitratio   Allocated         Free space        Dir. size      Free directory         Swaps       Database
                                                           Entries      Entries                          accesses
Nametab (NTAB)
   Table definition        99,28         6.447            0     0,00        30.000            0     0,00        17.354      106.524
   Field description       99,33        49.289        2.299     4,79        30.000       11.890    39,63        45.037       70.424
   Short NTAB              99,79         3.498        2.755    91,83         7.500        6.303    84,04             0        1.212
   Initial records         99,08         9.998        8.192    86,23         7.500          653     8,71        41.690       48.659
Program                   98,99       400.000        1.102     0,29       100.000       89.560    89,56       159.655      520.665
CUA                       99,89         5.000          208     4,67         2.500        1.464    58,56             0        1.360
Screen                    99,88        19.531        6.272    32,31         2.000        1.298    64,90             0        1.667
Calendar                 100,00           488          369    76,88           200           54    27,00             0          146
OTR                      100,00         4.096        3.657   100,00         2.000        2.000   100,00             0            0
Tables
   Generic key             99,92        48.828       20.810    43,46         5.000          262     5,24           168       97.934
   Single record           92,56        30.000          479     1,60           500          394    78,80            70      439.952
Export/import             87,68         4.096          110     3,01         2.000          187     9,35       245.701            0
Exp./Imp. SHM             95,02         4.096        3.581    97,92         2.000        1.999    99,95             0            0
     SAP memory              Current use      Max. use  In memory   On disk
  Roll area                 2,29      6.009      8.728     65.536    196.608
  Paging area              91,36    239.487    262.136    124.480    137.664
  Extended Memory          64,86  1.325.056  1.728.512  2.042.880
  Heap Memory                             0  1.356.990
DUMP LOG:
Errores tiempo ejec.   MEMORY_NO_MORE_PAGING
Fecha y hora           05.11.2009 10:43:41
Txt.brv.
SAP paging overflow when storing data in the ABAP/4 memory.
¿Qué ha sucedido?
The current program requested storage space from the SAP paging area,
but this request could not be fulfilled.
of this area in the SAP system profile.
Notas para corregir errores
|    The amount of storage space (in bytes) filled at termination time was:                   
Roll area...................... 8112
Extended memory (EM)........... 143208832
Assigned memory (HEAP)......... 0
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... " "
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MEMORY_NO_MORE_PAGING" C
"SAPDBIOC" or "DBIOCF02"
"FILL_MEMORY"
Entorno sistema
SAP Release.............. "640"
Application server....... "SRV-SAPPROD"
Network address.......... "172.16.1.11"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "SRV-SAPPROD"
Database type............ "MSSQL"
Database name............ "PRO"
Database owner........... "pro"
Character set............ "Spanish_Spain.1252"
SAP kernel............... "640"
Created on............... "Aug 7 2009 22:57:17"
Created in............... "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version......... "SQL_Server_9.00 "
Patch level.............. "295"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 8112
EM....................... 143208832
Heap..................... 0
Page..................... 32768
MM Used.................. 121508448
MM Free.................. 9141720
SAP Release.............. "640"
Usuario y transacción
Client.............. 300
User................ "AMATUCHESKI"
Language key........ "S"
Transaction......... "COOISPI "
Program............. "SAPDBIOC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Líneas de pila C en núcleo (estructura diferente según la plataforma)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=5596)
When      : 11/5/2009 10:43:38.343
Threads   : 2
Computer Name       : SRV-SAPPROD
User Name           : SAPServicePRO
Number of Processors: 4
Processor Type: x86 Family 15 Model 4 Stepping 3
Windows Version     : 5.2 Current Build: 3790
Stack Dump for Thread Id 15e0
Edited by: Fernando Zanelli on Nov 5, 2009 1:29 PM

Hi,
           After the first chart that displays the actual system memory status you can find the system parameters.The rdisp/PG_MAXFS as you can see is deactivated and his default value is 32768.
           It should stay deactivated or I need to bring it active?
SAP Memory St02:
SAP memory              Current use      Max. use  In memory   On disk
                                     [%]      [kB]            [kB]          [kB]       [kB]
Roll area                   2,15      5.630      6.888     65.536    196.608
Paging area              91,63    240.203   262.136    124.480    137.664
Extended Memory     60,75  1.241.088  1.514.496  2.042.880
Heap Memory                             0          0
system parameters:
|X|abap/fieldexit                             |yes
|X|login/system_client                        |300
|X|SAPSYSTEMNAME                              |PRO
|X|INSTANCE_NAME                              |DVEBMGS00
|X|SAPSYSTEM                                  |00
|X|rdisp/wp_no_dia                            |8
|X|rdisp/wp_no_btc                            |4
|X|rdisp/wp_no_vb                             |3
|X|rdisp/wp_no_vb2                            |2
|X|rdisp/wp_no_enq                            |1
|X|rdisp/wp_no_spo                            |2
|X|SAPGLOBALHOST                              |srv-sapprod
|X|PHYS_MEMSIZE                               |1996
|X|DIR_TRANS                                  |C:\usr\sap\trans
|X|icm/server_port_0                          |PROT=HTTP,PORT=8000
|X|abap/buffersize                            |400000
|X|zcsa/table_buffer_area                     |50000000
|X|rtbb/buffer_length                         |30000
|X|rsdb/cua/buffersize                        |5000
|X|gw/max_conn                                |2000
|X|gw/max_sys                                 |2000
|X|gw/max_overflow_size                       |25000000
|X|enque/table_size                           |10000
|X|zcsa/presentation_buffer_area              |20000000
|X|rdisp/appc_ca_blk_no                       |100
|X|rdisp/wp_ca_blk_no                         |300
|X|rsdb/ntab/entrycount                       |30000
|X|rsdb/ntab/ftabsize                         |48000
|X|rsdb/ntab/irbdsize                         |9500
|X|rsdb/ntab/sntabsize                        |3000
|X|DIR_ROLL                                   |C:\usr\sap\PRO\DVEBMGS00\data
|X|DIR_PAGING                                 |C:\usr\sap\PRO\DVEBMGS00\data
|X|DIR_DATA                                   |C:\usr\sap\PRO\DVEBMGS00\data
|X|DIR_REORG                                  |C:\usr\sap\PRO\DVEBMGS00\data
|X|DIR_TEMP                                   |.
|X|DIR_SORTTMP                                |C:\usr\sap\PRO\DVEBMGS00\data
|X|zcsa/system_language                       |S
|X|zcsa/installed_languages                   |EDPS
|X|install/codepage/appl_server               |1100
|X|abap/use_paging                            |0
| |ztta/roll_first                            |1024
| |ztta/roll_area                             |2000896
|X|rdisp/ROLL_SHM                             |8192
| |rdisp/ROLL_MAXFS                           |32768
|X|rdisp/PG_SHM                               |15560
| |rdisp/PG_MAXFS                             |32768
| |abap/heap_area_dia                         |2000683008
| |abap/heap_area_nondia                      |2000683008
| |abap/heap_area_total                       |2000683008
| |abap/heaplimit                             |40894464
|X|abap/swap_reserve                          |20971520
| |ztta/roll_extension                        |2000683008
| |em/initial_size_MB                         |1840
|X|em/blocksize_KB                            |1024
|X|em/stat_log_size_MB                        |20
|X|em/stat_log_timeout                        |0
| |em/address_space_MB                        |512

Similar Messages

  • MEMORY_NO_MORE_PAGING " dump

    Hi All,
    We are at SAP ECC 5.0 SAP_BASIS 640.
    Today morning while running mb51 we got " MEMORY_NO_MORE_PAGING " dump.
    Could please help to fix this problem?
    Here is the error info:
    What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "RM07DOCS" had to be terminated because the ABAP
    processor discovered an invalid system state.
    Error analysis
    An internal error occurred when releasing memory in
    SAP Paging. The release ended with the error code
    "-1".
    How to correct the error
    It is probably not possible to eliminate the system error
    with ABAP alone.
    If you have access to SAPnet, you can search for a relevant note
    using the following keywords:
    "MEMORY_PGFREE_FAILED" " "
    "RM07DOCS" bzw. "RM07DOCS_GENERATED"
    "DATA_SELECTION"
    171 endloop.
    172
    173 * process SELECT command depending on the
    174 * required material selection
    175 if l_cnt_matnr_total > 0 and
    176 l_cnt_matnr_total = l_cnt_matnr_i_eq.
    177 * work with .. for all entries ...
    178 select (l_t_fields)
    179 into corresponding fields of table itab
    180 from mkpf inner join mseg
    181 on mkpfmandt = msegmandt
    182 and mkpfmblnr = msegmblnr
    183 and mkpfmjahr = msegmjahr
    184 for all entries in matnr
    185 where matnr = matnr-low
    186 and MKPF~BUDAT in BUDAT
    187 and MSEG~BWART in BWART
    188 and MSEG~CHARG in CHARG
    189 and MSEG~KUNNR in KUNNR
    190 and MSEG~LGORT in LGORT
    191 and MSEG~LIFNR in LIFNR
    192 and MKPF~MJAHR in MJAHR
    193 and MSEG~SOBKZ in SOBKZ
    194 and MKPF~USNAM in USNAM
    195 and MKPF~VGART in VGART
    196 and MSEG~WERKS in WERKS
    197 and MKPF~XBLNR in XBLNR
    198 .
    199 else.
    200 * work with the select command as usual
    >>>>> select (l_t_fields)
    202 into corresponding fields of table itab
    203 from mkpf inner join mseg
    204 on mkpfmandt = msegmandt
    205 and mkpfmblnr = msegmblnr
    206 and mkpfmjahr = msegmjahr
    207 WHERE MKPF~BUDAT in BUDAT
    208 and MSEG~BWART in BWART
    209 and MSEG~CHARG in CHARG
    210 and MSEG~KUNNR in KUNNR
    211 and MSEG~LGORT in LGORT
    212 and MSEG~LIFNR in LIFNR
    213 and MSEG~MATNR in MATNR
    214 and MKPF~MJAHR in MJAHR
    215 and MSEG~SOBKZ in SOBKZ
    216 and MKPF~USNAM in USNAM
    217 and MKPF~VGART in VGART
    218 and MSEG~WERKS in WERKS
    219 and MKPF~XBLNR in XBLNR
    Regards,
    Leo

    Note 1091141 & note 1104914 also are recommending that you upgrade your Basis kernel release to resolve the error.
    4.6D: 2348
    6.40: 204
    7.00: 131
    If your Basis kernel release is not listed but you are receiving the error often, I would still upgrade to the latest kernel release.

  • MEMORY_NO_MORE_PAGING error

    Hi,
    We are using ECC 5.0 here. Our DB is Oracle 9.2.0.6 and OS is AIX.
    We have a problem here.
    Our Finance people run a report "S_ALR_87013542". It was working fine.
    But now it is giving an error with ABAP Dump. The error is MEMORY_NO_MORE_PAGING.
    I have increased the parameter "rdisp/PG_SHM" to the double value. Now the value is 16384. But it is still giving the same error.
    I increased it on a Dialog Instance (application server through which Finance people access SAP)
    I searched the notes, but could not find anything relevant about my error.
    I have tried to run the report in the night when there is no load on the server. But even then it gives the same error.
    My different Memory Paramters for the App server for finance people are listed below:-
    ztta/roll_area                              3000320   
    rdisp/ROLL_SHM                              16384     
    rdisp/ROLL_MAXFS                            32768     
    rdisp/PG_SHM                                16384     
    rdisp/PG_MAXFS                              32768     
    abap/heap_area_dia                          2000683008
    abap/heap_area_nondia                       2000683008
    abap/heap_area_total                        2000683008
    abap/heaplimit                              40894464  
    abap/swap_reserve                           20971520  
    ztta/roll_extension                         2000683008
    My ABAP dump gives this error:-
    Error analysis
        The ABAP/4 runtime system and the ABAP/4 compiler use a common
        interface to store different types of data in different parts of
        the SAP paging area. This data includes the
        ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
        CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
        macros (specified with DEFINE).
                                                                                    To store further data in the SAP paging area, you attempted to
        allocate a new SAP paging block, but no more blocks were
        available.
                                                                                    When the SAP paging overflow occurred, the ABAP/4 memory contained
        entries for 55 of different IDs.
                                                                                    Please note:
        To facilitate error handling, the ABAP/4 memory was
        deleted.
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
                                                                                    Roll area...................... 16128
        Extended memory (EM)........... 418992800
        Assigned memory (HEAP)......... 0
        Short area..................... " "
        Paging area.................... 40960
        Maximum address space.......... 4294967295
                                                                                    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
        you can display an overview of the current roll and paging memory
        levels resulting from active users and their transactions. Try to
        decide from this whether another program requires a lot of memory
        space (perhaps too much).
                                                                                    The system log contains more detailed information about the
        termination. Check for any unwanted recursion.
        Determine whether the error also occurs with small volumes of
        data. Check the profile (parameter "rdisp/PG_MAXFS", see
        Installation Guidelines).
        Is the disk or the file system that contains the paging file
        full to the extent that it cannot be increased, although it has
        not yet reached the size defined in the profile? Is the
        operating system configured to accommodate files of such a
        size?
                                                                                    The ABAP processor stores different types of data in the SAP paging area
        . These include:
                                                                                    (1) Data clusters (EXPORT ... TO MEMORY ...)
           (2) Parameters when calling programs (SUBMIT REPORT ...),
            dialog modues (CALL DIALOG ...) and transactions
            (CALL TRANSACTION USING ...)
        (3) Internally defined macros (DEFINE ...)
                                                                                    Accordingly, you should check the relevant statements in a program
    that results in an overflow of the SAP paging area.
                                                                                    The EXPORT statement is particularly critical - specifically when many
    internal tables, possibly with different IDs, are written to the
    memory.                                                                   
    Kindly help
    Regards,
    Tajinder

    Hello,
    Here the parameters for concern are
    1.rdisp/PG_SHM
    2.rdisp/PG_MAXFS
    1.rdisp/PG_SHM :
    The value specifies the size of the paging buffer in 8KB blocks.
    A paging buffer is no longer required for SAP Memory Managment,
    because internal tables and lists are not stored in SAP paging.
    Default : 0
    2.rdisp/PG_MAXFS :
    This value specifies the size of the SAP paging file in 8KB
    blocks.  The paging file is used to store extracts and for
    Export to Memory.
    Aim:
    The paging file must be sufficiently large. It is not a problem
    if it is set to too large a size.
    Dependencies:
    Sufficient disk space
    You can try
    1.Optimize the code, to use less memory.
    OR
    2.Increasing the parameter rdisp/PG_MAXFS as per the availability of disk space.
    Hope this solves your problem.
    Regards,
    Edited by: Satish P on Oct 21, 2008 2:01 PM

  • MEMORY_NO_MORE_PAGING dump in LCEI0F6O

    Hi Experts,
    When i run a background job for a zprogram automatically another job is getting triggered and it is getting cancelled after some time. When i check the Job log i saw the dump
    MEMORY_NO_MORE_PAGING in the iinclude LCEI0F6O of SAPLCEI0
    Short text says "SAP paging overflow when storing data in the ABAP/4 memory"
    and soucre code extract shows dump at the "Clear Statement"
       49   EXPORT
       50          multi_lingual
       51          mi
       52          wi
       53          anw
       54          gt_ghcl
       55          TO MEMORY ID gs_memory_id.
       56
    >>>>>   CLEAR gs_memory_id-memid.
       58
       59   EXPORT gv_actual_memory_id
       60          gt_memory
       61          TO MEMORY ID gs_memory_id.
    Please suggest me in correcting the above dump
    Thank you,
    Kavya

    Hi,
    It is not problem in standarad program, but it in zprogram problem. When you export data to memory it has some limitation parameter to limit the maximum data to store. when your zprogram run it try to store more data in to application server memory and it not allow to store the maximum due to limit it.
    In your porgram you are reading large amount of data. Don't read all data at all but you do the modification in your program to read data partially and process it. do the same for may time but don't forget to refresh or free the memory of internal table which is store unnecessary data.

  • SAP_COLLECTOR_FOR_PERFMONITOR dumping MEMORY_NO_MORE_PAGING

    Dear friends,
    In one of our BW production system, 2 instance of hourly job SAP_COLLECTOR_FOR_PERFMONITOR is dumping MEMORY_NO_MORE_PAGING.
    I have already checked this thread :
    MEMORY_NO_MORE_PAGING
    But I am unable to find out the reason and also i do not find any Moni Key in abap dump. Please suggest.
    PART OF ABAP DUMP :
       40          SEGMT     = SEGMT.
       41 *     exceptions
       42 *          others       = 1.
       43
       44 EXPORT TS    TO MEMORY ID 'RSORAT2M'.
       45 EXPORT TD110 TO MEMORY ID 'RSORAT4M'.
    >>>>> EXPORT SEGMT TO MEMORY ID 'RSORAT6M'.
       47
       48 * INCLUDE rsorat0b.       T.S. 11/96
       49 * INCLUDE rsorat0m.       T.S. 11/96
       50 * INCLUDE rsorat0f.       T.S. 11/96
       51 *INCLUDE RSORAT2F.
    thanks
    ashish

    Hello friends,
    Of-Course MEMORY_NO_MORE_PAGING is a memory dump and it can be avoided if i increage paging sizes. We have smaller value for this parameter and I am not convinced if it is required now to increase it. This was working nicely sometime back.
    So, When we say we have abap statement EXPORT which is causing MEMORY_NO_MORE_PAGING. But the same abap statement was working fine sometime back and we did not had this problem. So i assume if there is something like large number of history records as per SAP Note 713211 is troubling us.
    Now, i want to findout what is causing so much of memory requirement & page files.
    We also get similar dumo when we manually try to perform DB Checks & update histories with transaction DB02OLD. This is the same this what Collector Job also doing and dumping.
    Any new suggestion please..
    thanks
    ashish

  • Dump While Extracting with MEMORY_NO_MORE_PAGING.

    Hello Experts,
    I have enhanced a Standard Datasoure with 3 fields in which for 2 of the fields  I have used a standard function module to populate the data.It was working fine.
    Now I have a situation when I am extracting data from BI my load is going fine at one point if time and same one fails at another point of time.giving a Error mesage in the joblog that MEMORY_NO_MORE_PAGING.
    I am calling my FM in the Exit some 80000 times as the dataloaded to BI are 80000 records when I have a case of sucessful load when Extracted to BI from ECC. I have checked Commenting my FM called in EXIT and checked RSA3 the results are 80000 records working fine.
    Please advise if this could be a Page memory Problem or if I am calling my FM 80000 times in the Exit it needs a sufficient memory to retrieve the data.
    Please advise if we have any SAP notes related to the BAPI that corresponds to memory issue.
    STD FM-BAPI_TRIP_GET_DETAILS.
    Regards,
    KOKA.

    Answered

  • A problem with threads

    I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
    Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
    My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
    Thank you in advance,
    Lefty

    This was one solution from the socket programming forum, have you tried this??
    public Thread MyThread extends Thread{
         boolean active = true;          
         public void run(){
              ss.setSoTimeout(90);               
              while (active){                   
                   try{                       
                        serverSocket = ss.accept();
                   catch (SocketTimeoutException ste){
                   // do nothing                   
         // interrupt thread           
         public void deactivate(){               
              active = false;
              // you gotta sleep for a time longer than the               
              // accept() timeout to make sure that timeout is finished.               
              try{
                   sleep(91);               
              }catch (InterruptedException ie){            
              interrupt();
    }

  • A problem with Threads and MMapi

    I am tring to execute a class based on Game canvas.
    The problem begin when I try to Play both a MIDI tone and to run an infinit Thread loop.
    The MIDI tone "Stammers".
    How to over come the problem?
    Thanks in advance
    Kobi
    See Code example below:
    import java.io.IOException;
    import java.io.InputStream;
    import javax.microedition.lcdui.Graphics;
    import javax.microedition.lcdui.Image;
    import javax.microedition.lcdui.game.GameCanvas;
    import javax.microedition.media.Manager;
    import javax.microedition.media.MediaException;
    import javax.microedition.media.Player;
    public class MainScreenCanvas extends GameCanvas implements Runnable {
         private MainMIDlet parent;
         private boolean mTrucking = false;
         Image imgBackgound = null;
         int imgBackgoundX = 0, imgBackgoundY = 0;
         Player player;
         public MainScreenCanvas(MainMIDlet parent)
              super(true);
              this.parent = parent;
              try
                   imgBackgound = Image.createImage("/images/area03_bkg0.png");
                   imgBackgoundX = this.getWidth() - imgBackgound.getWidth();
                   imgBackgoundY = this.getHeight() - imgBackgound.getHeight();
              catch(Exception e)
                   System.out.println(e.getMessage());
          * starts thread
         public void start()
              mTrucking = true;
              Thread t = new Thread(this);
              t.start();
          * stops thread
         public void stop()
              mTrucking = false;
         public void play()
              try
                   InputStream is = getClass().getResourceAsStream("/sounds/scale.mid");
                   player = Manager.createPlayer(is, "audio/midi");
                   player.setLoopCount(-1);
                   player.prefetch();
                   player.start();
              catch(Exception e)
                   System.out.println(e.getMessage());
         public void run()
              Graphics g = getGraphics();
              play();
              while (true)
                   tick();
                   input();
                   render(g);
          * responsible for object movements
         private void tick()
          * response to key input
         private void input()
              int keyStates = getKeyStates();
              if ((keyStates & LEFT_PRESSED) != 0)
                   imgBackgoundX++;
                   if (imgBackgoundX > 0)
                        imgBackgoundX = 0;
              if ((keyStates & RIGHT_PRESSED) != 0)
                   imgBackgoundX--;
                   if (imgBackgoundX < this.getWidth() - imgBackgound.getWidth())
                        imgBackgoundX = this.getWidth() - imgBackgound.getWidth();
          * Responsible for the drawing
          * @param g
         private void render(Graphics g)
              g.drawImage(imgBackgound, imgBackgoundX, imgBackgoundY, Graphics.TOP | Graphics.LEFT);
              this.flushGraphics();
    }

    You can also try to provide a greater Priority to your player thread so that it gains the CPU time when ever it needs it and don't harm the playback.
    However a loop in a Thread and that to an infinite loop is one kind of very bad programming, 'cuz the loop eats up most of your CPU time which in turn adds up more delays of the execution of other tasks (just as in your case it is the playback). By witting codes bit efficiently and planning out the architectural execution flow of the app before start writing the code helps solve these kind of issues.
    You can go through [this simple tutorial|http://oreilly.com/catalog/expjava/excerpt/index.html] about Basics of Java and Threads to know more about threads.
    Regds,
    SD
    N.B. And yes there are more articles and tutorials available but much of them targets the Java SE / EE, but if you want to read them here is [another great one straight from SUN|http://java.sun.com/docs/books/tutorial/essential/concurrency/index.html] .
    Edited by: find_suvro@SDN on 7 Nov, 2008 12:00 PM

  • J2ME problem with threads

    Hi all,
    I would like to ask you for a help. I need to write a small program at my university. I started to write a midlet which function would be to countdown time for sports activities. I woul like to start a new thread - the one that counts down - and at the same time make the main thread sleep. After the "countdown" thread finishes, the main thread wakes up and waits for user input. The problem is that when the "countdown" thread finishes his work, I've got Uncaught exception java/lang/NullPointerException. error and the midlet halts.
    Below you can find the code
    import java.lang.*;
    import java.util.*;
    import javax.microedition.lcdui.*;
    import javax.microedition.midlet.*;
    public class intervals extends MIDlet implements CommandListener
    public Display ekran;
    private SweepCanvas sweeper;
    private Form rundy;
    private TextField round0, round1, round2, round3, round4, round5, round6, round7, round8;
    private long czas,x;
    private Command exitCommand;
    private Command addRound;
    private Command delRound;
    private Command start;
    private TextField repeat;
    private Form odliczanie;
    private Alert ostrz;
    Licznik thread;
    String test;
    StringItem test1;
    int parz,i,j,k;
    static int l;
    int ilrund;
    int ilpowt;
    Item sec;
    long sec1;
    public intervals()
        rundy = new Form("Interwa&#322;y sportowe");
        exitCommand = new Command("Wyj&#347;cie", Command.EXIT, 2);
        addRound = new Command("Dodaj","Dodaj rund&#281;", Command.ITEM,1);
        delRound = new Command("Usu&#324;","Usu&#324; ostatni&#261; rund&#281;", Command.ITEM,1);
        start = new Command("Start", Command.ITEM,1);
        odliczanie = new Form("Odliczanie");
        TextField dodaj(TextField kolej)
            kolej=new TextField("Podaj czas (s) rundy "+parz,null, 4, TextField.NUMERIC);//stworzenie nowej instancji do wybierania czasu trwania rundy
            if(rundy.size()==0)
                rundy.insert(rundy.size(),kolej);
                else
                    rundy.insert(rundy.size()-1, kolej);
            return kolej;
        void odliczanie(TextField round)
            monitor m=new monitor();
            k=Integer.parseInt(round.getString());
            ekran.setCurrent(odliczanie);
            thread=new Licznik(k,odliczanie);
            thread.start();
            ekran.setCurrent(rundy);
    public void startApp()// throws MIDletStateChangeException
        rundy.deleteAll();
        repeat = new TextField("Podaj ilo&#347;&#263; powtórze&#324;",null,1,TextField.NUMERIC);
        rundy.addCommand(addRound);
        rundy.addCommand(exitCommand);
        rundy.setCommandListener(this);
        Canvas obrazek = new MyCanvas();
        ekran = Display.getDisplay(this);
        ekran.setCurrent(obrazek);
        czas=System.currentTimeMillis();
        while (System.currentTimeMillis()<czas+1000)
            continue;
        ekran.setCurrent(rundy);
    public void pauseApp()
    public void destroyApp(boolean unconditional)
        notifyDestroyed();
    public void commandAction(Command c, Displayable s)
        if (c == exitCommand)
            destroyApp(false);
            notifyDestroyed();
        else if(c==addRound)
            if(rundy.size()==0)//Sprawdzenie ilo&#347;ci elementów w celu poprawnego wy&#347;wietlania liczby rund w formie
                parz=1;
                else
                parz=rundy.size();
            switch(parz)
                case 1:
                    round0=dodaj(round0);break;
                case 2:
                    round1=dodaj(round1);break;
                case 3:
                   round2= dodaj(round2);break;
                case 4:
                    round3=dodaj(round3);break;
                case 5:
                    round4=dodaj(round4);break;
                default:
                    ostrz=new Alert("Uwaga","Maksymalna liczba rund wynosi 9", null, AlertType.INFO);
                    ostrz.setTimeout(3000);
                    ekran.setCurrent(ostrz);
            if(rundy.size()==1)
                rundy.append(repeat);
                rundy.addCommand(start);
            rundy.addCommand(delRound);
        else if(c==delRound)
            if(rundy.size()!=0)
                rundy.delete(rundy.size()-2);
                if (rundy.size()==1)
                    rundy.deleteAll();
                if(rundy.size()==0)
                    rundy.removeCommand(delRound);
                    rundy.removeCommand(start);
        else if(c==start)
            ilrund=rundy.size()-1;
            if(this.repeat.size()>0)
                ilpowt=Integer.parseInt(this.repeat.getString());
            ekran = Display.getDisplay(this);
            for (i=1; i<=ilpowt;i++)
                odliczanie= new Form("Odliczanie");
                 for (j=0;j<ilrund;j++)
                    switch(j)
                         case 0:
                             odliczanie(round0);
                             break;
                         case 1:
                             odliczanie(round1);
                             break;
                         case 2:
                             odliczanie(round2);
                             break;
                         case 3:
                             odliczanie(round3);
                             break;
                         case 4:
                             odliczanie(round4);
                             break;
                         case 5:
                             odliczanie(round5);
                             break;
                         case 6:
                             odliczanie(round6);
                             break;
                         case 7:
                             odliczanie(round7);
                             break;
                         case 8:
                             odliczanie(round8);
                             break;
    class Licznik extends Thread
        int czas1,k;
        Form forma;
        monitor m;
        public Licznik(int k,Form formap)
            czas1=k;
            forma=formap;
        public synchronized void run()
            while(czas1>0)
                forma.deleteAll();
                forma.append("Czas pozosta&#322;y (s): "+czas1);
                try{Thread.sleep(1000);} catch(InterruptedException e){e.printStackTrace();}
                czas1--;
            if(czas1<=0)
                m.put();
        }and monitor class
    public class monitor
    boolean busy=false;
    synchronized void get()
        if(!busy)
            try
                wait();
            }catch(InterruptedException e){e.printStackTrace();}
        notify();
    synchronized void put()
        if(busy)
            try
            wait();
            }catch(InterruptedException e){e.printStackTrace();}
        busy=true;
        notify();
    }Can anybody help me with this?

    Groovemaker,
    Your Licznik class has a member m of type monitor, which has not been instantiated (in other words is null) hence, when calling m.put() you get NullPointerException. Please also mind, that using Thread.sleep(1000) is not an accurate way of measuring time.
    If I may, please use recommended for Java class naming conventions - some of your names use lower case, while other don't which is confusing to the reader.
    Daniel

  • Problem with threads within applet

    Hello,
    I got an applet, inside this applet I have a singleton, inside this singleton I have a thread.
    this thread is running in endless loop.
    he is doing something and go to sleep on and on.
    the problem is,
    when I refresh my IE6 browser I see more than 1 thread.
    for debug matter, I did the following things:
    inside the thread, sysout every time he goes to sleep.
    sysout in the singleton constructor.
    sysout in the singleton destructor.
    the output goes like this:
    when refresh the page, the singleton constructor loading but not every refresh, sometimes I see the constructor output and sometimes I dont.
    The thread inside the singleton is giving me the same output, sometime I see more than one thread at a time and sometimes I dont.
    The destructor never works (no output there).
    I don't understand what is going on.
    someone can please shed some light?
    thanks.
    btw. I am working with JRE 1.1
    this is very old and big applet and I can't convert it to something new.

    Ooops. sorry!
    I did.
         public void start() {
         public void stop() {
         public void destroy() {
              try {
                   resetAll();
                   Configuration.closeConnection();
                   QuoteItem.closeConnection();
              } finally {
                   try {
                        super.finalize();
                   } catch (Throwable e) {
                        e.printStackTrace();
         }

  • Problem with Threads and a static variable

    I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
    Code functionality:
    A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
    The problem as far I understand is:
    Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
    Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
    Thanks,
    B.D.
    Code:
    private static volatile boolean bChanged = false;
    private static Thread objMainProcess;
       protected static void Init(){
            objMainProcess = new Thread() {
                public void run() {
                    while( objMainProcess == Thread.currentThread() ) {
                       GetState();
            objMainProcess.setDaemon( true );
            objMainProcess.start();
        public static void initStatusTimer(){
            if(objTimer == null)
                 objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                    public void actionPerformed( java.awt.event.ActionEvent evt){
                              SetState();
        private static void SetState(){
            if( objMainProcess == null ) return;
            synchronized( objMainProcess ) {
                bChanged = true;
                try{
                    objMainProcess.notify();
                }catch( IllegalMonitorStateException e ) {}
        private static boolean GetState() {
            if( objMainProcess == null ) return false;
            synchronized( objMainProcess ) {
                if( bChanged) {
                    SendMessage();
                    bChanged = false;
                    return true;
                try {
                    objMainProcess.wait();
                }catch( InterruptedException e ) {}
                return false;
        }

    Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
    Again as you said, There is a reason I can't call sendMessage() inside setState().
    The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
    Thanks,
    B.D.

  • Problem with threads running javaw

    Hi,
    Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
    troy.

    troy,
    Try and post a minimum code sample of your app which
    does not work.
    When using javaw, make sure you redirect the standard
    error and standard output streams to file.
    Graeme.Hi Graeme,
    I dont understand what you mean by redirection to file? some of my code below.
    The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
    public class Server{
    ServerSocket aServerSocket;
    Socket dianosticsSocket;
    Socket nPortExpress;
    ClientListener aClientListener;
    LinkedList queue = new LinkedList();
    int port = 0;
    int clientPort = 0;
    String clientName = null;
    boolean serverAlive = true;
    * Server constructor generates a server
    * Socket and then starts a client threads.
    * @param aPort      socket port of local machine.
    public Server(int aPort, String aClientName, int aClientPort){
    port = aPort;
    clientName = aClientName;
    clientPort = aClientPort;
    try{
    // create a new thread
    aServerSocket = new ServerSocket(port) ;
    // connect to the nPortExpress
    aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
    // aClientListener.setDaemon(true);
    aClientListener.start();
    // start a dianostic port
    DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
    // System.out.println("Server is running on port " + port + "...");
    // System.out.println("Connect to nPort");
    catch(Exception e)
    // System.out.println("ERROR: Server port " + port + " not available");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
    serverAlive = false;
    System.exit(1);
    while(serverAlive&&aClientListener.hostSocket.isConnected()){
    try{
    // connect the client
    Socket aClient = aServerSocket.accept();
    //System.out.println("open client connection");
    //System.out.println("client local: "+ aClient.getLocalAddress().toString());
    // System.out.println("client localport: "+ aClient.getLocalPort());
    // System.out.println("client : "+ aClient.getInetAddress().toString());
    // System.out.println("client port: "+ aClient.getLocalPort());
    // make a new client thread
    ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
    // start thread
    clientThread.start();
    catch(Exception e)
    //System.out.println("ERROR: Client connection failure");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
    }// end while
    } // end constructor Server
    void serverExit(){
         JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
         System.exit(1);
    }// end class Server
    *** connect to another server
    public class ClientListener extends Thread{
    InetAddress hostName;
    int hostPort;
    Socket hostSocket;
    BufferedReader in;
    PrintWriter out;
    boolean loggedIn;
    LinkedList queue;      // reference to Server queue
    Server serverRef; // reference to main server
    * ClientListener connects to the host server.
    * @param aHostName is the name of the host eg server name or IP address.
    * @param aHostPort is a port number of the host.
    * @param aLoginName is the users login name.
    public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
    hostName = aHostName;
    hostPort = aHostPort;
    queue = aQueue;
    serverRef = aServer;      
    // connect to the server
    try{
    hostSocket = new Socket(hostName, hostPort);
    catch(IOException e){
    //System.out.println("ERROR: Connection Host Failed");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);     
    System.exit(0);
    } // end constructor ClientListener
    ** multi client connection server
    ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
    queue = aQueue;
    addToQueue(this);
    client = aSocket;
    clientRef = aClientListener;
    aDiagnostic = diagnostics;
    } // end constructor ClientWorker
    * run method is the main loop of the server program
    * in change of handle new client connection as well
    * as handle all messages and errors.
    public void run(){
    boolean alive = true;
    String aSubString = "";
    in = null;
    out = null;
    loginName = "";
    loggedIn = false;
    while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
    try{
    in = new BufferedReader(new InputStreamReader(client.getInputStream()));
    out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
    if(aDiagnostic){
    out.println("WELCOME to diagnostics");
    broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
    out.flush();
    else {       
    out.println("WELCOME to Troy's Server");
    broadCastDia("Connect : client "+client.getInetAddress().toString());
         out.flush();
    String line;
    while(((line = in.readLine())!= null)){
    StringTokenizer aStringToken = new StringTokenizer(line, " ");
    if(!aDiagnostic){
    broadCastDia(line);
    clientRef.sendMessage(line); // send mesage out to netExpress
    out.println(line);
    out.flush();
    else{
    if(line.equals("GETIPS"))
    getIPs();
    else{
    clientRef.sendMessage(line); // send mesage out to netExpress
    out.println(line);
    out.flush();
    } // end while
    catch(Exception e){
    // System.out.println("ERROR:Client Connection reset");
                             JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);     
    try{
    if(aDiagnostic){
    broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
    out.flush();
    else {       
    broadCastDia("Disconnect : client "+client.getInetAddress().toString());
         out.flush();
    // close the buffers and connection;
    in.close();
    out.close();
    client.close();
    // System.out.println("out");
    // remove from list
    removeThreadQueue(this);
    alive = false;
    catch(Exception e){
    // System.out.println("ERROR: Client Connection reset failure");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);     
    }// end while
    } // end method run
    * method run - Generates io stream for communicating with the server and
    * starts the client gui. Run also parses the input commands from the server.
    public void run(){
    boolean alive = true;
    try{
    // begin to life the gui
    // aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
    // aGuiClient.show();
    in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
    out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
    while (alive && hostSocket.isConnected()){
    String line;
    while(((line = in.readLine())!= null)){
    System.out.println(line);
    broadCast(line);
    } // end while
    } // end while
    catch(Exception e){
    //     System.out.println("ERRORa Connection to host reset");
    JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
    try{
    hostSocket.close();
         }catch(Exception a){
         JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
    alive = false;
    System.exit(1);
    } // end method run

  • Problem with Threads and "plase wait..."-Window

    Hi everyone,
    I have a problem that I'm not able to solve in any way... I have a time-consuming task (a file decryption) which I execute in a separate thread; I've used the SwingWorker class, like suggested by sun-tutorial, and it works right. The problem is that I have to wait that the decryption have finished before continuing with program-execution. Therefore I would like to display a "please wait"-window while the task runs. I've tryed all the possible ways I know but the problem is always the same: the waitWindow is displayed empty, the bounds are painted but the contents no; it's only painted when the decrypt-task has finished. Please help me, I have no more resources....
    decrypt-file code:
    public class DecryptFile {
      private String cryptedFileNameAndPath;
      private ByteArrayInputStream resultStream = null;
      // need for progress
      private int lengthOfTask;
      private int current = -1;
      private String statMessage;
      public DecryptFile(String encZipFileNameAndPath) {
        cryptedFileNameAndPath = encZipFileNameAndPath;
        //Compute length of task...
        // 0 for indeterminate
        lengthOfTask = 0;
      public ByteArrayInputStream getDecryptedInputStream() {
        return this.resultStream;
       * Called from ProgressBarDemo to start the task.
      public void go() {
        current = -1;
        final SwingWorker worker = new SwingWorker() {
          public Object construct() {
            return new ActualTask();
        worker.start();
       * Called from ProgressBarDemo to find out how much work needs
       * to be done.
      public int getLengthOfTask() {
        return lengthOfTask;
       * Called from ProgressBarDemo to find out how much has been done.
      public int getCurrent() {
        return current;
      public void stop() {
        current = lengthOfTask;
       * Called from ProgressBarDemo to find out if the task has completed.
      public boolean done() {
        if (current >= lengthOfTask)
          return true;
        else
          return false;
      public String getMessage() {
        return statMessage;
       * The actual long running task.  This runs in a SwingWorker thread.
      class ActualTask {
        ActualTask () {
          current = -1;
          statMessage = "";
          resultStream = AIUtil.getInputStreamFromEncZip(cryptedFileNameAndPath); //here the decryption happens
          current = 0;
          statMessage = "";
      }The code that calls decryption and displays waitWindow
          final WaitSplash wS = new WaitSplash("Please wait...");
          final DecryptFile cryptedTemplate = new DecryptFile (this.templateFile);
          cryptedTemplate.go();
          while (! cryptedTemplate.done()) {
            try {
              wait();
            } catch (Exception e) { }
          this.templateInputStream = cryptedTemplate.getDecryptedInputStream();
          wS.close();Thanks, thanks, thanks in advance!
    Edoardo

    Maybe you can try setting the priority of the long-running thread to be lower? so that the UI will be more responsive...

  • Problem with threads in j2me

    im using jdk 1.6 with java wtk 2.1
    ya i know..
    2.1 is a jdk1.4 source
    but im using souce as 1.4 during compiliation so thats not the prob
    this is my code
    package org.learn;
    import javax.microedition.midlet.MIDlet;
    import javax.microedition.lcdui.Alert;
    import javax.microedition.lcdui.Display;
    public class thtest extends MIDlet
    Thread t;
    public void startApp()
    Alert a=new Alert("hello");
    a.setString("hello");
    Alert b=new Alert("world");
    b.setString("world");
    Display d = Display.getDisplay(this );
    d.setCurrent(a);
    t=Thread.currentThread();
    try{
    t.sleep(10000);
    catch (Exception e){}
    d.setCurrent(b);
    public void pauseApp()
    public void destroyApp(boolean unconditional)
    its just supposed to pause between the alerts using threads
    however when i run it using the wtk, the emulator run properly but when i launch the app, it stops executing giving me this:
    "Error verifying method org/learn/thtest startApp()V
    Approximate bytecode offset 49: Inconsistent or missing stackmap at target
    %the stack info%
    Execution completed.
    437782 bytecodes executed
    9 thread switches
    486 classes in the system (including system classes)
    2506 dynamic objects allocated (73832 bytes)
    2 garbage collections (60652 bytes collected)
    Execution completed.
    437782 bytecodes executed
    9 thread switches
    486 classes in the system (including system classes)
    ALERT: java/lang/VerifyError: org/learn/thtest.
    2506 dynamic objects allocated (73832 bytes)
    2 garbage collections (60652 bytes collected)
    please can someone help me out with this, is it an error on my part or do i have to set some option.

    Hi gandalf123,
    First, Thread.sleep is a static method, so you don't need to create a Thread object to use it.
    I think the problem is due to the fact you don't preverify your midlet.
    More over, you don't need to double post your question.

  • Problem with threads and camera.

    Hi everybody!
    I've a problem with taking snapshot.
    I would like to display a loading screen after it take snapshot ( sometimes i
    have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
    I was trying to use threads but i didn't succeed.
    I made this code:
    display.setCurrent(perform);               
            new Thread(new Runnable(){
                public void run() {               
                    while((!performing.isShown()) && (backgroundCamera.isShown())){
                        Thread.yield();
                    notifyAll();
            }).start();
            new Thread(new Runnable(){
                public void run() {
                    try {
                        this.wait();                   
                    } catch(Exception e) {
                        exceptionHandler(e);
                    photo = camera.snapshot();                               
                    display.setCurrent(displayPhoto);
            }).start();This code is sometimes showing performing screen but sometimes no.
    I don't know why. In my opinion performing.isShown() method isn't working correctly.
    Does anyone have some idea how to use threads here?

    Hi,
    I've finally managed to work this fine.
    The code:
           Object o = new Object();
           display.setCurrent(perform);               
            new Thread(new Runnable(){
                public void run() {               
                    while(!performing.isShown()){
                        Thread.yield();
                   synchronized(o) {
                      o.notify();
            }).start();
            new Thread(new Runnable(){
                public void run() {
                    try {
                        synchronized(o) {
                           o.wait(1);
                    } catch(Exception e) {
                        exceptionHandler(e);
                    photo = camera.snapshot();                               
                    display.setCurrent(displayPhoto);
            }).start();

Maybe you are looking for

  • Fatal error when updating Payload with Java hw Worklist API

    Hi all, I am receiving an error when I want to update some non-String-type fields of a task payload. I access the fields in the payload with facade-classes, generated by Schemac. The fact is that I can read all the payload fields, but when I try to s

  • Need material document number

    Dear all,     I have an issue.  Inorder resolve it i need run a run aset up in OL1BW using the material document number. I have the process order, period, plant and material, but i need to find the corresponding material document number. Can anyone h

  • Proactive caching Error while installing BPC 7.0 SP6

    All, We are installing BPC 7.0 sp 6 on Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)   Jul  9 2008 14:43:34   Copyright (c) 1988-2008 Microsoft Corporation  Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) In short S

  • UMELoginException: PASSWORD_EXPIRED

    Dear experts, I am facing problem while log-in to the Visual admin using the user "administrator" in our protal inastalled system. Following is the error: #1.5^H#00151778AF8C005B0000011000003CD20004730A14D9C060#1252387043523#com.sap.engine.services.s

  • In what server a class is running

    Hello, I have a web application in JSP. In a class, i need a environment varible that I'm recovering it with System.getProperty(). This variable can to exist or not, it depending in this web application Server I use. Could know I in the class what is