Problem with Infopackage

I am having a Infopackage(delta)  in Dev. When every I am trying to open that Infopackage I am getting short dump . even I am unable run ,open or change that Infopackage.  But I am able to do these things in quality …..
I am facing the same problem with all infopackages under that Infosource. Even I am unable to create a new Infopackage under (only) that infosource .
   In the dump I got the following messages
"MESSAGE_TYPE_X" C        
"SAPLRSS1 " or "LRSS1F11 "
"RSM1_CHECK_FOR_DELTAUPD" 
pls let me know what to do. Its urgent.

Hi Kris,
You may want to look at notes :424848 and 834229
Hope this helps...

Similar Messages

  • Problem with loading in process chain

    Hello all,
    I've a problem with my process chain. There are few loading packages that are suppose to start together. Problem is, I guess, not enough processes to start them all together. What happens is that some start loading where others "wait". In SM50 I can see all processes are taken. When the loading of the first pacakages is finished (and I can see processes available in  SM50)
    I'm expecting the load of the waiting packages would start, but nothing happens and the process chains stucks!
    The infopackage load gets a yellow color, and stays that way, no cahnges , and no start of process, can someone help? anyone encountered that before?
    Thank you,
    Yoav Ophek.

    Hi,
    Monitor the InfoPack Loads through the T-Code RSMO.
    When u select a Job, go to EnvironMent ->tRFC -> In Source System / DataWarehouse, and check if there are any Stuck tRFC's due to which the loads are stuck.
    I do not see any other reasons why the Loads would be stuck.
    Also check ST22 for any Short Dumps occurred for that time.
    SM21 for Job Overview.
    And check what else could have been the problem for not loading the InfoPackages.
    Hope it helps,
    Pradip Parmar

  • Load Masterdata with Infopackage and DTP..Is there any other way simplier ?

    Dear all:
    We are currently working under BI 2004s SP09. And we are trying to loading Masterdata from R3. For Attributes and text, we have to create Infopackage for DS, load data from R3 into PSA(Not able to into Char directly), then create transformation and DTP to upload data into characteristics.
    If we work with transformation and DTP directly, we got nothing!!?? But if that is the only way we can upload InfoObject, the whole process seems more complexe then what happened in BW 3.X.
    Or there is way to allow us upload data into Infoobject directly with DTP?
    Thank you all very much
    BR
    SF

    Hi Kenneth,
    Am wondering whether the DTP was created at the wrong level, the top level as you have suggested, i.e the Infocube (or Infoprovider) level is the correct place to place the DTP.
    As for a simpler method, I'd stay clear of the do not access PSA.  We found numerous problems with moving to PRD and daily deltas not working correctly.
    Hence as such changed loads to OLTP > Infopackage > DTP > Data Target(be it master data).
    Hope it helps.
    Pom

  • Problem with delta load urgent!!

    Hi,
    I have a problem with delta load
    We have an IP, which loads data from R/3 system daily, its a delta load to the ODS and it updates to the cube with the selection on Company Codes and 0FISCPER
    we are in 3.5 system
    For a couple of company codes A & B, the init was done for the period 07.2010 to 12.2099 and after tht the deltas are loaded from 07.2010 till 12.2099 and there's no pblm with tht
    Now, there was some updation in R/3 system and the data was maintained for the company codes in A& B for the FISCPER 001.2010 to 006.2010, for which init wasnt maintained...
    now how shall we need to load the init in this case? dnt ask me how the postings was done in R/3, but my pblm is purely related to the loading data in BW from R/3, as its very imp for the customer to see the data from 01.2010 to 12.2010 in reports, but the data was only available in reports from 07.2010 onwards
    do i need to create another IP and maintain the init for 01.2010 to 06.2010? so tht this selection will automatically appear in the ODS delta loading infopackage
    pls throw ur inputs ASAP
    thank you

    Hi Prince,
    No need to maintain any Init for this data, It will be enough if you can load the data from jan 2010 to jun 2010 into your Info Cube.
    Follow the below steps:
    1)create full load IP for this data source.
    2) give the selection as A and B company codes and 0FISCPER as 001.2010 to 006.2010
    3) in menu bar, click on scheduler --> select full repair request
    4) In the next screen check the check box and save
    5) Now execute the IP, it will the data with out disturbing your daily delta.
    follow the same procedure to load data till to your Info Cube.
    Please revert if you have any questions
    Regards,
    Venkatesh

  • Problem with triggering process chain

    Hi
    We have a remote process chain that calls a process chain in another system.The process chain in the other system is not getting triggered with the remote chain.
    We have 3 such remote chains and we are facing such a problem with only one of them.
    The process chain in the other system has a start variant which gets triggered( i suppose) and gives an instance id...the next step in the process chain is to load data into a ODS.Now this step remains yellow forever.When i manually try to schedule this step it gives me records and the request in the monitor screen turns green.But the process chain step continues to remain yellow.
    What can be a way out for triggering the process chain or where could the problem be?
    Please help
    Thanks,
    Suchi

    Hi Suchitra,
    Even though ur process seems to be in yellow your data loading may be completed and the  reason for it may be the delay in activation of ODs by ur PC.
    For your information please go through the below infm provided in SAp Library
    Note when loading into an ODS object and for the subsequent, event-controlled update:
    If you switched on the automatic activation in the ODS maintenance or administration, the monitor status for the request remains yellow after the load was successfully completed. Nevertheless, the subsequent processing for the InfoPackage is started, because the loading process is successfully completed.
    [http://help.sap.com/saphelp_nw04/helpdata/en/65/163d3873130057e10000009b38f842/content.htm]
    I hope ur doubt is clear.
    Regards,
    Rajkandula

  • Problem with Real Time Data Acquisition

    Hello,
    I tried to built a RDA data flow according to the SAP-Help and this blog (/people/kamaljeet.kharbanda/blog/2006/11/13/real-time-data-acquisition-bi2004s), but I ran into a problem. Everything seems to be fine, but even though the daemon is running no new data is added to the DSO. I'll explain in detail what steps I took and hope someone can pinpoint my error(s).
    System is BW4 on SPS 17. My datasource as well as my DSObject are in the same system
    1.) Created a transparent table with a timestamp-field for generic delta as a local object.
    2.) Created a generic datasource from view/table (used the above table), marked it as realtime-enabled and used timestamp as delta-specific field.
    3.) Replicated the metadata for my datasource and activated it.
    4.) Created a Data Storage Object with infoobjects corresponding to the table fields
    5.) Created a transformation between DataSource and DSO
    6.) Created a DTP from Data Source to DSO. The type is realtime-DTP.
    7.) Created an InfoPackage for Delta-Initial Load. Update mode: Initialize Delta Process -> Initialization with Data Transfer.
    8.) Then I changed my DTP (step 6) to "normal DTP" and executed it. Then activated the data in the DSO. The datasets from the table (which i filled with an ABAP-program) were successfully loaded and activated. So now my DSO contains 5 datasets.
    9.) Changed the DTP back to "realtime DTP"
    10.) Created an InfoPackage for RDA. Adapter is set to "Realtime extraction from SAP System"
    11.) Created a daemon, assigned the IP for RDA and the DTP to the daemon and started it up.
    12.) Executed my ABAP program to added 3 datasets to the table which is used as a datasource.
    So now in my source table there are 8 datasets, but the daemon won't load them. In my RDA-Monitor (trx rsrda) it shows my daemon, the assigned IP and the assigned DTP (status green). Under the IP there's one yellow request (that should be right according to the help), but unlike the picture in the blog (link see above) there's no request under the DTP.
    Job overview (sm37) shows an active batch job and some jobs that are ready (every 10minutes a new batch starts and the old one is closed). the job log shows, that the daemon runs, but loads no data...
    i think it might be a problem with the delta extraction somewhere, because the intial load works fine and there are no errors anywhere.
    Edit: perhaps my settings in the data source unter tab: extraction are wrong?
    Delta process: AIE After Images By Extractor (can't change that)
    Direct Access: Allowd
    real Time: Real-Time DA Supported
    Adapter: realtime data extraction (also tried Access to SAP Data through Service API which seems senseless)
    Data Format: Fixed Lenght
    Anyone can explain what those fileds mean and which one i should use?
    Edited by: Christoph Jender on Apr 10, 2008 2:48 PM
    Edited by: Christoph Jender on Apr 10, 2008 3:33 PM

    Hi again, another thing i'd like to try is to just active a business content datasource which is realtime-enabled and has the ability to dynamically add some values so that i can test if it works. but i have no idea what business content would be applicable here, any ideas on that perhaps?

  • Problem with Adftreetable when disclosured and re-open it

    I have problem with using adftreetable. Normally adftreetable do not expand all nodes even though there is an attribute for that (it expands only the first node strangely). So we have to use this tip (http://thepeninsulasedge.com/frank_nimphius/2007/12/19/adf-faces-rc-initially-expanding-all-nodes-in-a-tree-or-tree-table/) to expand nodes when first running web page. It works but when click to close (-) to close and open the node again with (+) the animation seems to loop forever and the clicked node doesn't open. Could anyone know this problem? Please help me.
    Thanks.

    As you are loading in development
    try to create new Infopackage and try loading with the datatarget for whcih you want to load alone
    Also try to activate all the related objects.
    Regards
    Edited by: 200816 on Oct 7, 2009 11:58 AM

  • Delta problem with datasource 2LIS_08TRTLP

    Hello everybody,
    I'm having a problem with the delta to datasource 2LIS_08TRTLP.
    I follow this tasks:
    1 - I did a deletion of setup table data in transaction LBWG for application 08 and checked Shipment document and Shipment Costs.
    2 - Transaction VTBW -> Execute this transaction with the fields "Shipment Number" and "Created on" empty.
    3 - Execute a infopackage with update - "Initialize Delta process - Initialization with Data Transfer".
    I don't have problem with this 03 tasks, the data come from ECC without problem.
    But when I execute a infopackage with "Delta Update"  the Monitor - Administrator Workbench show me 0 from 0 records "No data available, data selection ended ".
    What is wrong in my tasks? Why the delta don't work?
    Thanks.
    Paulo Sampaio

    Hi,
    Your Process is correct for initialization load. But when you are running the delta there should be a V3 run for this datasource in ECC system, then it captures the deltas.
    Till you have pulled all the full load data to BI, but there is no data available in the delta tables for this datasource, since you have not run any V3 run for this. That is why it is showing zero from zero recrods.
    There must be some positings in ECC to the database tables related to this datasource after your initialization run, then only after running the V3 to capture the new/changed records it updates to Delta Queue (RSA7), then we will get the records to the BI.
    Otherwise check the data source data in RSA7 tcode.
    Hope this helps.
    Veerendra.

  • Problem with special extra characters

    Hi Experts,
    I´m working in SAP BW 7.0 using Data Integrator XI 3.1 with SAP BW as a target and BO DI as a source and we have some problems with the load process
    I have problems with the conversion of special characters that exist in DI and in BI arrive as an entirely different character, for example, Ñ is replaced with Å , and so on witn the á, é, í, ó, ú, etc
    In SAP BI these characters were included in the T-code RSKC (Maintenance of the permitted extra characters in BW) as special characters. In addition I tried to change the character set settings in order to use the 1100 SAP internal, like ISO 8859-1 in the infopackage but it doesn't works neither.
    The character encoding used in DI by default is utf-8.
    Can anyone hel me to solve this issue?
    Thanks in advanced.

    This worked in BW 3.5:
    Use function module RSKC_CHAVL_OF_IOBJ_CHECK to covert Special characteristics into Latin ones.
    John Hawk

  • 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();
    }

  • 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 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();

  • Problem with threads hanging

    We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
    We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
    A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
    =============================================================================================
    "ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
    at java.lang.String.substring(String.java:1446)
    at java.lang.String.substring(String.java:1411)
    at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
    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)
    =============================================================================================
    String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
    We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
    =============================================================================================
    ----------------- lwp# 44 / thread# 44 --------------------
    ff31f364 lwp_mutex_lock (e3d70)
    fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
    fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
    fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
    0) + 78
    fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
    fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
    fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
    fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
    fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
    fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
    fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
    fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
    fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
    fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
    fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
    fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
    fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
    fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
    fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
    fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
    fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
    From the thread dump:
    "VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
    From the first pstack:
    =============================================================================================
    ----------------- lwp# 2 / thread# 2 --------------------
    fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
    fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
    fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
    fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
    fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
    feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
    feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
    fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Second pstack
    =============================================================================================
    ----------------- lwp# 2 / thread# 2 --------------------
    fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
    fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
    fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
    fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
    fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
    feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
    feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
    fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
    ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
    =============================================================================================
    Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

    Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there.  Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this. 
    We're using the following memory options:
    -ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
    -verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
    Thanks!
    --Andy                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Problem with threads and ProgressMonitor

    Dear Friends:
    I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
    But I need deactivate the main class(the main class is the user interface) until the thread ends.
    I use something like this:
    LongTask myTask=new LongTask();
    myTask.start();
    myTask.join();
    Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
    What's wrong?

    Is the dialog a modal dialog? This can block other UI updates.
    In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

Maybe you are looking for

  • Indesign cc crashes

    Process:     Adobe InDesign CC [929] Path:        /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/Adobe InDesign CC Identifier:  com.adobe.InDesign Version:     9.2.0.69 (9200) Code Type:   X86-64 (Native) Parent Process:  launch

  • Mac Mini and 1080i

    Guys, I am confused. Can the mac mini 1.66 handle 1080i hdtv or not? I have seen many conflicting reports and need to know Thanks Mo!

  • Mail for changes

    Hi, How can we send mail for change in cost, budget, date  ? Also give some workflow related with PS.

  • A notice has said I am unable to access my organizer as it is not registed but it definately is?

    I have been using my Elements 10 since before Christmas and I have had this fault happen on two occasions when I try to access the organzer it come up with: Elements organizer is not currently licensed. Please launch Photoshop Elements Editor to upda

  • ROUND_UNNECESSARY - java.lang.ArithmeticException: Rounding necessary

    I am doing a BigDecimal.divide with ROUND_UNNECESSARY as my rounding mode - this is because I want the real number returned to me so that I can use my own customized rounding method. How can I accomplish this without rounding? By the way, the operati