Problem with TMS

Hi,
I have a transport management system with 3 systems.
I delete a system on the transport controller now on the contoller appear 2 systems.
If I excute transaction STMS on the system which I deleted on the domain controller, the system has not the same configuration as domain controller. There are still 3 systems!
Is it possible to delete the system manually?
If anyone has an idea please write, its urgent!
Thank you.

Hi Andreas,
Changes in TMS configuration must be done in client 000 of the domain controller in order to affect and replicate across the 3 systems. If you want to remove one system do it form there and then just click on the distribute button.
Read more about TMS here,
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm
Hope this help
Juan
Please reward ith points if helpful

Similar Messages

Problem with TMS setup in HA systems

Dear colleagues,
Our team have installed a new production environmnent to ECC in HA. We have a ASCS in cluster and two dialog instance in each server(local instance).
A virtual host GPPR3CIB and two instances in local, node GPPR301 and node GPPR302. This is an ECC 6.0 on Windows 2003 Server and SQL server 2005.
The architecture is as follows:
- GPPR301 node:
   - Virtual ASCS ASCS_0 (message server)
   - ABAP Primary Instance PPR301_1 (disp+work)
   - ERS (Enqueue replication server) instace ERS_10
- GPPR302 node:
   -ABAP Additional Instance PPR302_2 (disp+work)
   -Virtual Database Instance GPPR3DB
   -ERS (Enqueue replication server) Instance ERS_10
Once the installation is complete you need to apply SAP Note No. 943334 - "TMS setup in high availability systems" to set up high availability STMS. The problem is to distribute the configuration after running
the report " 'TMS_MGR_LOADBALANCING" described in SAP note.
The message indicates problems trying to run the command tp.exe. It has followed the note No. 1010990 and we have checked the folder permissions of the kernel but the problem persists.
Any information or help regarding this type of setup would be welcome.
Thanks.

Hi,
We have solved the problem with STMS. After several tests, the problem was in the parameter SAPLOCALHOSTFULL. This parameter must be assigned the hostname of the local system for each profile instance. If you've assigned the virtual host in the cluster generates the error in the distribution of the STMS.
Regards.

Problem with TMS config

Hi all,
I have a problem with my TMS config.
When I adjust the transport queue, the "No system found in another group for import queue QAS" message appears.
My landscape includes a DEV-QAS and a PRD systems.
can somebody help me?
thanks in advance.

Hello,
I have the same problem. I just forund the alert from RZ20. When we are doing transport and checking RFC connections from SM59, seems to be all working fine. So I am not sure where this alert is coming from.
Command TMS_MGR_READ_TRANSPORT_QUEUE
Service Transport Service
Start Online
Function TMS_MGR_TRANSMIT_TR_QUEUE
Message TRANSMIT_QUEUE_FAILED
No system found in another group for import queue <SID>
I run into this thread but there is no information on how the problem got resolved. Please let me know if you have any ideas.
Regards,
Tony

TMS problem with ECC 6.0

Dear Global Support,
After hardware resizing we have successfully installed ECC 6.0 and
successfully performed DB restoration.
Now the problem lies with TMS as after installation performing necessary post installtion activity
we have configured TMS. As per all TMS check STMS configuration is fine. Even tp and domain
profile are generated.
But issues lies while releasing change request as after realease no data or cofile are populated in
trans/data or trans/cofile.
Even slog is not been generated. Kindly look into this and advice the needful.
Regards,
Partha

Hi Partha,
Is there only one system in the transport landscape at present?
If the transport has been built up in STMS properly, there should be no problem to export.
But you can create a virtual system and create the "transport route" accordingly.
Then when you release a transport, the data and cofiles should be generated.
Is the transport a local transport?
Do you get a message "LOCAL REQUEST .......... released(objects no longer locked)   "
Local request can not be transported so releasing a local request does
not export file to operating level.
If you want to transport this released local change request, you
can create a new reqeust of tranport type "Transport of Copies" from
SE01 and include the objects in <local transport number>.
Then you can transport the content of <local transport> by this newly created
request.
Hope this helps,
Paul

Tp ended with error code 0247 - addtobuffer has problems with data- and/or

Hello Experts,
If you give some idea, it will be greatly appreciated.
This transported issue started coming after power outage, sap system went hard shutdown.
Then we brought up the system. Before that , we do not have this transport issue.
our TMS landscape is
DEV QA-PRD
SED-SEQSEP
DEV is having the TMS domain controller.
FYI:
*At OS level, when we do scp command using root user, it is fine for any TR.
In STMS, while adding TR in SEQ(QA system), we are getting error like this.
Error:
Transport control program tp ended with error code 0247
     Message no. XT200
