Problem with PGI

Hi Folks,
I am facing the below problem while doing PGI:
"The error message is : Goods Movement: Error Log
Account " " requires an assignment to a CO object"
Appreciate for the prompt responses.
Thanks
Krish

Hi
CO Object required to be assigned to G/L account . If you know the CO Object, go to <b>FS00</b>, enter G/L account number in Change Mode --> Goto Cost Element & Maintain CO Object. In case you do not know CO Object, ask the FI consultant to assign the same.

Similar Messages

Problem with PGI (Post Goods Issue).......?

hi Experts,
i have taken 5 materials in my sales order, and do PGI via VL01n for 3 materials.
after that we got some error in my Delivery Documents, so i reverse my Delivery document by using Tcode VA09,
after reversing, we have an option to change the Quantity of material or reduce the number of material,
but the problem is that, now i want to include the remaining 2 materials in my same delivery document.
can i do this, if YES then how?
thanks and regards,
Vishal Singh

Dear,
In VL02 on the top click on DELIVERY DOCUMENT -- DELIVER SALES ORDER -- PUT ORDER NO. and also give selection for
Line ITEM in pop screen.
Regards
AJIT K SINGH
HAPPY TO HELP U
Edited by: AJIT K SINGH on Dec 22, 2009 5:46 PM

Problem with PGI for serialized materials

Hello
We have created a delivery out of a stock transport order.
The materials are picked and we have specified which serial number were picked (the material has a serial number profile).
When performing the post goods issue for the delivery, the following error message occurs:
"Stock data of serial number 12345678 not suitable for movement
Serial number 12345678 cannot be used here"
I check the status of the related equipment via IE03 and the status is EDEL ESTO.
Could someone please help out on what is causing this error message to occur and how we can proceed with the PGI?
BR,
OT

Please check whether the following notes helps you
Note 684326 - IO231 during goods receipt
Note 316342 - IO231 during goods receipt for stock transport order
Note 712985 - IO201, IO231 and IO305 occur for a delivery goods movement
G. Lakshmipathi

Problem with PGI - Sales Order stock does not exist

Hi
I created order 58161 with 1 item line (10).
Did a delivery and created a Picking Request (which i released via transaction VL08).
When i try to do PGI i get following message:
Sales order stock 58161 000010 does not exist.
I have previously done a similar order with same material and so on and it went through the system without a hitch.
I have checked the other threads, is this where i have to use MB1B and mov.type 412 E to move unrestricted goods to sales order stock?
Thx
RM

Hi,
first u check stock at tcode:MMBE for ur material ,plant and storage location.If u dont have stock than create stock through goods receipt:mb1c.[movement type 501 e,enter ur sales order no.,item no.],I think it will solve than

Problem with pgi for returns delivery

Hi,
I'm trying to do PGI for returns delivery through BAPI_GOODSMVT_CREATE.
The when the delivery is opened through VL02N, the Post Goods Issue button has Post Goods Receipt text written on it. When the GI is done, the material document has movement type 651.
However I'm not able to create the same through the BAPI. I have tried various combinations of GM_CODE and all other variables. Have anybody of you tried doing movement type 651 for a returns delivery using the same BAPI?
Please reply if you've come across some similar situation. I know how to use the BAPI, I've been using it successfully for other movement codes etc. It's only in this case that I'm stuck up.
Regards,
Vijay

Hi Vijay,
can u pls tell me how did u do it....i am also having the same requirement....
Developed a custom program for creating and updating Goods Movement Document by using BAPI_GOODSMVT_CREATE & WS_DELIVERY_UPDATE_2.
thanks, Ankita.

Problem with Material Confirmation (Availability Check)

Dear All,
There is a problem with the availability check. when i place order system does availability check and confirms the order. Now say for example i have 100qty of material - X and i created order for 50qty, system confirmed and then i went on creating orders for this , say i have created orders for it for 150qty, so system has confirmed 100 and 50 on future date.
Now when i try to do the delievry for the first order(50 qty), system gives me an error that "0" qty is available.
Can you please tell me what may be the reason for this.
Thanks,

You can also check in T-code Co09 of the availability. Best and easy one to read for me has been MD04 Transaction code.
What system does in Sales Order is that it plans the requirement taking into consideration Material availability and if material doesn't exist but sees that in a few days in the future material will be available so system confirms it. Note that physically the material may not even be present. You find out if you really have physical stock in the delivery. For example in the sales order in the future the system sees that a Purchase Order will take place so system confirms it. Even though physically you have not even done a goods receipt for that PO. So any Sales Order which has been created before holds that reservation. So if you make a PO goods receipt in the future all those sales order has taken up this stock even. So the new sales order you created may not even have physical stock present or available as back order exists.
If you delete Deliveries that have not had PGI done to them this will take the requirement out of the list of Deliveries you can see this in MMBE if you scroll to the right. You can also do reason for rejection for other old orders to take out reservation in MD04.
Good Luck
Ali Lozada

