AirTunes problems with 10.5.2

Hello,
after updating from 10.5.1 to 10.5.2 this week I got the problem that AirTunes doesn't work anymore.
My Aiport Express is connected to a WLAN (WPA/WPA2). Under 10.5.1 everything worked well (except the known annoyance that AirTunes doesn't work with FrontRow anymore, but ok...) But under 10.5.2 I have to reboot both my wireless routers and to restart my MacBook Pro to be able to use AirTunes. After waking up from sleeping modus or rebooting the MacBook Pro, Airtunes doesnt work, even though my speakers are displayed in Itunes. The WLAN router the AirPort Express is connected to shows that they are connected correctly. AirTunes tries to connect to the speakers, but it doesn't work, so it still displays "computer" in Itunes. Still I can choose my AirPort speakers, they are still displayed, but no connection possible. AirTunes network requires no password, I reinstalled both WLAN routers, green light on my Airport Express is on, I can ping the Airport Express, but Airtunes doesn't work and requires a fully reboot of all systems.
Using a MacBook (10.4.10) in the same WLAN everything works well.
Is there anybody facing the same problems or having an idea how to solve this problem (except downgrading to 10.5.1...)?
Thanks
Message was edited by: volloerb
Message was edited by: volloerb

Today I spent considerable time trying to track down my Airtunes problem. I disconnected and did a hard reset on my Airport Express and Airport Extreme. Rebooted my computer and tried a new Airport Express.
Most mysteriously I tried streaming to Airtunes using a G4 laptop that still has Tiger on it. I cannot use Airtunes on that either. But.... before the upgrade to 10.5.2 I could use Airtunes. This tells me it's a network problem that 10.5.2 made a change to.
Next I tried Airtunes to my Apple TV - worked fine. So Airtunes is sending the music, but the Airport Expresses are not outputting it to the speakers.
Lastly, I tried Airfoil. Same problem. It says it's connecting to my remote speakers, all appears well, but no sound. The green lights are on, the music is advancing in iTunes, and if I try to connect to computers to the remote speaker, it indicates it's already in use by another connection.
I'm at the end of my non-techie computer rope. I hope we have an answer soon. I miss my Airtunes!!

Similar Messages

ITunes with Airtunes Problems

I have a problem with iTunes/Airtunes,
I am using iTunes to access my music collection, which i consider fairly large ( approx 80Gb)
Every now and then itunes will ramdomly either skip a song half way through or it will not cross-fade its tunes. Even though the cross-fade feature is active.
I have tried reinstalling OSX and this made no difference, I have also tried resetting my airport settings ( as i play music through Airport Express) Although iTunes does this even when playing through my powerbooks speakers.
Any ideas or suggestions would be greatly appreciated as this problem is really annoying! I like iTunes and wouuld like to contunue using it but if it has bugs in it then will have fo find a new Music Player.
help?!?!?!

I have had the same experience. I am using itunes on windows xp. I have the Airport Express configured as a client and am using a Linksys as my base station.

Airtunes having problems with multiples speakers

Airtunes works very well when I just have the music play through the remote speakers. But when I try to get it to play music through both my computer's speakers and the remote speakers at the same time, I get a message saying
"An error occured while connecting to the remote speaker 'Bedroom.' An unknown error occured (-3256)."
Then the music starts playing through my computer speakers but not the remote speakers.
Any thoughts?

Never mind, I found an article in the Apple support articles telling me how to solve this issue. It was a problem with my firewall settings.

Airtunes user with a minor problem: Ethernet

Hi everyone I am a mostly satisfied Airtunes user with a minor problem I hope someone can help me with.
The Airtunes/Airport Express is working perfectly with my stereo and my usb printer. But even after reading and tinkering I cannot make it connect via ethernet to my G3 iMac.
My setup is thus: A G5 Dual 2Ghz has the Airport Extreme card inside it and the aerial attached. That's in the studio. In the lounge is the stereo, Airport Express and the printer and iMac.
I have the Airport Admin Utility 4.2 and there are no updates available according to Software Update. I don't have any security activated and have turned internet sharing off for the base station. I have turned WDS on. The amber light has been flashing since I first plugged the Express in yesterday. I'm using OSX.3.9 and the Admin Utility still says I am on a WAN Network, even though I am trying to setup a LAN thing so I can access the printer and G5 from the imac through the ethernet cable.
Reading around I have discovered advice that says things like: 'yes, you can connect via ethernet to an existing network using WDS... 'and then stops there. It doesn't say how, or if it says 'the Express base station needs a static ip for the ethernet to see it', it never says how to assign the ip, what it should be, just assumes I must know what that means, rather than going through the necessary steps.
So could someone please help with this? To me this seems the absolute most basic setup anyone would use and should be in the manual, or at least on the Airport Support site. Why can't the imac (also using OSX.3.9) scan for available networks and see what is hanging off the other end of the ethernet cable?

I could be mistaken, but I believe it is not possible to do what you are trying to do. I don't think you can connect the Airport Express via WDS to an airport card installed in a Mac.
You were correct when you enabled WDS on the Airport Express in an effort to share the internet connection, but I think you are only half-way there. I think you need to add an Airport Extreme to your network to act as the WDS master for the Airport Express.
In this case, you would put the Airport Extreme next to the G5. You would plug the internet connection (from DSL or cable or whatever) into the Airport Extreme. You would then set it up as a WDS master and add the Airport Express to the new wireless network using the Airport Utility that comes with the Airport Extreme.
Lastly, you connect the G5 wirelessly to the new network and plug the iMac into the ethernet port on the Airport Express. The iMac will not know it is on a wireless network. It will just get an address through its ethernet connection and start working.

Airport Express B/G : problems with manual IP configuration?

I don't know when it started, but I think it has something to do with one of te latest systemupdates or airport firmware updates.
Configuration :
- Airport Express N : only N, bridge mode, IP manual (192.168.1.7), roaming with Extreme N
- Airport Extreme N : only N, bridge mode, IP manual (192.168.1.35), roaming with Express N
- Airport Express B/G (older one) : B/G compatible, bridge mode, IP manual (192.168.1.8), no roaming, just stand alone.
All the airports are wired connected to a 10/100 switch.
No internet configuration on these airports, I'm using a separated router, also connected to the switch.
Problem : The airport Express B/G dissapears from the network : from time to time not visible in the airport utility program, from time to time not visible in iTunes (airtunes). In spite of these problems, he is always visible in the airport network menu. An IP ping works just fine.
When I change the IP configuration of the Airport Extreme B/G from manual to DHCP, there is NO problem anymore.
No problems with the Airport Express N an Airport Extreme N.
Are there other users with the same problem?
Thanks in advance.
Message was edited by: Mario Willen

question: i below what should i do ?
1) put a cable from my cablemodem to the airport extreme bs;
2) put a cable the airport extreme bs to the airport express bs.
Yes on both. Your network configuration would look something like the following:
Modem > (Ethernet) > \[WAN port] AEBSn \[LAN port] > (Ethernet) > AX
do i have to reset the modems and are there any setting i should be aware of ?
Yes, it's always a good idea to both reset both base stations and, after doing so and before configuring them, perform a complete power recycle of your network equipment.
So in this case ...
o Power-down the modem, AEBSn, AX, & computers. (Order is not critical.)
o Reset both the AEBSn & AX. (Again, order is not critical.)
o Power-down each base station after performing a successful reset.
o Power-up the modem; wait at least 15 minutes.
o Power-up the AEBSn; wait at least 10 minutes.
o Plug-in the AX; wait at least 5 minutes.
o Power-up your computer(s).
o Use the AirPort Utility to reconfigure both base stations as required.

