[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Weird deadlock I had today...

[timfox]

"clebert.suconic at jboss.com" wrote : What happened on my test was a call to close taking longer than PING_TIME.
  | 
  | The test was sending 100 messages, in 10 threads. All the sends were being performed asynchronously, and every PersistentMessage sent was syncing the page (it would be same effect on Journal if using NIO). When close was called, it had to wait the pending commands to finish, what took longer than the PING_TIME.
  | 
  | But you shouldn't have a DeadLock on that case.. right?
  | 
  | 

Why are you waiting for completion at close?

For non transactional persistent messages you should be waiting for completion at send time, and for transactional at commit. In no case should you be waiting for completion at close.

It's crucial that all commands can execute quickly so they prevent the remoting thread from executing other commands

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194207#4194207

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194207