Session bean actions should happen at `SYSTEM` priority

[chris-allan]

Session bean actions should happen at SYSTEM priority so that long running user or background tasks cannot cause things like closeSession() to block for long periods of time. The Executor system thread pool is unbounded.

[sbesson]

@chris-allan

diff --git a/src/test/java/ome/server/utests/sessions/SessionBeanUnitTest.java b/src/test/java/ome/server/utests/sessions/SessionBeanUnitTest.java
index a39055eb..fdf8ee8f 100644
--- a/src/test/java/ome/server/utests/sessions/SessionBeanUnitTest.java
+++ b/src/test/java/ome/server/utests/sessions/SessionBeanUnitTest.java
@@ -111,7 +111,7 @@ public class SessionBeanUnitTest extends MockObjectTestCase {
         exMock.expects(once()).method("submit").will(new Stub(){

             public Object invoke(Invocation arg0) throws Throwable {
-                Callable callable = (Callable) arg0.parameterValues.get(0);
+                Callable callable = (Callable) arg0.parameterValues.get(1);
                 final Object rv = callable.call();
                 return new Future() {

should update the test to match the proposed implementation changes in SessionBean and fix the unit test failures.

[chris-allan]

Thanks, @sbesson.