ITunes/airTunes Problems

I bought my airport express a couple of months ago, it works fine connecting to the internet, but I have never been able to use airTunes. The external speaker menu does not appear in iTunes. I have tried everything that I can think of, and the people on the customer support help line weren't exactly helpful. There is an article for this problem when related to windows, but none for OSX. There have been a few iTunes updates in the last few months, but none has made any difference.
If anyone else has had this problem, or if you can think of anything that might help, please let me know; it's getting very annoying!

At the moment I'm not getting the internet through the airport, I'm just trying to use the speakers. This means it's currently flashing amber as there's no cable plugged into the ethernet port, however this doesn't seem to make any difference in connecting to it, or to the airTunes problem. But yes, in a normal situation I'm on a standard network setup as you described.
As for reinstalling MacOS, it's something that I had hoped to, and would still rather, avoid. If you think its the only other option, then how complicated is it?
one thought - is it possible that there could be a problem with the actual speaker connection on the airport itself that would prevent iTunes from recognizing them?

Airtunes Problems

I have been having a problem with iTunes and audio dropout. I have searched the forums and tried all the potential solutions without any resolution. I was convinced that I had interference on my wifi network. Then today while playing the iTunes radio through airtunes, no dropout. Try to play a song from the library, droput. Seems to me that it would indicate that the problem is with iTunes itself and how it handles the song, not interference. Any comments about this? Does anyone agree that this speaks against interference? Thanks for any input or directions

