Problem with threads communication

Hi All
I have a multithreaded application in which I have 3 threads running including main thread. One of the thread (Thread1) spawned by main thread is performing the business logic required. The other one (Thread 2) is just to send the periodic signals to an admin application that it is alive. Now I need to pass some data obtained from business logic (Thread1) to the second thread (Thread2). How can i do that.? I need the data from Thread1 to Thread2 every time, the thread2 send the alive request to admin application.
Thanks & Regards
Inder Jeet Singh

See Producer/Consumer example at for 2 threads exchanging data:
http://java.sun.com/docs/books/tutorial/essential/threads/synchronization.html
In your case it seems reasonable to store data somewhere until T2 will use it during sending
alive request to admin application

Similar Messages

Problem with Thread and InputStream

Hi,
I am having a problem with threads and InputStreams. I have a class which
extends Thread. I have created and started four instances of this class. But
only one instance finishes its' work. When I check the state of other three
threads their state remains Runnable.
What I want to do is to open four InputStreams which are running in four
threads, which reads from the same url.
This is what I have written in my thread class's run method,
public void run()
     URL url = new URL("http://localhost/test/myFile.exe");
URLConnection conn = url.openConnection();
InputStream istream = conn.getInputStream();
System.out.println("input stream taken");
If I close the input stream at the end of the run method, then other threads
also works fine. But I do not want to close it becuase I have to read data
from it later.
The file(myFile.exe) I am trying to read is about 35 MB in size.
When I try to read a file which is about 10 KB all the threads work well.
Plz teach me how to solve this problem.
I am using JDK 1.5 and Win XP home edition.
Thanks in advance,
Chamal.

