[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: AIO error

[clebert.suconic@jboss.com]

As the close and open are both asynchronous, at high rates we could have 5 or 6 files opened what would maximize the max AIO on the OS.

I want to add a retry block on open, but since that will require some minor changes on the native layer I will leave it for Beta. My concern is this excpetion is thrown by a constructor and I'm concerned If we keep retrying to open the file, hitting the constructor and ignoring the memory created. I don't know what are the consequences and I don't have enough time to test this before alpha. A simple and easy change.. but requires testing.  (It is almost done on my workspace BTW.. but I won't commit it now)

The native layer is stable for a while already and I would like to keep as is for Alpha now.

I have added these two tasks to revisit this on Beta:

http://jira.jboss.org/jira/browse/JBMESSAGING-1350 - Revisit Error codes and messages on exceptions thrown by the native layer
http://jira.jboss.org/jira/browse/JBMESSAGING-1349 - Retry blocks on asynchronous open

Maybe I will make one tiny change on the native layer before the release that wouldn't cause any issues though... just to change that error message. (Can't initialize aio).  It is an optional task.

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

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