[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1348) Re-enable INVM transport

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-1348.
--------------------------------

    Resolution: Done


> Re-enable INVM transport
> ------------------------
>
>                 Key: JBMESSAGING-1348
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1348
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Assignee: Tim Fox
>             Fix For: 2.0.0 Beta
>
>
> The INVM transport is currently disabled and should be re-enabled.
> Things that we need to do when re-enabling it
> 1) One way invocations need to be executed on a different thread (like they originally used to do) to preserve execution semantics, also to improve throughput.
> 2) OrderedExecutorFactory needs to be used also for INVM transport
> 3) Copying semantics needs to be same as TCP transport.
> With the old invm transport, the invocations were never marshalled to and from packets, this meant that extra copies had to be introduced at both sender and before sending to client to preserve JMS semantics. These copies were unnecessary for TCP transport and added extra overhead.
> The invm transport should also marshall to and from packets, the only difference being it dosn't actually use a socket, this would remove the necessity for extra copying.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira