NIO on Windows spontaneously spawning thread?

Hey guys.
I have a question concerning something odd i've noticed. When i run my NIO socket on a Windows machine and load test it then after a while (about 20-30 seconds) a new thread is spontaneously started.
One is spawner per active selector, they're unnamed threads and they're involved with this method :
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(long, int, int[], int[], int[], long) line: not available [native method]
These threads are only spawned if the server is really busy, so my questions are :
1) Why does this thread appear
2) Once it appears, does that mean my server has a problem?
I can only guess that the threads appear because my server isnt dealing with something fast enough, but i just cant seem to find details.

Oh yes? That's odd, i only see one when i reach about 1500-2000 connections. Maybe it wont get spawned until more than 64 keys are selected during a single select() or something?
I'm not liking that at all, i dont want threads to spontaneously appear. Is this Windows specific?

Similar Messages

NIO and Windows

Hallo,
I have a strange problem with nio and windows. If want to map a MappedByteBuffer to a FileChannel (read-only).
The file resides on a local hard drive.
After doing my stuff, I close the FileChannel. But as long as the jvm is running,
it is not possible to rename, delete or overwrite the file. (I'm using jre1.4.2 on Windows XP)
If I don't map the FileChannel to the MappedByteBuffer I can delete the file after closing the FileChannel.
If I call explicit the garbageCollector after using the MappedByteBuffer, I can delete the file, too.
But I dislike the idea to call the garbage collector to be able (via a side effect) to delete the file. Isn't there a better way to send the MappedByteBuffer a message, that I don't need it anymore?
Here is a test program to show my problem:
package test;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.nio.channels.FileChannel;
/** This class shows a strange behaviour on the windows platform.
public class NioTest {
     // The file must be on a local hard disk for the error to occure
     private final static File FILE = new File("C:\\map.txt");
     private static boolean withGC;
     public static void main(String[] args) throws IOException,
               InterruptedException {
          withGC = args.length > 0;
          try {
               while (true) {
                    if (FILE.exists()) {
                         System.out.println("File exist; try to overwrite");
                    } else {
                         System.out.println("File doesn't exist; try to create new one");
                    createFile();
                    lockingAction();
                    System.out.println("Seemed to work; try new iteration");
                    Thread.sleep(1 * 1000);
          } catch (IOException exp) {
               exp.printStackTrace();
     private static void lockingAction() throws IOException {
          FileChannel channel = new FileInputStream(FILE).getChannel();
          channel.map(FileChannel.MapMode.READ_ONLY, 0, channel.size());
          if (withGC) {
               // if garbage collector is called the exception doesn't occure
               Runtime.getRuntime().gc();
          channel.close();
     private static void createFile() throws IOException {
          FileOutputStream out = null;
          try {
               out = new FileOutputStream(FILE);
               out.write("Test".getBytes());
          } finally {
               if (out != null) {
                    out.close();
}

Thanks for your answer, I knew that already, but it is nowhere specified, that when the filechannel is mapped to a mapped byte buffer the file is locked.
And this only occures on windows system and not on unix systems.
There is no (?) api function to close the mapped byte buffer. All I can do is to wait that the mapped byte buffer is garbage collected. Then through the observed behaviour of the system the lock is released, but it is nowhere specified.
Because the lock is released after the m.b.b. is garbage collected it seems that there is indeed some code which released the lock.
Is there a possibility for the programmer to this functionality directly?

EJB client spawning threads

We've got problems with respect to the number of EJB client threads (ExecuteThread) spawned by WebLogic in a client JVM. As the number of threads increase (~1700 in a JVM with 512Mb of memory and 2 hours of uptime), the JVM performance degrades substantially - although almost all these threads are waiting for requests, as one can see in the thread dump attached bellow.
This problem happens in an integration scenario involving both WebLogic (8.1 and 6.1 as service providers) and webMethods Integration Server (version 6.0.1); the webMethods EJB adapter (version 1.2) acts like EJB client from the WebLogic instances, and the "EJB client spawning threads" can be detected by thread dumps extracted from the Integration Server JVM. The URL property from the wm EJB adapter has been setup as t3://server:port. The Integration Server runs with Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP), mixed mode) JRE in HP-UX (11.11) environment.
Although we couldn't reproduce this problem in a prod like environemnt, we'd identified that initially, WebLogic (weblogic.jar from WebLogic 6.1) spawns 5 ExecuteThreads plus 3 additional threads (TimeEventGenerator, SpinnerRandomSource and HighPriority TimeEventGenerator) in the first access of an EJB not matter the instance used, as well as two new threads (ExecuteThread) for each access to new WebLogic instances (different from previously accessed WebLogic instances). With weblogic.jar from the WebLogic 8.1 SP4 the behavior is slightly different: from the second instance access toward, only two new Threads (ExecuteThread in weblogic.JavaSocketReaders queue) are created.
We have also noticed that this problem should not be reflect of context classloaders because the counter of the ExecuteThread for the default pool only increases; in case of a pool cached in separate context classloaders, we should see "duplicate" threads with the same counter (starting with 0), which is not the case.
The questions are 1) why weblogic is spawning so much threads; 2) is there any setup/config to limit the number of WebLogic threads in the client context ?
Excerpt from the thread dump:
Full thread dump Java HotSpot(TM) Server VM (1.4.2 1.4.2.02-040225-19:18-PA_RISC2.0 PA2.0 (aCC_AP) mixed mode):
"ExecuteThread: '1749' for queue: 'default'" daemon prio=10 tid=05734140 nid=4813 lwp_id=583942 in Object.wait() [0x0dfbe000..0x0dfbe4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
     at weblogic.common.internal.DynaQueue.getW(DynaQueue.java:228)
     - locked <4a5ef9f0> (a weblogic.common.internal.DynaQueue)
     at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:252)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1742' for queue: 'default'" daemon prio=10 tid=04c263f0 nid=4812 lwp_id=583845 runnable [0x06449000..0x064494f0]
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:281)
     - locked <4a5ee690> (a java.net.Socket)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '1735' for queue: 'default'" daemon prio=10 tid=05733fd8 nid=4811 lwp_id=583784 in Object.wait() [0x064ca000..0x064ca4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a6b8> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a6b8> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1734' for queue: 'default'" daemon prio=10 tid=01ecd940 nid=4810 lwp_id=583783 in Object.wait() [0x0654b000..0x0654b4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a728> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a728> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1733' for queue: 'default'" daemon prio=10 tid=05733e70 nid=4806 lwp_id=583777 in Object.wait() [0x066ce000..0x066ce4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a798> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a798> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1732' for queue: 'default'" daemon prio=10 tid=01ecd7d8 nid=4801 lwp_id=583771 in Object.wait() [0x065cc000..0x065cc4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a808> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a808> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1731' for queue: 'default'" daemon prio=10 tid=05733d08 nid=4798 lwp_id=583766 in Object.wait() [0x067d0000..0x067d04f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4c40a878> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4c40a878> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
... (cut for brevity)
"ExecuteThread: '2' for queue: 'default'" daemon prio=10 tid=009251b8 nid=172 lwp_id=569500 in Object.wait() [0x3d61f000..0x3d61f4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b4498> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b4498> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '1' for queue: 'default'" daemon prio=10 tid=00924ee8 nid=171 lwp_id=569499 in Object.wait() [0x3d6a0000..0x3d6a04f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b40f0> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b40f0> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"ExecuteThread: '0' for queue: 'default'" daemon prio=10 tid=00925050 nid=170 lwp_id=569498 in Object.wait() [0x3d7a2000..0x3d7a24f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <4a5b3d48> (a weblogic.kernel.ExecuteThread)
     at java.lang.Object.wait(Object.java:429)
     at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
     - locked <4a5b3d48> (a weblogic.kernel.ExecuteThread)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
"Thread-2" daemon prio=10 tid=00bec5f0 nid=18 lwp_id=569246 in Object.wait() [0x41e2e000..0x41e2e4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
     at com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr.run(RepoServer.java:1533)
     - locked <46c14ff0> (a com.wm.app.repov4.server.RepoServer$RepoLockTimeoutMgr)
"Thread-1" daemon prio=10 tid=00bec488 nid=17 lwp_id=569244 in Object.wait() [0x41eaf000..0x41eaf4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.driver.queue.data.DataQueue.dequeue(DataQueue.java:310)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:260)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.driver.queue.data.DataQueue.dequeueCommit(DataQueue.java:254)
     - locked <46c150a8> (a com.wm.driver.queue.data.DataQueue)
     at com.wm.app.repov4.server.RepoServerBase$RepoEventManager.run(RepoServerBase.java:224)
"Log Thread" prio=10 tid=00bec320 nid=16 lwp_id=569243 in Object.wait() [0x41f30000..0x41f304f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:171)
     - locked <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.util.sync.SimpleQueue.deq(SimpleQueue.java:126)
     - locked <46c15120> (a com.wm.util.sync.SimpleQueue)
     at com.wm.app.b2b.server.ServerLogHandler$LogThread.run(ServerLogHandler.java:268)
"Cron Daemon" prio=10 tid=00bec1b8 nid=15 lwp_id=569241 in Object.wait() [0x41fb1000..0x41fb14f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15190> (a java.util.Vector)
     at com.wm.util.Cron.run(Cron.java:424)
     - locked <46c15190> (a java.util.Vector)
     at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool2" prio=10 tid=00bec050 nid=14 lwp_id=569240 in Object.wait() [0x42032000..0x420324f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15268> (a com.wm.util.pool.PooledThread)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
     - locked <46c15268> (a com.wm.util.pool.PooledThread)
     at java.lang.Thread.run(Thread.java:534)
"Cron Daemon Pool1" prio=10 tid=00bebee8 nid=13 lwp_id=569239 in Object.wait() [0x420b3000..0x420b34f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152d0> (a com.wm.util.pool.PooledThread)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.util.pool.PooledThread.run(PooledThread.java:103)
     - locked <46c152d0> (a com.wm.util.pool.PooledThread)
     at java.lang.Thread.run(Thread.java:534)
"webMethods Integration Server" prio=10 tid=000870e0 nid=12 lwp_id=569238 in Object.wait() [0x42134000..0x421344f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Object.wait(Object.java:429)
     at com.wm.app.b2b.server.Server.run(Server.java:353)
     - locked <46c152f0> (a com.wm.app.b2b.server.Server)
"Signal Dispatcher" daemon prio=10 tid=00086f78 nid=7 lwp_id=569231 waiting on condition [0x00000000..0xffffffff]
"Finalizer" daemon prio=10 tid=00086e10 nid=5 lwp_id=569229 in Object.wait() [0x4293b000..0x4293b4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
     - locked <46c15668> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
     at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:188)
"Reference Handler" daemon prio=10 tid=00086ca8 nid=4 lwp_id=569228 in Object.wait() [0x429bc000..0x429bc4f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c15340> (a java.lang.ref.Reference$Lock)
     at java.lang.Object.wait(Object.java:429)
     at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:120)
     - locked <46c15340> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=00086b40 nid=1 lwp_id=569222 in Object.wait() [0x68ff3000..0x68ff24f0]
     at java.lang.Object.wait(Native Method)
     - waiting on <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Thread.join(Thread.java:1001)
     - locked <46c152f0> (a com.wm.app.b2b.server.Server)
     at java.lang.Thread.join(Thread.java:1054)
     at com.wm.app.b2b.server.Server.start(Server.java:141)
     at com.wm.app.b2b.server.Main.main(Main.java:40)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.wm.proxy.Proxy.invokeStaticMethod(Proxy.java:166)
     at com.wm.app.server.ServerProxy.ServerMain_main(ServerProxy.java:77)
     at com.wm.app.server.ServerApp.start(ServerApp.java:105)
     at com.wm.app.Application.launch(Application.java:490)
     at com.wm.app.server.Main.main(Main.java:50)
"VM Thread" prio=7 tid=000167f8 nid=3 lwp_id=569227 runnable
"VM Periodic Task Thread" prio=8 tid=00016908 nid=11 lwp_id=569235 waiting on condition
"Suspend Checker Thread" prio=10 tid=00016880 nid=6 lwp_id=569230 runnable

We already opened a case. Actually, we did reproduce the problem: it happens because there is a hardware load balancing between the client and the WebLogic Server.
As far as I know, EJB load balancing can be done only with WebLogic clusters. Could you confirm that ?

Spawning threads from within a UnicastRemoteObject

I have a question regarding spawning threads from within a class that extends UnicastRemoteObject. Would it be okay to spawn new thread(s) in the constructor/ remote methods of the class that extends UnicastRemoteObject .? Are there any pitfalls to doing so? Is it against the suggested practice of writing RMI server code?
rajkumar

You can do anything you like in the Class that extends URO.
The classic problem of doing anything within a constructor is that the object under construction may not be available to the threads you are spawning. That is, since the object is not fully constructed, any fields the new threads need may not be available. There have been discussions on this subject in the forums before. You might give a look and see.

Spawning Threads in WebLogic - forbidden in 5.1. what about 6.x?

          Is spawning threads in 6.x permitted?
          http://websupport.beasys.com/websupport/clearexp_cgi/solution.htm?probdesc.objid=268519040


I do not think it is forbidden, but certainly not recommended. In 5.1 using user
          threads was causing all sorts of problems ranging from memory leaks (caused by
          threadlocal implementation) to mysterious exceptions when ivoking EJBs etc.
          Threadlocal was fixed in 6, but still, you can never tell what will break if you
          try to invoke WebLogic services (EJBs etc) from user threads.
          You can use this trick to borrow threads from WebLogic execute threads pool:
          http://dima.dhs.org/misc/AsyncServlet.jsp
          Mike Reiche <[email protected]> wrote:
          > Is spawning threads in 6.x permitted?
          > http://websupport.beasys.com/websupport/clearexp_cgi/solution.htm?probdesc.objid=268519040
          Dimitri

Spawning threads in application servers

Hi All,
I know spawning threads within your application server is a no no according to EJB specs. However I have a problem which calls for it!!
We are using weblogic and we are creating application logs which need to be rotated at midnight every night. The best choice would be to spawn a thread on server startup which will sleep till midnight then wake up and rotate the log.
Another choice would be to write a client program which does the same (sleeping and waking up) and then makes a request to weblogic server and the logs get rotated. However in production environemnt there will be this other new client program that will need to be deployed.
Any other ideas?
Thanks in advance for help.

If weblogic supports it you could try a 'load on startup' servlet that loops forever. You can then startup a timer to wait until the desired time and invoke a session bean to do the rotation.

Spawning thread in the stateful session bean

I ran into an interesting issue: I am spawning a thread inside
my stateful session bean's ejbCreate(...) method. The spawned
thread runs in an infinite loop until some stop signal. The
thread uses some BMP entity beans to access some data from DB,
it creates some BMP entity beans as well as creates another
stateful session bean in each iteration. The application ran
into a crash. Now I have a couple questions:
- First, is it an allowed operation to have a stateful session
bean spawn off threads? Am I violating the specs?
- Second, is it also allowed to have that thread create another
bmp entity bean and another stateful session bean? Again, am I
violating the specs also in here?
Your responses will be very much appreciated.
- Simon

From the EJB 2.0 Spec, Section 24.1.2:
<quote>
These networking functions are reserved for the EJB Container.
Allowing the enterprise bean to use these functions could compromise
security and decrease the Container’s ability to properly manage the
runtime environment.
• The enterprise bean must not attempt to manage threads. The
enterprise bean must not attempt to start, stop, suspend, or resume
a thread; or to change a thread’s priority or name. The enter-prise
bean must not attempt to manage thread groups.
<quote>
And, spawning threads in weblogic is highly discouraged in any
server-side component. An application should not be designed this
way.
Bill
Simon wrote:
I ran into an interesting issue: I am spawning a thread inside
my stateful session bean's ejbCreate(...) method. The spawned
thread runs in an infinite loop until some stop signal. The
thread uses some BMP entity beans to access some data from DB,
it creates some BMP entity beans as well as creates another
stateful session bean in each iteration. The application ran
into a crash. Now I have a couple questions:
- First, is it an allowed operation to have a stateful session
bean spawn off threads? Am I violating the specs?
- Second, is it also allowed to have that thread create another
bmp entity bean and another stateful session bean? Again, am I
violating the specs also in here?
Your responses will be very much appreciated.
- Simon

ITunes 10.4 and Windows 7 bug thread

I thought I would start an entire thread devoted to iTunes 10.4 and Windows 7 bugs since there are MANY people reporting various issues and may not know about all of them. Hopefully this will combine a list of all bugs for reference and help others. So far, most of this effects Windows 7 64 bit, but some are reporting issues under 32 bit too.
I have spoken with both Apple Care and a higher level tech at iTunes support. The iTunes support tech said they were "looking into all reported bugs and are aware of issues with version 10.4, especially under Windows 7. They encourage others to report their bugs to iTunes support so they can work on this and find all the issues.
KNOWN BUGS:
Album Art copy/paste broken - A bug that causes copy/pase from clipboard where album art is not displayed in the info tab as before. Some have reported success by dragging the image file over to it vs copy/paste method but it is still very much spotty and a known bug.
iTunes store not working - Some have been effected with the iTunes store not working properly for them. Personally I don't have a problem but this has been for some.
"Purchases" link not working in iTunes - When you click on "Purchases" link on the right column, all your purchases are missing and do not show up. This includes, music, movies, apps, etc. This is also a known bug and one that I have personally. Works fine in iTunes 10.3 for Windows 7 64bit and also works fine under both Snow Leopard and Lion OS.
Sync issues - Some have reported syncing issues since upgrading to 10.4 iTunes on Windows 7. This is a bit spotty as well as I have no trouble but there are others that have reported issues.
Solutions:
For now, the only way to fix this is to use iTunes 10.4 under Snow Leopard or Lion OS. Also, you can uninstall (not repair) 10.4 and install 10.3 again which should work.

You are correct and I wish that I had known this before spending 4 days and a lot of trouble going over this with both Apple Care and iTunes support. They had me jumping through hoops and didn't know anything until it was finally escalated. Only then did I get a vague response like I mentioned in the first post. It's troubling to me how a simple response from anyone there could've just said we know about this and they are bugs in 10.4 causing this.
There are other issues too as you point out with the syncing and crashing. Anyway, hopefully others will find information here more useful than calling Apple for help. Not much we can do now except roll back to 10.3 for those that kept it and hope also they can updated Apple Application Support component.

Spawning Threads inside the Web Container

What are the ramifications of a developer spawning off threads from a "helper"
object called from a servlet service() method ?
Thanks in advance.

That's what I said, it is not at all advisable but if you know what you
are doing it can work just fine.
The biggest issue is migration since the behavior is not defined in the
spec and thus all vendors can implement it differently and it can change
from version to version, which in turn defeats the J2EE portability
advantage.
That is why I highly recommended using JMX timers since it is going to
be available on all J2EE servers and then the only vendor dependent
thing is to get the MBeanServer.
Dejan
DN wrote:
Hello
I was also doing the same thing from my servlet but using another class which
extends thread.
I was using JDBC calls in the new thread , eventhough it worked fine I was getting
warning messages in the console when I was using WSAD.(websphere studio).
My app is deployed to WLS , i did not see any messages in WLS.
When I post this issue in a forum , some one advised me that it is not advisable
to open up threads from the servlets and this is what he said 'quote'
so eventually (i.e.
J2EE 1.4) spun threads from a Servlet accessing a
database outside of a transaction will not be
supported either.
"Deyan D. Bektchiev" <[email protected]> wrote:
Whit,
If you are not careful you can very well starve the JVM, lose your
security, transaction contexts and probably some other bad things I
don't know about...
But having said all those scary things, I must admit that we do it all
the time and don't have any issues with that.
For most purposes you should try to use the JMX timer service instead
of
spawning your own threads. You callback will be called in a different
thread from the Weblogic thread pool and I guess this will be sufficient
for most cases.
Regards,
Dejan
Whit Armstrong wrote:
What are the ramifications of a developer spawning off threads from
a "helper"
object called from a servlet service() method ?
Thanks in advance.

Why does CS6 window spontaneously collapse to a small window which cannot be resized?

I run Dreamweaver on both Mac and PC, mostly the PC. This problem has just been experienced on the PC (Windows 7 running on a Mac using Parallels). This phenomenon occurs when trying to move or resize the DW window. It has also occurred when trying to open a webpage by double clicking on it. The smaller window that results cannot be resized so I have to quit the program and restart it. When restarted it is still a small window but this version (which looks a bit different, too) can be resized. I have searched the web for discussions about this but to no avail.

I've never encountered this.
Some things to try:
Try changing your Work Space (upper right corner of interface).
Deleting Corrupted Cache in DW
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
Nancy O.

Spawning threads from a webapp

Can I spawn a thread from a webapp the same way I do in a normal java app?
Is there anything I should know before I get started doing this(i.e. special circumstances)?
Any comment are welcome, thanks in advance
silastad

anyone???, I know that you can spawn a thread from a webapp, I just want to know if there is anything in particular that I should look out for before I begin.
silastad

Windows Services, Timers & Threading

I have a self hosted WCF service. I have 2 methods that need to run periodically so the Host Service has 2 System.Threading.Timers.
Timer1 has a long running process. May take up to a minute to run.
Timer2 has a method that is quick but MUST run every 10 seconds.
My first thought was that each timer would run on a separate thread and I should be able to get this right out of the box. I was incorrect. I can't get Timer2 to be consistent because there seems to be a dependency between the two timers
and/or the server load. Timer2 doesn't give me a clean execution pattern.
In trying to fix this, I put a System.Threading.Tasks.Task around the method call on Timer1. I expected this to release resources so that Timer2 can run cleanly. Still, no luck.
This has me stumped. Any idea why Timer2 doesn't fire on a consistent pattern?
Thanks for your help, Joel.
Application Developer Manufacturing

Timer2 has a method that is quick but MUST run every 10 seconds.
Timer2 doesn't give me a clean execution pattern.
Hi Joel. What doe you mean by clean execution pattern? Is the timer taking longer than 10 seconds to execute the callback or is it random when the call back happens based on server load?
What I can tell you is that any thread execution is always dependent on the O/S. If the O/S is busy with a process dubbed as high priority which takes up all the resources then your application would also suffer as would any other application running on
that server. This could be seen in the form of threads not being allocated to run your application, timers not being fired, longer wait times than usual for resource requests etc.
As stated above if thread 1 is doing some heavy lifting and using up more CPU cycles/resources on the O/S is willing to allocate to your process then thread 1 (example of processing started on timer1) could affect thread 2 (example of processing
started on timer 2).
As far as timers go the timer is System.Threading namespace will always execute independent of each other unless you have added syncronization logic or thread 1 (example of processing started on timer1) blocks on a resource thread 2 (example
of processing started on timer 2) is requesting.
Let me know if I am way off on what I think you are asking here.
Mark as answer or vote as helpful if you find it useful | Igor

Windows 8.1: Thread Creation Error: Not enough St...

I have done all the steps
1) Reset the Internet Explorer
2) Currently haivng the latest version of Skype (7.5.64.102)
3) Latest and updated version of Windows 8.1
4) Internet Explorer version 11.0.9600.17801
Event Viewer
: Faulting application name: Skype.exe, version: 7.5.64.102, time stamp: 0x556dd607 Faulting module name: mshtml.dll, version: 11.0.9600.17801, time stamp: 0x5536793e Exception code: 0x4000001f Fault offset: 0x00db3608 Faulting process id: 0xcbc Faulting application start time: 0x01d09e3af411afc9 Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe Faulting module path: C:\Windows\SYSTEM32\mshtml.dll Report Id: 9f878ed6-0a37-11e5-bedd-a4db3020abbb Faulting package full name: Faulting package-relative application ID:
Thanks
Abhishek Alekar

Please, run the DirectX diagnostics tool.
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.

[WINDOWS] Spotify DL thread (Official links)

Official links for offline / standalone spotify installers:v1.0.10.107.gd0dfca3a-139http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.10.107.gd0dfca3a-139.exe v1.0.10.106.gccf469cc-137http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.10.106.gccf469cc-137.exe v1.0.10.104.ge563a026-136http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.10.104.ge563a026-136.exe v1.0.9.133.gcedaee38-122http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.9.133.gcedaee38-122.exe v1.0.8.59.gee82e7e6-108
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.8.59.gee82e7e6-108.exe
v1.0.8.44.g2d463d4e-99
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.8.44.g2d463d4e-99.exe
v1.0.7.157.g2a6526f9-88
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.7.157.g2a6526f9-88.exe
v1.0.6.80.g2a801a53-61
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.6.80.g2a801a53-61.exe
v1.0.5.186.ga9c24d6a-17
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.5.186.ga9c24d6a-17.exe
v1.0.5.178.g885b099b-28
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.5.178.g885b099b-28.exe
v1.0.4.90.g0b6df40b-9
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.4.90.g0b6df40b-9.exe
v1.0.4.89.g22b04e33-7
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.4.89.g22b04e33-7.exe
v1.0.3.101.gbfa97dfe-48
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.3.101.gbfa97dfe-48.exe
v1.0.3.98.g5ef498fc-41
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.3.98.g5ef498fc-41.exe
v1.0.2.6.g9977a14b-15
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.2.6.g9977a14b-15.exe
v1.0.1.1060.gc75ebdfd-220
http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.1.1060.gc75ebdfd-220.exe
How can I keep Spotify from auto updating?
This .7z includes files + instructions: https://mega.co.nz/#!uhgi1DbY!xU2ZMB-vn8accGF7L2bryS9G-uoa40UJC2Lmv3J7A_c How to find DL URL:URL base + full name of the version you want = Download link.Add version number to this:http://upgrade.spotify.com/upgrade/client/win32-x86/You will need full name of the updated exe which Spotify automatically downloads.When using the Spotify client, and you get the message "new release ready to install", the update is downloaded to a somewhat hidden folder.
Newer releases: appdata\local\spotify\update, older releases: appdata\roaming\spotify.
How to get to appdata\roaming folder:
- win+r
- type %localappdata% for appdata\local\, %appdata% for appdata\roaming\. Ex:http://upgrade.spotify.com/upgrade/client/win32-x86/spotify_installer-1.0.2.6.g9977a14b-15.exe

I need to be able to choose where CACHE is set as using a SSD which is basically for the Windows OS alone - Large amounts of data is quite happy residing on the large spinning rust drive - Also the ability to limit the amount of room Spotify uses for CACHE which was available on pre 1.x versions is needed on my other PC, still can't work out why these useful settings were removed in the first place? The ability to adjust the Song, Album, Artist, ect. widths also was useful & is there on just about every other Windows programs there has ever been, why on earth was it removed or not added as a matter of course when it was re-written. Extra features in advanced settings should have been added for those who use them rather than removing the ones already there, deault settings could have been left in for those who are happy with a vanilla program? And am I alone in not being able to drag & drop MP3's onto the playlists, something else I used to be able to do. Spotify also uses three times more RAM than version 0.7x, the list goes on ...

Thread hangs in windows XP with JRE 1.5

My java application hangs in a windows xp machine with jre 1.5. But it works fine in windows 2000 and in some other windows xp machine.
I am doing UI updates(like custom listmodels) inside the user spawn thread. I read from forums that we need to use SwingUtilities.invokeLater() in such cases. But how it then works in some windows xp machines and windows 2000 ? Am I missing anything.
Here is the thread dump :
Full thread dump Java HotSpot(TM) Client VM (1.5.0-b64 mixed mode, sharing):
"Image Animator 3" daemon prio=4 tid=0x038bab90 nid=0x9cc waiting on condition [
0x0378f000..0x0378fbe8]
at java.lang.Thread.sleep(Native Method)
at sun.awt.image.GifFrame.dispose(Unknown Source)
at sun.awt.image.GifImageDecoder.readImage(Unknown Source)
at sun.awt.image.GifImageDecoder.produceImage(Unknown Source)
at sun.awt.image.InputStreamImageSource.doFetch(Unknown Source)
at sun.awt.image.ImageFetcher.fetchloop(Unknown Source)
at sun.awt.image.ImageFetcher.run(Unknown Source)
"Thread-17" prio=7 tid=0x038baa10 nid=0x9a4 waiting for monitor entry [0x0311f00
0..0x0311fc68]
at java.awt.Component.setFont(Unknown Source)
- waiting to lock <0x17e98810> (a java.awt.Component$AWTTreeLock)
at java.awt.Container.setFont(Unknown Source)
at javax.swing.JComponent.setFont(Unknown Source)
at javax.swing.plaf.basic.BasicComboBoxRenderer.getListCellRendererCompo
nent(Unknown Source)
at javax.swing.plaf.basic.BasicListUI.updateLayoutState(Unknown Source)
at javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(Unknown Sou
rce)

Crosspost:
http://forum.java.sun.com/thread.jspa?threadID=761152&messageID=4345269#4345269

NIO on Windows spontaneously spawning thread?

Similar Messages

Maybe you are looking for