[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-216) Prepare Messaging to replace JBossMQ in the JBoss Mail distribution

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-216?page=all ]

Tim Fox closed JBMESSAGING-216.
-------------------------------

    Resolution: Won't Fix

> Prepare Messaging to replace JBossMQ in the JBoss Mail distribution
> -------------------------------------------------------------------
>
>                 Key: JBMESSAGING-216
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-216
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> Andy's input:
> does jboss messaging:
> 1. recover from outages with incomplete blobs being written?
> 2. avoid making 3 copies of a message in memory?
> 3. install cleanly on JBoss 4.0.3SP1/JDK5?
> 4. work with Postgresql, MySQL, Hypersonic?
> 5. perform better/on par with JBossMQ when used locally (no remote invocation)
> 6. Have a reasonably simple method of swapping out its persistence layer ?
> #1 is a particularly bad problem (in my view it should be detected and moved to the DMQ with a the blob truncated and a reference to the orgininal record [which should be excluded from mainstream processing by a flag])

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