[ http://jira.jboss.com/jira/browse/JBMESSAGING-402?page=all ]
Ovidiu Feodorov updated JBMESSAGING-402:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.2)
> Update the EJB3 example so it work with the latest EJB3 release.
> ----------------------------------------------------------------
>
> Key: JBMESSAGING-402
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-402
> Project: JBoss Messaging
> Issue Type: Task
> Affects Versions: 1.0.1.CR2
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Currently, it works with EJB 3.0 RC5 - PFD , but seems to break for EJB 3.0 RC7 - FD
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-265?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-265:
---------------------------------------------
Andy: This task is about *creating* a soak test, and not automating it. It does not belong to the QA team.
> Soak tests
> ----------
>
> Key: JBMESSAGING-265
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-265
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Ovidiu Feodorov
> Fix For: 1.0.2
>
>
> A test that runs long enough and sends a significant number of messages into the server; used to detect memory leaks and failure under load
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-393?page=all ]
Ovidiu Feodorov closed JBMESSAGING-393.
---------------------------------------
Fix Version/s: 1.0.1.CR4
(was: 1.0.2)
Resolution: Done
> Remove the serverless packages from CVS
> ---------------------------------------
>
> Key: JBMESSAGING-393
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-393
> Project: JBoss Messaging
> Issue Type: Task
> Affects Versions: 1.0.1.CR1
> Reporter: Tim Fox
> Assigned To: Ovidiu Feodorov
> Fix For: 1.0.1.CR4
>
>
> The serverless classes are not used anywhere. Should be removed from CVS.
> If we want them back they will still be in the CVS attic
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-379?page=all ]
Ovidiu Feodorov updated JBMESSAGING-379:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.2)
> Split large messages into fragments
> -----------------------------------
>
> Key: JBMESSAGING-379
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-379
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 1.2.1
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> An alternative way of dealing with very large messages than using a streamed body, is to automatically split large messages into many small fragments and send each in it's own message. These can be automatically re-assembled at the receiver.
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ]
Ovidiu Feodorov updated JBMESSAGING-153:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.2)
> JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-153
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153
> Project: JBoss Messaging
> Issue Type: Feature Request
> Components: Messaging Core
> Affects Versions: 1.0.0 alpha PR3
> Reporter: Karl de Boer
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.1
>
> Original Estimate: 4 minutes
> Remaining Estimate: 4 minutes
>
> As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications.
--
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