[JBoss JIRA] Created: (JBMESSAGING-544) Use NBIO for connection model
by Tim Fox (JIRA)
Use NBIO for connection model
-----------------------------
Key: JBMESSAGING-544
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server.
Unfortunately the JBoss remoting model does not currently allows this.
We can either drive JBoss Remoting to support this model (may take some time)
Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
This would also solve the problem of providing a functional and performant multiplex transport.
Essentially we need a bidirectional channel between jms client and server. On either end bytes can be read or witten in a non blocking fashion.
On top of that we can introduce simple framing in order to provide multiplex functionality.
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBMESSAGING-604) Duplicate message detection
by Tim Fox (JIRA)
Duplicate message detection
---------------------------
Key: JBMESSAGING-604
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-604
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
Whereas JMS requires once and only once *delivery* of messages, there are no such guarantees when sending messages to a queue/durable sub.
This can result in duplicate messages existing in a queue or durable sub.
For some clients this is unacceptable, so we should implement a feature which alerts to the presence of duplicates.
This can be done by keeping a persistent cache of message (or transaction) id on the server. Entries should time out after a period of time.
This will not remove duplicates 100% of the time since we cannot cache the previous values of id for ever, but only for a window.
See forum thread for more details
--
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
15 years, 8 months