Problem with document dates

Hello dear friends,
I have a little problem with some document dates
I've created a sales order (tcode: VA01) on 07.05.2009
After creating delivery on 25.06.2009 and doing PGI at the same day, I've created billing invoice (tcode: VF01).
I've noticed in invoice header data the following:
System shows that the invoice was created on 01.07.2009.
But, under "accounting data" tab, the system shows billing date: 26.06.2009
What's going on ? I don't seem to understand !
Regards,
Bahia.
Edited by: Bahia M. on Jul 15, 2009 3:07 PM

Dear Bahia,
> My request is: I would like to make the system brings the sales order's date as the princing date in the invoice.
While maintaining the Sales order type in VOV8 we generally maintain the setting for Pricing date proposal., please check this, i guess this is blank in your case that is why system is proposing Todays date as pricing date Please change it to B.
in Invoice as the pricing in billng is copying from the Sales order date. This control is in copy control.
For this please check these
Goto VTFL,
Select Delvery and sales document type, Click on item right side, Select the correct item category, generaly it will be TAN.
Now there is two things One is pricing source and the other is pricing type.
Make the relevant setting and try to do the cycle again and give us your feedback, i guess it will help.,
Thanks,
Raja

Problem with BAPI_SALESORDER_CHANGE function module

I know lot of posts have been done about problems with this function module. However I was not able to find the answer to my problem. Hence posting a new thread
I have the following code which changes the reason rejection (if required to 'ZF') and also updates the sales order quantity.
The code works absolutely fine as long as the PGI date of the order item is either today or in the future. However if the PGI date of the order item is in the past. I get an error in the t_return table with error type 'E' saying 'PGI date is in the past hence could not update the item'.
If I try to update the same order quantity in VA02 for the item with PGI date in the past it does so without any problem.
Can someone please suggest what the problem might be. Or if there is some other way I can update the quantity. (I dont want to use BDC)
FORM change_sales_order_item USING value(r_rtb_posnrs) TYPE zpsd_ztsdrtb_ro_track
                             CHANGING r_return TYPE type_t_bapiret2.
DATA: v_order_header_in TYPE bapisdh1,
v_order_header_inx TYPE bapisdh1x,
t_schedule_lines TYPE bapischdl OCCURS 0 WITH HEADER LINE,
t_schedule_linesx TYPE bapischdlx OCCURS 0 WITH HEADER LINE,
v_temp_rtb_vbeln TYPE vbeln,
v_temp_rtb_posnr TYPE posnr,
wa_old_rtb_posnrs TYPE ztsdrtb_ro_track,
t_item_in TYPE bapisditm OCCURS 0 WITH HEADER LINE,
t_item_inx TYPE bapisditmx OCCURS 0 WITH HEADER LINE,
v_rtb_old_vbeln TYPE zrtbvbeln,
v_rtb_old_posnr TYPE zrtbposnr,
v_ro_old_vbeln TYPE zrovbeln,
v_ro_old_posnr TYPE zroposnr,
v_rtb_count TYPE i,
v_next_row_index TYPE i,
v_update_order_flg TYPE char1, "Update the sales order flag
v_rtb_record_counter TYPE i,
v_original_vbeln TYPE vbeln,
t_bapiret TYPE STANDARD TABLE OF bapiret2.
FIELD-SYMBOLS: <wa_r_rtb_posnrs> TYPE ztsdrtb_ro_track,
                 <wa_r_rtb_posnr_next> TYPE ztsdrtb_ro_track.
CONSTANTS: c_updateflag TYPE bapisditmx-updateflag VALUE 'U'.
v_order_header_inx-updateflag = 'U'.
Get rid of the duplicate records for the same RTB order. Just use
the last record quantity in the internal table
LOOP AT r_rtb_posnrs ASSIGNING <wa_r_rtb_posnrs>.
    v_rtb_record_counter = v_rtb_record_counter + 1.
    <wa_r_rtb_posnrs>-seqnr = v_rtb_record_counter.
ENDLOOP.
SORT r_rtb_posnrs DESCENDING BY zrtbvbeln zrtbposnr seqnr zrtbconsumedflg.
DELETE ADJACENT DUPLICATES FROM r_rtb_posnrs COMPARING zrtbvbeln zrtbposnr.
DESCRIBE TABLE r_rtb_posnrs LINES v_rtb_count.
v_rtb_record_counter = 0.
v_update_order_flg = space.
LOOP AT r_rtb_posnrs ASSIGNING <wa_r_rtb_posnrs>.
    v_rtb_record_counter = v_rtb_record_counter + 1.
    v_update_order_flg = space.
Popluate the item quantity update flags for schedule lines
    t_schedule_linesx-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
    t_schedule_linesx-sched_line = '0001'.
    t_schedule_linesx-updateflag = c_updateflag.
    t_schedule_linesx-req_qty = 'X'.
    APPEND t_schedule_linesx.
    CLEAR t_schedule_linesx.
