Problems With Adium

Has anyone else experienced problems with Adium since the 10.4.11 update? It doesn't properly load my buddy list. A fix would be greatly appreciated.

Perhaps your commentary should be directed at the developers of Adium.

Similar Messages

Problem with Script in Adium

Greetings,
I'm having a problem with a Script. In Adium, I'm trying to use a Script called "quoteDB" that basically picks up a random quote from a file and shows it. Since I'd like to use it to change my display name from time to time, my problem is that the script runs every 20 seconds, so my name also changes..
My question is: does anyone knows how to configure the script "delay", I mean, how to introduce some kind of "wait" ou "idle"..
Here's the script:
on substitute(filePath)
set filePath to (filePath as alias)
open for access filePath
set raw to read filePath using delimiter "
close access filePath
set quotes to {""} as list
set j to 1
repeat with i from 1 to number of items in raw
set this_item to (text item i of raw)
if (this_item is "-") then
set quotes to quotes & ("" as item)
set j to j + 1
else
set item j of quotes to (item j of quotes & (this_item & ""))
end if
end repeat
return some item of quotes
end substitute
Thanks a lot.
rc

The statement for a delay is:
delay 60
where the time is the number of seconds (60, or one minute in my example). There is also an idle handler in a stay-open script, that uses the number of seconds returned for the interval until the next time the handler is run:
on idle
return 60
end idle
I don't know what you are using to run the script every 20 seconds (or why your name is changing), so there may be a conflict with the various timings.

Weird display problem with iMac 24"

Hi guys, I have a very weird problem with my 24" iMac. For some reason it seems that after approx. 10 minutes using the Mac, whenever I keep a window on top of another window and then I minimize it, it keeps there like a ghost for another 5-10 seconds until it fades away slowly slowly.
Sometimes it's hard to see it however it's very evident when using a white window (such as Safari) on a dark background (not black).
I'm attaching an image split into 2 parts, the 2nd part is shot exactly after I minimised the browser. It clearly shows a faded ghost image on the grey Photoshop canvas.
Here's the pic:
http://www.neilazzopardi.com/imac.jpg
Has anyone ever experienced a problem similar to mine? or am I getting paranoid?
By the way, I bought this Mac, 5 months ago and I don't know whether this problem has been there from the beginning but I only noticed recently while cropping in Photoshop and still seeing the parts I removed away very faded.

den.thed it's not that I took it the wrong way or anything but shouldn't I be doing whatever I like with my iMac?
For the record that is a dark grey Photoshop canvas, which just happens to show the problem much more evidently.
The problem is that it happens on any background (even desktop) with any window, even Adium etc. Their ghost just stays there for a while... I use the iMac for design purposes and it's very annoying especially when cropping a picture and what I just cut out stays there very faded...

A serious problem with Mac OS X

Dear Mac Community
Since I bought my first iPod (a 3G), I have been a fan of Apple. For years, I had wanted to make a switch to the Mac. About a month ago, I finally decided it was time to leave the M$ world, and bought a Mini.
My overall experience has been nearly flawless, with no crashes, truly amazing apps that are mac only (like QS, adium, spotlight and the whole iLife bundle, to name a few) and a very good looking interface.
You may've noticed the word "nearly" on the previous paragragh, and it's there for a reason. There is one serious problem I can't solve. I am Brazilian, and therefore, I speak and write mostly in Portuguese. But OS X has no support for the Brazilian layout keyboard. I have been after a solution since day 1 with my Mac, but all I have managed to find out is that there are tons of pages in the web about Portuguese speakers complaining that their keyboards don't work properly. Apparently, this has been an issue since Mac OS 10.0, and until Tiger there isn't a solution for it.
There are many different hacks to try to solve this, and I've tried every one, but they are either buggy, or don't work properly with non-universal apps (including word), or aren't 100% accurate on the keys placement.
The fact is, I write a lot for school, and I need a Brazilian layout keyboard. And my parents, who were also seriously considering switching, work a lot with translations, so it is even more important for them to have the right layout.
I am going to send a complaint for apple regarding this, but I'm skeptical that I'll get a solution, since this has been a known issue for a long time.
Sincerely
Daniel

