Since I've restarted the service this morning, I haven't had any issues yet.

However, I've looked at the thread dump, and I have a question.

I have quite a few threads (currently 60) such as 

"pool-component.my-file-thread-2476" prio=6 tid=0x283aead8 nid=0x19e0 in
Object.wait() [0x2c25f000..0x2c25fb9c]
        at java.lang.Object.wait(Native Method)
        - waiting on <0x0759a9b8> (a
edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock)
        at java.lang.Object.wait(Object.java:432)
        at
edu.emory.mathcs.backport.java.util.concurrent.TimeUnit.timedWait(TimeUnit.java:301)
        at
edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:349)
        - locked <0x0759a9b8> (a
edu.emory.mathcs.backport.java.util.concurrent.LinkedBlockingQueue$SerializableLock)
        at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:498)
        at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:689)
        at java.lang.Thread.run(Thread.java:595)



It appears that these threads are for a version of servicemix-file that I've
created.  (basically the same as the normal servicemix-file component, big
logic difference is that it renames the file before it processes it - needed
this due to some limitations on the systems that are creating these files)

The configuration is as follows:
4 pollers - usually on a period of 1000 ms
35 senders - some for 'debugging' purposes - others that I need to
distribute files to multiple locations


My question:

Do this sound normal? Would I expect to have thread's waiting for the
file:sender's also?


Thanks,
James
-- 
View this message in context: 
http://www.nabble.com/http-lock-up-tf3488493s12049.html#a9743776
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to