Examples of org.mule.api.ThreadSafeAccess

org.mule.api.ThreadSafeAccess

Interface implemented by message-related objects that avoid exposing mutable data to multiple threads by providing immutable copies. This interface is optional - it is an implementation detail that is tested for dynamically and used only if available.

To avoid "scribbling" where several threads change state within in a single method (typically in inconsistent ways, causing subtle and intermittent errors) we use the following access policy for message related objects:

A new object is "unbound" and "mutable".
An object is "bound" to the first thread that calls the object after it is created.
A "mutable" object can be modified only by the thread to which it is bound.
An object is "sealed" (no longer "mutable") when it is accessed by a thread other than the thread to which it is "bound". It is an error to attempt to change a "sealed" object.

In practice this means that objects are initially mutable, but become immutable once they are shared.

    }


    public void testDisable() throws InterruptedException
    {
        assertFalse(ThreadSafeAccess.AccessControl.isFailOnMessageScribbling());
        ThreadSafeAccess target = new DefaultMuleMessage(new Object(), muleContext);
        newThread(target, false, new boolean[]{true, true, false, true});
        newThread(target, false, new boolean[]{false});
        newThread(target, false, new boolean[]{true});
    }


    @Test
    public void testDisable() throws InterruptedException
    {
        assertFalse(ThreadSafeAccess.AccessControl.isFailOnMessageScribbling());
        ThreadSafeAccess target = new DefaultMuleMessage(new Object(), muleContext);
        newThread(target, false, new boolean[]{true, true, false, true});
        newThread(target, false, new boolean[]{false});
        newThread(target, false, new boolean[]{true});
    }

Examples of org.mule.api.ThreadSafeAccess

Related Classes of org.mule.api.ThreadSafeAccess