I dunno if we should be doing such things as this code does, but it works fine for me. All threads get completed.
public class ThreadURL implements Runnable
    /* (non-Javadoc)
     * @see java.lang.Runnable#run()
    public void run()
        try
            URL url = new URL("http://localhost:7777/java/install/");
            URLConnection conn = url.openConnection();
            InputStream istream = conn.getInputStream();
            System.out.println("input stream taken by "+Thread.currentThread().getName());
            istream.close();
            System.out.println("input stream closed by "+Thread.currentThread().getName());
        catch (MalformedURLException e)
            System.out.println(e);
            //TODO Handle exception.
        catch (IOException e)
            System.out.println(e);
            //TODO Handle exception.
    public static void main(String[] args)
        ThreadURL u = new ThreadURL();
        Thread t = new Thread(u,"1");
        Thread t1 = new Thread(u,"2");
        Thread t2 = new Thread(u,"3");
        Thread t3 = new Thread(u,"4");
        t.start();
        t1.start();
        t2.start();
        t3.start();
}And this is the o/p i got
input stream taken by 2
input stream closed by 2
input stream taken by 4
input stream closed by 4
input stream taken by 3
input stream closed by 3
input stream taken by 1
input stream closed by 1
can u paste your whole code ?
ram.

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

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 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 Receiver Communication (File Adapter)

Hi,
My SAP XI Version is 3.0 with Service Pack 7,I have a strange problem,
I have a flat file coming from Unix system,I need to convert this into XML and put a copy in the Archive mode and send the XML file,getting it converted into flat file format send it to the receiver.Here I have to do the content Conversion,So,I have done content conversion while configuring Sender and Receiver Communication Channel.
I am using NFS as Transport Proctocol.So, everthing was fine when i run the scenario,after activating.The Sender communication Channel is Archiving the files.But I am unable to see any file with receiver communication channel.
So,for this I have checked up with Adapter monitoring in Runtime Workbench. In my File Adapter My Sender as well as Receiver Communication Channels are in Green.They are mentioning that Sender Communction is sucessful and
RECEIVER COMMUNICATION IS Sucessful but no messages processed.
Can any one suggest what to do now.Everything is fine with Content conversion and Unix System.But my receiver is not receiving any messages.
Should any OSS notice or patch work needs to be applied.
Thank You,
KishoreJ.

Hi Kishore,
I Guess you should first see if the file is being picked......for that do the following.
While configuring your Sender File Adapter, let the mode be DELETE. This way, we will know if the file is being picked by the File adapter. The file will be deleted and you can be sure that it has been picked up.
Next, look into the RWB--> FILE ADAPTER and see the log of the file adapter
and also, you can see the flow of your message in the integration engine in SXMB_MONI.
Ans still if your message is not showing up in SXMB_MONI, please do as explained below.
Increase logging and trace level in:
SXMB_ADM -> Integration Engine Configuration -> Specific Configuration
Also create entries as follows in it:
LOGGING = 1
LOGGING_SYNC = 1
TRACE_LEVEL = 3
TRACE_LEVEL_PROPAGATION = 1
Also refer XI: I cannot see some of my messages in the SXMB_MONI
Regards,
Abhy

Problem with RFC Communication in BPM

Hi,
I'm again facing problem with transfer of
File->RFC->File scenario.The error in sxmb_moni is given below .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error
opening an RFC connection.</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Can anyone help me in fixing out this problem.
Regards,
Prashanth K.R,

Hi Prashant,
Just click onto your namespace and verify the details given in the "Connection data for import from SAP system". Check whether its matching the system from where you have called the RFC.
hope this will help u.
regards
divya
Message was edited by: Divya Nambiar

BT Infinity modem problem with Kelly Communication...

Hi all,
I am using Unlimited BT Infinity 1 (just for one month). I just received a call from a mobile phone regarding my broadband modem. He said he is from Kelly and there is something wrong with my broadband equipment. He is going to send an engineer to my home to change something (like taking the modem back?).
I searched on the forum and found a post about "Infinity Modem Swap & Kelly Communications" but that's about 1 year ago. In this post (http://bt.custhelp.com/app/answers/detail/a_id/37051/) it said:
"We've been working with Kelly Communications to replace the Openreach modems for some BT Infinity customers. We've now finished this work."
anyone else gets the call? not sure if it is a genuine contacts because they didnt even veryfy any account detail (but he said he knows my address).
Cheers
Chris

It could be that they have used an old modem and are going to swap it.
You could try calling BT to see if the know anything about it.
If they do come to your house make sure you verify their details and check ID card and stay with them when they change the modem over. If at all in doubt don't let them in.
If they telephone again and ask to check your computer do not let them. They have no need to do that.

Problems with Threads after upgrade to 817 on Tru64.

Hewwo.
I am wondering if you can help me with the following error and, perhaps, tell me how to relink the executables for Oracle. I cannot figure out where -laio_raw has been set. I've poured through the env*.mk files, and looked through the stuff in ~/install/utl directory, but I cannot find out how to respond to the error message below and remake the Oracle apps correctly. Surprisingly, svrmgrl works fine.
dstyo404:orafs2 50> sqlplus system/manager
Internal AIO consistency error: Cannot use libaio_raw with threads.
Either relink without -pthread or link -laio, not -laio_raw.
Aborting...
exception system: exiting due to multiple internal errors:
exception dispatch or unwind stuck in infinite loop
exception dispatch or unwind stuck in infinite loop
Thank you for your time.

To answer my own question, there is a file in $ORACLE_HOME/lib/ called "sysliblist". In order to relink the executables without aio_raw, it must be deleted from this list; and, in it's place, put "-laio". This will solve the above errors with sqlplus, exp, etc.
Hmph.
null

Problem with socket communications

I am trying to put together a client server socket communication pair.
I have one application that runs in the background acting as a server and another that can be started and stopped that acts as a client.
I can start the server and create a server socket with no problem.
I can start the client and it connects to the server.
The server acknowledges the connection and appears to go into a blocking state waiting for the client to send another message.
The server blocks at the line
parent.logit("Waiting for message from EVR..... ");
The problem is that when the client sends another message, the server doesn't hear it.
I am not sure if the problem is with the client or server communication code.
If anyone out there is a socket communication guru, I would appreciate it if you could tell me what I am doing wrong.
Thanks
Server code:
import java.io.*;
import java.net.*;
public class EVRServer
    extends Thread
EVRDataLoader parent = null;
ServerSocket serverSock = null;
Socket clientSock = null;
BufferedReader reader = null;
BufferedWriter writer = null;
int evrPort = 0;
int retryLimit = 10;
int retryCount = 0;
boolean alive = false;
boolean killSocket = false;
boolean evrConnected = false;
boolean retry = true;
EVRListener evrListener = null;
//=============================================================================
// Full constructor
//=============================================================================
   * Full constructor.
   * @param dl DataLoader - Parent application
   * @param port int Socket port
public EVRServer(EVRDataLoader dl, int port)
    parent = dl;
    evrPort = port;
//=============================================================================
// Run method - Main thread executed by start() method
//=============================================================================
   * Main thread executed by start() method
public void run()
    while (retry)
      if (retryCount > retryLimit)
        retry = false;
      parent.logit("Retry count = " + retryCount);
      // Create new server socket connection
      if (serverSock == null)
        try
          serverSock = new ServerSocket(evrPort);
          parent.logit("Created Server Socket for EVR on port " + evrPort);
          alive = true;
          killSocket = false;
          evrConnected = false;
        catch (Exception e)
          parent.logit(
              "ERROR - Could not create Server socket connection for EVR: " +
              e.toString());
          killSocket = true;
          alive = false;
      // Create new client socket connection
      if (clientSock == null)
        try
          parent.logit("Waiting for EVR to connect");
          clientSock = null;
          clientSock = serverSock.accept();
          retryCount = 0;
          evrConnected = true;
          killSocket = false;
          parent.logit("EVR connected on server Socket Port " + evrPort);
        catch (Exception e)
          parent.logit("ERROR - Error accepting EVR connection: " + e.toString());
          killSocket = true;
        try
          reader = new BufferedReader(new InputStreamReader(
              clientSock.getInputStream()));
          writer = new BufferedWriter(new OutputStreamWriter(
              clientSock.getOutputStream()));
          parent.logit( "Created reader "+reader);
          parent.logit( "Created writer "+writer);
        catch (Exception e)
          parent.logit(
              "ERROR - creating reader or writer to EVR: " + e.toString());
          killSocket = true;
      int nullCount = 0;
      while (killSocket == false)
        try
          parent.logit("Waiting for message from EVR..... ");
//          sendMessage("Data Controller connected on port " + evrPort);
          String s = reader.readLine();
          parent.logit("EVR - Received message: " + s);
          if (s != null)
            parent.processEvrMessage( s);
          else
            sleep(1000);
            nullCount++;
            if (nullCount > 10)
              parent.logit("Exceeded retry limit: ");
              killSocket = true;
        catch (Exception ex)
          parent.logit("Error Reading from EVR: " + ex.toString());
          killSocket = true;
      parent.logit( "After while loop");
      evrConnected = false;
      try
        retryCount++;
        parent.logit("Closing EVR connection. ");
        reader.close();
        writer.close();
        clientSock.close();
        writer = null;
        reader = null;
        clientSock = null;
        try
          sleep(1000);
        catch (Exception ee)
          parent.logit("Error after sleep " + ee.toString());
      catch (Exception e)
        parent.logit("Error closing EVR server socket");
//=============================================================================
// Call this method to kill the client socket connection.
//=============================================================================
   * Call this method to kill the client socket connection.
public void killConnection()
    killSocket = true;
//=============================================================================
// Return RTM connected state
//=============================================================================
   * Return RTM connected state
   * @return boolean - Returns true if RTM is connected to server, false if not.
public boolean isRtmConnected()
    return evrConnected;
//=============================================================================
// Returns state of server socket.
//=============================================================================
   * Returns state of server socket.
   * @return boolean - Returns true if server socket is enabled, false if not.
public boolean isServerSocketAlive()
    return alive;
//=============================================================================
// Send a message to the client socket.
//=============================================================================
     * Send a message to the client socket.
     * @param msg String - Message to send.
     * @return boolean - Returns true if message sent OK, false if not.
public boolean sendMessage(String msg)
    parent.logit(" In EVR Server - Send Message - got message: " + msg);
    if (evrConnected)
      try
        parent.logit("Sending message to EVR: " + msg);
        writer.write(msg + "\n");
        writer.flush();
        return true;
      catch (Exception e)
        parent.logit("ERROR - Error sending message to EVR: " + e.toString());
        return false;
    else
      parent.logit("EVR not connected, cannot send message: " + msg);
      return false;
}Client code:
package evrsimulator;
import java.net.*;
import java.io.*;
class PortConnector
      extends Thread
   ServerSocket serverSock = null;
   boolean isIP = false;
   InetAddress addr = null;
   Frame1 parent = null;
   byte[] rawIP;
    //   String initialMsg = "";
   public PortConnector( Frame1 f )
     parent = f;
   // This method is called when the thread runs
   public void run()
      if ( parent.hostName.indexOf( "." ) > 0 )
         isIP = true;
         byte[] rawIP = parent.getRawIP( parent.hostName );
      try
         System.out.println( "Connecting to host " +
                                        parent.hostName + " on port " +
                                        parent.socketPort );
         if ( isIP )
            addr = InetAddress.getByAddress( rawIP );
         else
            addr = InetAddress.getByName( parent.hostName );
         System.out.println( "Inet address = " + addr );
         SocketAddress sockaddr =
               new InetSocketAddress( addr, parent.socketPort );
         // Create an unbound socket
         parent.client = new Socket();
         // This method will block no more than timeoutMs.
         // If the timeout occurs, SocketTimeoutException is thrown.
         parent.client.connect( sockaddr, parent.socketTimeOut );
         parent.socketOut =
               new BufferedWriter( new OutputStreamWriter(
               parent.client.getOutputStream() ) );
         parent.socketIn = new BufferedReader( new InputStreamReader(
               parent.client.getInputStream() ) );
         parent.localName = parent.localName +
               parent.client;
         System.out.println( "Parent socketOut = "+parent.socketOut);
         System.out.println( "Parent socketIn = "+parent.socketIn);
      catch ( UnknownHostException uhe )
         System.out.println( "Unknown Host - " + uhe.getMessage() );
      catch ( SocketTimeoutException ste )
         System.out.println( "Socket time out - " + ste.getMessage());
      catch ( IOException ioe )
         System.out.println( "IO exception - " + ioe.getMessage() );
      // Listen on socket for message from host - thread should block.
      parent.portConnected = true;
      while ( parent.portConnected )
         try
            String msg = parent.socketIn.readLine();
            System.out.println( "Message from Host: " + msg );
            System.out.println( "Message from Host: |" + msg + "|" );
            if( msg.length() > 2)parent.processMessage( msg );
         catch ( IOException ioe )
            System.out.println( "Exception creating server socket." );
      try
         System.out.println(
               "PortConnection - Closing socket and IO connections" );
         parent.socketIn.close();
         parent.socketOut.close();
         parent.client.close();
         parent.clockRunning = false;
         if( parent.heartBeating) heartBeat.interrupt();
      catch ( IOException ioex )
         System.out.println( "Exception closing socket." );
}

Your first problem is that you keep closing and recreating the ServerSocket. Do this once only in the lifetime of the server.
This is such a basic error that I haven't read the rest of the code. Before you go any further I suggest you read the Custom Networking trail of the Java Tutorial.

Problem with java communication api for gsm modem port

Hi,every body
    Am using gsm modem in my project previously my linux is 32bit with 32 bit jvm of sun that time there was no problem at the time of working with gsm modem port .But now am using 64bit linux then 32bit files are not supporting to communicate with gsm modem port .How can i get java communication api for unix 64bit ,64bit jvm of sun.please any body help me ...i am searching in sun/oracle also for downloading java communication files of 64bit jvm but i didn't get the link... i need bellow java communication api files.
       ex:1)libLinuxSerialParallel.so
            2)javax.comm.properties
            3)comm.jar
            4)commtest.jar

Moderator Action:
This duplicate cross-post is locked.
Stay with your original post.
https://forums.oracle.com/thread/2602063
(... and your hijack reply to a third thread has been removed.)

Problem with threads communication

Similar Messages

Maybe you are looking for