java.lang.InterruptedException in NewMsgsWorker

[jeff.yuchang]

Hi All,

While working on this issue (https://jira.jboss.org/jira/browse/SOA-708), I got the following exceptions when I press 'Ctrl + C' to shutdown the AS.

========================================
21:28:52,820 INFO [HypersonicDatabase] Database standalone closed clean
21:28:52,919 WARN [NewMsgsWorker] Interrupted waiting for new msg check
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at EDU.oswego.cs.dl.util.concurrent.Semaphore.acquire(Semaphore.java:108)
at EDU.oswego.cs.dl.util.concurrent.SemaphoreControlledChannel.take(SemaphoreControlledChannel.java:131)
at org.jboss.resource.adapter.mail.inflow.NewMsgsWorker.run(NewMsgsWorker.java:75)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
====================================

Detailed information from dump thread as following:

===========================================
"WorkManager(2)-1" daemon prio=1 tid=0x5bee9360 nid=0x4d88 in Object.wait() [0x5bc73000..0x5bc73db0]
at java.lang.Object.wait(Native Method)
- waiting on <0x85628290> (a EDU.oswego.cs.dl.util.concurrent.Semaphore)
at java.lang.Object.wait(Object.java:474)
at EDU.oswego.cs.dl.util.concurrent.Semaphore.acquire(Semaphore.java:108)
- locked <0x85628290> (a EDU.oswego.cs.dl.util.concurrent.Semaphore)
at EDU.oswego.cs.dl.util.concurrent.SemaphoreControlledChannel.take(SemaphoreControlledChannel.java:131)
at org.jboss.resource.adapter.mail.inflow.NewMsgsWorker.run(NewMsgsWorker.java:75)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
=======================================

Can someone please shed me some light on this? What cause would it be?

Thanks
Jeff

[vickyk]

"jeff.yuchang" wrote:
Hi All,

While working on this issue (https://jira.jboss.org/jira/browse/SOA-708), I got the following exceptions when I press 'Ctrl + C' to shutdown the AS.

You are seeing the WARN message and not the EXCEPTION, WARN!=EXCEPTION ;)
Looks Ctrl+C is causing the interrupted exception at java.util.concurrent.PriorityBlockingQueue.take().
You can write the standalone application to test this scenario, how is this causing problem to you?

[jeff.yuchang]

Thanks for your reply.

Well, the case is that in some cases, we didn't see this warning, while some of them are. So I am wondering if there are any potential issues.

Just like I described in the https://jira.jboss.org/jira/browse/SOA-708,

======================
Got this error reproduced against SOA-P 4.3.0.GA. Both the standalone and embedded version.

Steps to reproduce the error:

1. start the server, bin/run.sh (for embedded version, I ran bin/run.sh -c default)
2. Open another window, go to the samples/quickstarts/bpm_orchestration2
ant deploy
ant deployProcess
ant startProcess
3. Press 'Ctrl + C' in the server window.

But the interesting thing is that this error didn't happen on jbossesb-server-4.4.GA
=====================

[vickyk]

"vickyk" wrote:
java.util.concurrent.PriorityBlockingQueue.take().

It should be java.util.concurrent.PriorityBlockingQueue
http://anonsvn.jboss.org/repos/jbossas/tags/JBPAPP_4_3_0_GA/connector/src/main/org/jboss/resource/adapter/mail/inflow/NewMsgsWorker.java
The util concurrent package is used in Jboss5.

[akostadinov]

The problem is that if message is harmless:
* but still potentially useful it needs to go out of level INFO
* and useless, then it doesn't need to be logged at all

And if the message indicated any problem, then the problem needs to be fixed...