Diagnosis
     An error occurred when executing a tp command.
       Command:        ADDTOBUFFER SEDK906339 SEQ client010 pf=/us
       Return code:    0247
       Error text:     addtobuffer has problems with data- and/or
       Request:        SEDK906339
System Response
     The function terminates.
Procedure
     Correct the error and execute the command again if necessary.
This is tp version 372.04.71 (release 700, unicode enabled)
Addtobuffer failed for SEDK906339.
Neither datafile nor cofile exist (cofile may also be corrupted).
standard output from tp and from tools called by tp:
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0247

when we do scp using sm69,
SEDADM@DEVSYS:/usr/sap/trans/cofiles/K906339.SED SEQADM@QASYS:/usr/sap/trans/cofiles/.
it throws the error like below,
Host key verification failed.
                                                                                External program terminated with exit code 1
Thanks
Praba

Problems with transporting

Hi,
I have a problem with transporting from DEV to PROD. There are no imports in import queue in SMTS.
I can export data from DEV, but there are not displayed in STMS. (Only texts as Language Netweaver 04 SR1 CS).
In TMS alert viewer there are a lot of errors. F.E. READ_DOCU_FAILED, RFC_SYSTEM_FAILURE, TP_REPORTED_ERROR (Transport control program tp ended with error code 0012).
We had no problems with this before but the old transports are not displayed in gueue too.
The RFC connection seems to be ok.
Can anybody help?
Thanks
Radka

Hi,
it seems does not help.
But I found a problem in transport groups.
If i run a check of transport groups. The error message "System DWP cannot read test file written by DWD" is displayed.
"When the system checked the transport groups, it discovered that system DWP cannot read a test file written by system DWD to the transport directory. The return code of the action was 0008"
DWD=DEV
DWP=PROD
Can anybody help? Or does somebody know, where sap creates the test file? Or the name of the test file...
Thanks
RH

Problems with lack of connection between macs on a network.

For about a month i've had both my macbook and Mac Pro connecting fine over my network but suddenly they don't recognise each other.Is this a problem with my proxie settings within the Network Settings??.Sorry if this question is answered on the forum but i can't find it.
Message was edited by: D-Fiance

If the endpoint doesn't answer the first call, the expected behaviour should be that the TP server tries dialling again as many times as you've set in TMS, but it's only trying once for me.
This might be of interest to you, why TMS might only dial out once to an endpoint, see my reply near the end of the discussion.
conductor-telepresence-server-dial-out-and-redial-when-no-one-answer

Tuxedo 10.0 : Problem with MQ Adapter for Tuxedo