*Item (Order QQuantity Field to be changed "KWMENG")
    t_schedule_lines-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
    t_schedule_lines-sched_line = '0001'.
    t_schedule_lines-req_qty = <wa_r_rtb_posnrs>-zrtbchgqty.
    APPEND t_schedule_lines.
    CLEAR t_schedule_lines.
If fully consumed then set the rejection flag
    IF <wa_r_rtb_posnrs>-zrtbconsumedflg = 'X'.
      t_item_inx-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
      t_item_inx-updateflag = 'X'.
      t_item_inx-reason_rej = 'X'.
      APPEND t_item_inx.
      CLEAR t_item_inx.
      t_item_in-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
      t_item_in-reason_rej = 'ZF'.
      APPEND t_item_in.
      CLEAR t_item_in.
    ELSE.
      t_item_inx-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
      t_item_inx-updateflag = 'X'.
      t_item_inx-reason_rej = 'X'.
      APPEND t_item_inx.
      CLEAR t_item_inx.
      t_item_in-itm_number = <wa_r_rtb_posnrs>-zrtbposnr.
      t_item_in-reason_rej = ' '.
      APPEND t_item_in.
      CLEAR t_item_in.
    ENDIF.
If you have reached the last line of the RTB intern table update the sales order
*Index pointing to the next row
    v_next_row_index = v_rtb_record_counter + 1.
    IF v_rtb_record_counter = v_rtb_count.
      v_update_order_flg = 'X'.
    ELSEIF v_rtb_record_counter < v_rtb_count.
Get the next row data
      READ TABLE r_rtb_posnrs INDEX v_next_row_index ASSIGNING <wa_r_rtb_posnr_next>.
      IF sy-subrc = 0.
        IF <wa_r_rtb_posnrs>-zrtbvbeln <> <wa_r_rtb_posnr_next>-zrtbvbeln.
          v_update_order_flg = 'X'.
        ENDIF.
      ENDIF.
    ELSE.
      v_update_order_flg = space.
    ENDIF.
update the rtb orders with quantities and the rejection flag (if required)
    IF v_update_order_flg = 'X'.
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE' STARTING NEW TASK 'SOUPDATE'
        PERFORMING callbk_bapi_salesorder_change ON END OF TASK
        EXPORTING
          salesdocument    = <wa_r_rtb_posnrs>-zrtbvbeln
          order_header_in = v_order_header_in
          order_header_inx = v_order_header_inx
        TABLES
          return           = t_return
          schedule_lines   = t_schedule_lines
          schedule_linesx = t_schedule_linesx
          order_item_in    = t_item_in
          order_item_inx   = t_item_inx.
      WAIT UNTIL t_return[] IS NOT INITIAL.
      READ TABLE t_return INTO wa_return WITH KEY type = 'E'.
      IF sy-subrc <> 0.
      ELSE.
        r_return[] = t_return[].
        MESSAGE ID 'ZSD' TYPE 'E' NUMBER 613.
       RAISE errorinorderupdate.
      ENDIF.
      REFRESH t_schedule_linesx.
      REFRESH t_schedule_lines.
      REFRESH t_item_in.
      REFRESH t_item_inx.
      REFRESH t_return.
    ENDIF.
ENDLOOP.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
   IMPORTING
     return = t_bapiret.
ENDFORM.                    "Change_Sales_Order

see the following example and try to do this:
i_hdrx-updateflag = 'U'.
*" Fill required SCHEDULE_LINES data.
i_sched-itm_number = p_posnr.
i_sched-sched_line = p_etenr.
i_sched-req_qty = p_reqqty.
i_schedx-updateflag = 'U'.
i_schedx-itm_number = p_posnr.
i_schedx-sched_line = p_etenr.
i_schedx-req_qty = 'X'.
APPEND i_sched.
APPEND i_schedx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = p_vbeln
order_header_in = i_hdr
order_header_inx = i_hdrx
TABLES
return = i_ret
schedule_lines = i_sched
schedule_linesx = i_schedx.

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

Problem with threads and/or memory

I'm developing an application where there are 3 threads. One of them sends a request to the other, and if the 2nd can't answer it, it sends it to the 3rd (similar to CPU -> CACHE -> MEMORY). When i run the program with 1000-10.000 requests, no problem occurs. When i run it with 300.000-1.000.000 requests, it sometimes hangs. Is this a problem with the garbage collector, or should it be related to the threads mecanism.
(note: eache thread is in execution using a finite state machine)

i had been running the program inside Netbeans.
Running the jar using the command line outside
Netbeans i have no more problems... Does Netbeans use
it's own JVM?Depends how you set it up, but look under the options. There are settings for the compiler and jvm that it uses.

Problem with PGI

Similar Messages

Maybe you are looking for