There is another major problem with the layout I'm currently using which I forgot to say:
- I can type accented letters with almost no problem (á, à, ó, é, etc), except for "è" (e + `), which shows up simply as "e".
"That seems very strange to me. It could be something related to layout id's, which can easily be changed. Let me know if mine works with Word (I assume you are talking about Word2004 rather than the old WordX?)."
I've checked that more carefully, and here's what I've come up with: Word doesn't change the layout to US, it simply stops recognizing the 12th key (the extra one) which is responsible for "/" and "?" (and therefore is fairly important)
btw, I'm using Word 2004
"Thanks. Feel free to email me details and screenshots if you like. Since no one outside Brazil is likely to have the special keyboard with 12 keys on the bottom row, it's somewhat difficult to build and test layouts like this. (tom at bluesky dot org).
Try the one called winbrazabnt73.keylayout, which tries to put in the extra key. "
There is one problem with your layout, which is the fact that no app recognizes the 12th key responsible for "/" and "?" (including Pages, which doesn't have this problem with the other layout I'm using).
On the other hand, your layout manages to type the "è", whereas my other layout doesn't.
In the site you provided above in this thread (
http://m10lmac.blogspot.com/2007/02/fixing-brazilian-keyboard-layout.html), there is an image of different kb layouts available in Windows and OS X. If you could make the Windows Brazilian ABNT and it worked with Word, all my issues would be solved, since that's exactly the layout I'm looking for.
BTW, thanks for all the support
Best regards
Mac Mini 1.83 GHz Core Duo 1 GB Ram 80 GB HDD Mac OS X (10.4.8)

Problem with system Inactivity/Idle time after installing Lion.

Since installing Lion strange things have been happening.
While I was happily editing a text file in TextMate and interacting with the Terminal, my screen saver started. I could only get rid of it by clicking on it, keyboard interaction didn't seem to clear it.
Adium was sending lots of updates to MSN to try and update my friendly name, which was causing issues with MSN sending errors back.
After unlocking 1Password and starting to look for a username/password the application would then lock itself.
I have since disabled my screen saver, which has not appeared again. I have updated the preferences in Adium to not change my status based on system idle time, although the dock icon for it permanently displayed the Idle sign. I have also updated the preferences in 1Password to prevent auto-lock after n minutes.
Since changing these preferences I have not had any problems with the applications, however this isn't ideal. As soon as I revert these changes my problems come back.
Has anyone else had this sort of issue? Does anyone know what might be causing my system to believe that it is idle, when I am clearly interacting with it?

If I delete the existing xml file and set the file path to the desktop, the script works again. However it doesn't work if the applescript is called by another program. This seems to indicate that the XML portion if fine, but that there is some sort of new file permission level control in applescript that wasn't there before that is preventing me from viewing the file. Any further ideas?
Cheers

Problems with AIM on new iMac G5

Hi--Sorry if this is in the wrong place. I'm having an extremely frustrating problem with AIM, which I recently downloaded on my son's new iMac G5 (TIger 10.4.3). I've tried posting this question in the iChat forum, but since he doesn't use iChat and never has it open on his computer, I don't think it's an interference problem with iChat.
AIM quits unexpectedly and repeatedly, often several times in just a few minutes. I've tried: throwing out all preferences, trashing and reinstalling AIM, and using AIM from a different user account on the machine. AIM worked FINE on my computer--an older G4 also running OS Tiger, so I can't imagine that this is an operating system conflict.
A friend suggested that it might be a problem with the wireless network. The new G5 is connected wirelessly via Airport to my G4. Has anyone heard of AIM not running well on a wireless machine? Could something (an outside frequency perhaps?) be interfering with the wireless connection, causing AIM to quit?
Needless to say, AOL's tech support is completely unhelpful. Says they don't provide tech support for AIM.
If anyone can help, or knows someplace I can find AIM tech support, I would GREATLY appreciate it! THanks!

The best advice I can offer is to dump the AOL AIM client altogether, and use a third-party instant messaging application that supports AIM.
For example, Adium X is a full featured IM client that supports AIM as well as many other IM protocols.
It's very stable on Tiger, and it's light years ahead of the official AIM client from AOL.
Try it out!

Problems with Menu Bar after recent security update

Ever since installing yesterday's security update I have been having problems with the menu bar. When clicking on the blue Apple in the upper left hand corner, no drop-down menu appears as it should. This problem also occurs in the drop-down menu named for the program in various instances (Thunderbird, Azureus, iTunes, Finder, Firefox) but not in others (Safari, Adium, VLC). Sometimes the menus are simply truncated and do not include all the options they should rather than not opening at all.
I have run Disk Utlity which found no problems and have performed a hard restart multiple times but the problem persists. Any advice would be very helpful. Thank you.

Thanks for the help. I tried most of the solutions listed in the link you supplied, but am still having the same problem. However, when I tried to run the Tiger Cache Cleaner, I got the following error message:
Runtime Error 4: Failed Assertion
Location: /Volumes/RBUS/Common/MacOs/MacOSMenu.cpp:420
Failure Condition: appMenu
Failure Message:
Please report what caused this error along with the details above.
Thoughts?

Problem with 10.7.1

i've bought new imac 27" with Lion 10.7. everything was good. until i've installed 10.7.1 update today. applications unexpectedly quits (skype, adium, photoshop cs5, mail), all applications become slow down, sometimes problems with audio, sometimes hang on.
may i rollback to 10.7? and how? or maybe someone know, how to fix this problem?

Start by booting into the Recovery HD. You do this by restarting your iMac while holding down command-r, or by holding down the option key.
Once booted into Recovery HD, launch Disk Utility. Run Repair Disk repeatedly until no errors are found. Reboot into your normal boot volume, launch Disk Utility, and run Repair Permissions one time (even if errors are found and some are not corrected). Then restart one more time.
If that doesn't resolve most of your issues, you can reinstall Lion. Again, boot into Recovery HD then follow the instructions on this page:
http://support.apple.com/kb/HT4718

Another Problem With Memory..

Ok, so recently I just posted that I had a problem with mem... here is another. I just checked how much memory I'm using and it says I'm using 989 out of 1 gb.. is that normal? It was 504 about an hour ago and all I have open are Adium and Safari..

The two important questions are 1) how much is inactive and 2) how many page outs are you showing in virtual memory. In fact, the second question is the one to key on. The number of page outs will indicate how often your computer has tried to access more memory than it has and as therefore been forced to copy RAM contents to the drive so it could perform the task it was asked to do. This is when your computer is being slowly choked to death.
Now don't just open the Activity Monitor, look at the Page ins and Page outs and panic because you have 30,000 page outs. Keep in mind that's an accumulative number and if your Mac hasn't been restarted for 90 days, well that number may not be relevant at all. So restart the computer, and use it as you normally do. Then check the status of Page Outs at 30 minute intervals. The faster the Page Outs mount up with your normal usage the more you'll benefit from an upgrade.

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

Problems With Adium

Similar Messages

Maybe you are looking for