Hi,
Currently I am working over integration of tuxedo and MQ 6.0 using MQ Adapter which was included in version 10.0. During my work some problem appears, when I execute tmboot I get error message. This problem appears only with TMS when I execute adapter without TMS every thing works fine
Below I attached all the important files :
Execution of tmboot
Boot all admin and server processes? (y/n): y
Booting all admin and server processes in /tuxedo/tuxconfig
INFO: BEA Tuxedo, Version 10.0, 64-bit, Patch Level (none)
INFO: Serial #: 454493271161-2664984303294, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Customer
Booting admin processes ...
exec BBL -A :
process id=295114 ... Started.
Booting server processes ...
exec MQXA -A :
Failed.
exec MQXA -A :
Failed.
exec MQXA -A :
Failed.
exec TM_MQO -- -C file.cfg :
Failed.
1 process started.
ULOG file
174445.aix!tmloadcf.180380.1.-2: 10-15-2008: Tuxedo Version 10.0, 64-bit
174445.aix!tmloadcf.180380.1.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file /tuxedo/tuxconfig has been updated
174454.aix.maxdemo.pl!BBL.295114.1.0: 10-15-2008: Tuxedo Version 10.0, 64-bit, Patch Level (none)
174454.aix.maxdemo.pl!BBL.295114.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174454.aix.maxdemo.pl!MQXA.286894.1.0: 10-15-2008: Tuxedo Version 10.0, 64-bit
174454.aix.maxdemo.pl!MQXA.286894.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174454.aix.maxdemo.pl!MQXA.286894.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_ASYNC
174454.aix.maxdemo.pl!MQXA.286894.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
174454.aix.maxdemo.pl!MQXA.286894.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
174454.aix!tmboot.180382.1.-2: 10-15-2008: Tuxedo Version 10.0, 64-bit
174454.aix!tmboot.180382.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
174454.aix.maxdemo.pl!MQXA.315556.1.0: 10-15-2008: Tuxedo Version 10.0, 64-bit
174454.aix.maxdemo.pl!MQXA.315556.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174454.aix.maxdemo.pl!MQXA.315556.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_ASYNC
174454.aix.maxdemo.pl!MQXA.315556.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
174454.aix.maxdemo.pl!MQXA.315556.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
174454.aix!tmboot.180382.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
174454.aix.maxdemo.pl!MQXA.299166.1.0: 10-15-2008: Tuxedo Version 10.0, 64-bit
174454.aix.maxdemo.pl!MQXA.299166.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174454.aix.maxdemo.pl!MQXA.299166.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_ASYNC
174454.aix.maxdemo.pl!MQXA.299166.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
174454.aix.maxdemo.pl!MQXA.299166.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
174454.aix!tmboot.180382.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
174454.aix.maxdemo.pl!TM_MQO.303262.1.0: 10-15-2008: Tuxedo Version 10.0, 64-bit
174454.aix.maxdemo.pl!TM_MQO.303262.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174454.aix.maxdemo.pl!TM_MQO.303262.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_RMERR
174454.aix.maxdemo.pl!TM_MQO.303262.1.0: TUXMQ_CAT:1000: TPMQ_EATMI tpopen failed error = TPERMERR - resource manager error
174454.aix.maxdemo.pl!TM_MQO.303262.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() faile
174454.aix!tmboot.180382.1.-2: CMDTUX_CAT:825: ERROR: Process TM_MQO at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
UBBCONFIG with TMS ( That doesn't work )
*RESOURCES
IPCKEY 62345
MASTER MQTESTGSERVER
MAXACCESSERS 5
MAXSERVERS 5
MAXSERVICES 10
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
APPDIR="/opt/bea/tuxedo/tuxedo10.0/bin/"
TUXCONFIG="/tuxedo/tuxconfig"
TUXDIR="/opt/bea/tuxedo/tuxedo10.0/"
TLOGDEVICE="/tuxedo/logi/current"
"aix.maxdemo.pl" LMID=MQTESTGSERVER
*GROUPS
GROUP1
TMSNAME=MQXA TMSCOUNT=3 LMID=MQTESTGSERVER GRPNO=1 OPENINFO="MQSeries_XA_RMI:QUEUE.MANAGER"
*SERVERS
DEFAULT:
CLOPT="-A"
TM_MQO SRVGRP=GROUP1 SRVID=1
CLOPT="-- -C file.cfg"
*SERVICES
file.cfg
*SERVER
DEFMAXMSGLEN=2048
DEFTIMEOUT=60
*QUEUE_MANAGER
LQMID=QM1
NAME=QUEUE.MANAGER
*SERVICE
NAME=MQTEST
LQMID=QM1
TIMEOUT=30
TRAN=N
MQNAME=IN
REPLYTOQ=OUT
RM
TUXEDO/D:tuxd_switch:-lrms -lfs
TUXEDO/SQL:tuxsql_switch:-lsql -lusort -lrms -lfs
NONE:tmnull_switch:
TUXEDO/QM:tuxq_switch:-lqm -ltmib
# BEA makes no attempt to keep the information in the following samples
# up to date. To make sure you have correct and complete information for
# your platform and RM version, please consult your RM vendor.
# ORACLE 7
#Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lxa ${ORACLE_HOME}/lib/libsql.a -lora -lsqlnet -lcore -lnlsrtl -lcore ${ORACLE_HOME}/lib/osntab.o -lsqlnet -lcv6 -lora -lm -lsocke
# Oracle 9, 10
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lclntsh
# INFORMIX-Online 5
INFORMIX-OnLine:infx_xa_switch:${INFORMIXDIR}/lib/esql/libinfxxa.a -lx
# INFORMIX-Online 6
#INFORMIX-OnLine:infx_xa_switch:${INFORMIXDIR}/lib/esql/libinfxxa.a ${INFORMIXDIR}/lib/esql/libsql.a ${INFORMIXDIR}/lib/libasf.a ${INFORMIXDIR}/lib/netlib.a ${INFORMIXDIR}/lib/esql/libgen.a ${INFORMIXDIR}/lib/esql/libos.a -lsocket -lm
#ident "@(#)RM 1.3"
NONE2:tmnull2_switch:xa.o
# WebSphere MQ 6.0
MQSeries_XA_RMI:MQRMIXASwitchDynamic: /usr/mqm/lib64/libmqmxa64.a /usr/mqm/lib64/libmqm.a /usr/mqm/lib64/libmqmcs.a
UBBCONFIG (working but without TMS)
*RESOURCES
IPCKEY 62345
MASTER MQTESTGSERVER
MAXACCESSERS 5
MAXSERVERS 5
MAXSERVICES 10
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
APPDIR="/opt/bea/tuxedo/tuxedo10.0/bin/"
TUXCONFIG="/tuxedo/tuxconfig"
TUXDIR="/opt/bea/tuxedo/tuxedo10.0/"
"aix.maxdemo.pl" LMID=MQTESTGSERVER
*GROUPS
GROUP1
LMID=MQTESTGSERVER GRPNO=1 OPENINFO=NONE
*SERVERS
TM_MQO SRVGRP=GROUP1 SRVID=1
CLOPT="-- -C file.cfg"
*SERVICES
I would be thankful for any support Bartosz Chrabski
Edited by: Bartosz Chrabski on 2008-10-19 02:11

Hi,
As I changed MAXACCESSERS, MAXSERVERS, MAXSERVICES to 100, 50, 50 TM_MQO starts but MQXA still have errors during execution process:
Execution of tmboot
Boot all admin and server processes? (y/n): y
Booting all admin and server processes in /tuxedo/tuxconfig
INFO: BEA Tuxedo, Version 10.0, 64-bit, Patch Level (none)
INFO: Serial #: 454493271161-2664984303294, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Customer
Booting admin processes ...
exec BBL -A :
process id=282800 ... Started.
Booting server processes ...
exec MQXA -A :
Failed.
exec MQXA -A :
Failed.
exec MQXA -A :
Failed.
exec TM_MQO -- -C file.cfg :
process id=319576 ... Started.
2 processes started.
ULOG
125049.aix.maxdemo.pl!BBL.364726.1.0: 10-21-2008: Tuxedo Version 10.0, 64-bit, Patch Level (none)
125049.aix.maxdemo.pl!BBL.364726.1.0: LIBTUX_CAT:262: INFO: Standard main starting
125049.aix.maxdemo.pl!MQXA.282810.1.0: 10-21-2008: Tuxedo Version 10.0, 64-bit
125049.aix.maxdemo.pl!MQXA.282810.1.0: LIBTUX_CAT:262: INFO: Standard main starting
125049.aix.maxdemo.pl!MQXA.282810.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_ASYNC
125049.aix.maxdemo.pl!MQXA.282810.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
125049.aix.maxdemo.pl!MQXA.282810.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
125049.aix!tmboot.356520.1.-2: 10-21-2008: Tuxedo Version 10.0, 64-bit
125049.aix!tmboot.356520.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
125049.aix.maxdemo.pl!MQXA.319578.1.0: 10-21-2008: Tuxedo Version 10.0, 64-bit
125049.aix.maxdemo.pl!MQXA.319578.1.0: LIBTUX_CAT:262: INFO: Standard main starting
125049.aix.maxdemo.pl!MQXA.319578.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_oen returned XAER_ASYNC
125049.aix.maxdemo.pl!MQXA.319578.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
125049.aix.maxdemo.pl!MQXA.319578.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
125049.aix!tmboot.356520.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
125049.aix.maxdemo.pl!MQXA.348360.1.0: 10-21-2008: Tuxedo Version 10.0, 64-bit
125049.aix.maxdemo.pl!MQXA.348360.1.0: LIBTUX_CAT:262: INFO: Standard main starting
125049.aix.maxdemo.pl!MQXA.348360.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_ASYNC
125049.aix.maxdemo.pl!MQXA.348360.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
125049.aix.maxdemo.pl!MQXA.348360.1.0: LIBTUX_CAT:300: ERROR: tlogopen: gptblopen: UNIX sys call error - 2
125049.aix!tmboot.356520.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at MQTESTGSERVER failed with /T tperrno (TPERMERR - resource manager error)
125049.aix.maxdemo.pl!TM_MQO.344110.1.0: 10-21-2008: Tuxedo Version 10.0, 64-bit
125049.aix.maxdemo.pl!TM_MQO.344110.1.0: LIBTUX_CAT:262: INFO: Standard main starting
125049.aix.maxdemo.pl!TM_MQO.344110.1.0: TUXMQ_CAT:1055: TPMQ_INFO TM_MQO started
Edited by: Bartosz Chrabski on 2008-10-21 03:50

Problem with Creative T3100...

Hi. I have problem with my speakers. One of them (left)stops reproducing the music after 7-8 listening her.
Sound be distorted first, faint. There is no him at all in left speaker then. I checked all cables and I think everything is OK, but...what I have to do ? Subwoofer and right speaker are OK...

<FONT face="Tms Rmn" size=2>
Some of the Microsoft Jet and Microsoft MDAC files of your operating system may be corrupted. Use a MDAC repair tool from
http://www.macropool.com/en/download/mdac.html

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 TMS

Similar Messages

Maybe you are looking for