Please confirm whether or not this is specific to SOA-P by running this on vanilla EAP.

See attached EAP_server.log.bz2 (4.3.GA server all)
No such an exception is thrown by EAP.

Attachment: Added: EAP_server.log.bz2

Thanks. Can you attach a full stack trace and indicate what version of OS/JVM you are using?

The full trace you can see in description field. Java version is sun 1.5.0_15
If you need full server logs, please look at http://hudson.qa.jboss.com/hudson/job/soa-win-scripts/217/

What version of OS? Did you run any examples before shutting down, or is this the sequence really just 'start up -> shut down'?

No, what I do is start the server, connect RMI ,check services' states and shutdown. The same I tested with EAP.

Strange, as I can't get it to fail locally. Can you append a txt file to this JIRA that contains a step-by step command-level sequence, just in case I'm missing something?

Also, what OS are you using (for the 3rd time)?

Alex - is this reproducible at will?

I *think* that I saw it once a couple of days ago (on RHEL5) - but I cannot recreate it on RHEL5 now...

I got it twice on the weekend, once on RHEL5 and once on Ubuntu. I was not able to find out steps to reproduce it. However, it was not my primary concern, so maybe I'll be more lucky today.

So - perhaps a timing issue? I still can't get the problem to recur on a RHEL5 system with this CPU - Alex - on which system are you seeing this? single CPU? Dual?

cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Pentium(R) M processor 1.70GHz
stepping        : 6
cpu MHz         : 1700.000
cache size      : 2048 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
bogomips        : 3398.33

I was able to get the problem when there was another AS or ESB instance running in the network. But in this case the user should specify UDP (-u) address or group (-g).

Just saw the WARNING message - after starting and stopping the server...

21:24:34,817 INFO  [Server] Shutdown complete
Shutdown complete
Halting VM
21:24:34,820 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)

Attachment: Added: server.log.zip

I see it on windows soa7 which is dual CPU dual core windows machine. I haven't tried a physical machine with linux (only virtual) so going to build once on such.

I see it on dev17 which is RHEL 4U6 dual Xeon 3,6GHz

Well, in a run I test server all, production and standalone. I got all three of them with the exception.
The only thing I do and you don't is checking services on the server and doing all operations without any delay. 

1.start
2.check services
3. stop

Martin sent recently sent this command "./twiddle.sh -u admin -p admin query '*:*'".

Can you try running it before shutdown?

Link: Added: This issue is related to SOA-815

Issue affects standalone server as well and is still present in IR5.

Link: Removed: This issue is related to SOA-815 

Len, can you get more info because we can't reproduce it in engineering?

Could you be more specific what do you need? I can think only of a box where you can reproduce. Or if you tell us where did you tried, I can try as well.

Just tried this with IR5.

Saw the problem on (2) of (5) tried just doing a bin/run.sh followed by control/c after the server starts.

The server.log is attached - along with the results of:  ./twiddle.sh -u admin -p admin query '*:*' from just before the server was stopped - but nothing really stands out for me.

This was all on a single CPU-system, running RHRL5.

21:28:51,789 INFO  [TomcatDeployer] undeploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
21:28:51,790 INFO  [TomcatDeployer] undeploy, ctxPath=/juddi, warUrl=.../tmp/deploy/tmp22660juddi-exp.war/
21:28:51,793 INFO  [TomcatDeployer] undeploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
21:28:51,794 INFO  [TomcatDeployer] undeploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddi.war/
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)
21:28:54,034 INFO  [TransactionManagerService] Stopping recovery manager
21:28:54,076 INFO  [Server] Shutdown complete
Shutdown complete
Halting VM

Attachment: Added: server.log
Attachment: Added: twiddle.txt

Alex - just to confirm - with IR5 you're seeing this on a Windows system? Dual processor? What % of the time are you seeing it?

I'm seeing it on RHEL with a 1.2 GHz single CPU system. 

The ONLY steps that I'm performing are run.sh and then (after the server is fully up) control C to stop it. No deployments of .esb archives or anything else. OOTB config used (HSQLDB and H2).

Yes, I see it on windows with 2 dual core CPUs. I've seen it 100% of the builds. As well I see it on linux machines. I don't perform anything than getting list or services and their states.

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

Forgot to say that thanks to Julian. ;-), This error also happens on SOA-P 4.2 CP03 standalone distribution by using the same above steps.

Inadvertently attached a 4.3 server.log yesterday - here is a 4.2 CP03 CR5 standalone log.

Attachment: Added: server_42_cp03_cr5_standalone.log.gz

Link: Added: This issue depends JBESB-2232

Link: Removed: This issue depends JBESB-2232 

JBoss Forum Reference: Added: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=147063

Link: Added: This issue is a dependency of JBAS-6326

Link: Removed: This issue is a dependency of JBAS-6326 

Link: Added: This issue depends JBAS-6326

Link: Added: This issue related SOA-1084