Yes, that counts. The key is to set up the AE connecting to your wireless access point, not to your local mac's connection.
I'd reset your AE. Then, If you have wireless security enabled on your wireless access point, disable it, then access the Airport Admin Utility and connect to your AE and configure it to "Joint an existing network" Enter all of the information consistant to the security that you had enabled on the Access point. Then re-enable your security on your access point, then reboot your AE.
If everything is configured properly, your AE should join your network via your Wireless access point and allow access from all of your macs.
I hope this makes sense, let me know if you have any questions!

AirTunes streaming with apps other than iTunes

I love the Dashboard "Rabbit Radio" Widget, but why can't applications other than iTunes support AirTunes streaming? I 'd like to listen to Internet Radio through the $2000 sound system the computer is connected to (through the Airport Express). Dashboard, and other applications, need audio streaming capability, just like iTunes.
It seems silly that we cannot do this. This also can be a problem with Safari as well, and other system-level or iLife applications...
Also, the last time I checked, iTunes won't even stream music video or movie audio through AirTunes-connected speakers...

Hi
Airtunes is part of iTunes, it isnt really a stand alone app.
If you dont mind paying a little, Airfoil is a great little app that allows you to stream from most other sources to your Airport Express.
With regards to video/movie audio, it does tend to get out of sync when you stream to an AE!
Will

AX not visible...sort of - Airtunes problem

In the last several weeks, I've been having Airtunes issues with my almost 2 year old AX. It runs version 6.3 firmware and I use it as a client for Airtunes only with a Buffalo router.
The green light is on. I can ping it. My router shows it is currently a connected DHCP client. However, iTunes can't see the remote speakers and the Airport Admin Utility doesn't see it.
Here's the weird part. If I rescan within the utility...nothing. If I choose other and put in the IP assigned to it (from the DHCP client table), there it is, free to configure in the utility. When I restart the AX via the utility, it shows up in the utility and iTunes can see it. It works for several hours, then it drops again.
There are no new 2.4 ghz devices in the house and interference robustness on the AX is "on".
Any thoughts?

Update to my previous question:
After some reflection, since I could ping the AX, I began getting suspicious that it was not the problem.
First, I've figured out that I lose my AX connection after I close the lid to the iBook and reopen it, even for a second. Therefore, sleep seems to induce the issue.
Second, after some serious screwing around to get a copy of the new Airport Utility for Windows, I loaded it to my XP machine. I'm now seeing that my XP desktop can see the AX with no problem, while my iBook cannot. That leads me to suspect a software update glitch with the recent security update for 10.3.9. The XP machine is hard wired to the router, the AX is set up wirelessly, as is the iBook.
This leads to a few new questions (recognizing that I'm not upgrading to 10.4 until I get a new laptop):
1. Does my software update hypothesis seem sound?
2. If so, can I roll back to where I was before that security update?
3. When the airport admin utility or iTunes is launched, is it the AX or the program (AAU or iTunes) that initiates the contact? If it's the latter, it seems more like a software problem on the computer side, rather than the AX side.
4. And to help build a corollary based on the answer to question 3, does AAU and the iTunes "Search for Remote Speakers" function rely on the same underlying piece of code?
My next task will be to slap a wireless adapter to my desktop to see if that has anything to do with anything.

Airtunes distortion with wireless clients

I have a wireless network that consists of an Apple Snow Airport Extreme and Apple TV. My MacPro is connected via Ethernet to the Airport Extreme. I regularly play music from my MacPro through my Apple TV with no issues.
But... anyone that comes by with their laptop and connects wirelessly to play music though my Apple TV has a serious problem. The audio is distorted and sounds awful, like it has too much gain and distorts with the last 8-12db of headroom.
Has anyone experienced this? I used to use an Airport Express to play music though my stereo and had the exact same issue. Without doing a lot of experimenting, this issue seems to be related to wireless clients using Airtunes but may be more pervasive.
Any other insight or experiments would be helpful.

Just purchased a new Airport Extreme (gigabit) and still have the problem with:
*) Wireless client
*) Wireless music playback (AppleTV, Airport Express)
using Airtunes in iTunes.
This makes no sense that I am the only person having this issue. I have tried a different base station, different playback device, and different wireless client. This is a brand new configuration.
Things still work fine with my MacPro connected via ethernet to the Airport, streaming wirelessly to the AppleTV.
Anybody?

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

AirTunes problems with 10.5.2

Similar Messages

Maybe you are looking for