Sent to DLQ if routeFromCluster fails
-------------------------------------
Key: JBMESSAGING-1572
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1572
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0.CR1
If routeFromCluster fails e.g. if queue has been deleted after sending on source, then message should go to DLQ not be deleted.
--
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
Need to check permissions on create producer for JMS
----------------------------------------------------
Key: JBMESSAGING-1565
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1565
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0.CR1
For JMS, we need to check permissions when creating a JMS message producer. However if we do this in JBossSession (currently commented out), then sending management messages to JMS fails since there is no actual management queue.
The code in JBossSession is temporarily commented out until this is resolved.
--
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
Re-enable producer flow control when adress is full
---------------------------------------------------
Key: JBMESSAGING-1528
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1528
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
This can be done by holding back packet confirmations until more space frees up.
--
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
Client side load balancing integration tests
--------------------------------------------
Key: JBMESSAGING-1584
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1584
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
We need tests for this, that test different policies etc.
--
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
Server logs should include client's IP in case of client crash
--------------------------------------------------------------
Key: JBMESSAGING-1696
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1696
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Clebert Suconic
Assignee: Tim Fox
Fix For: 2.0.0
--
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
Statically wired clusters and initial/reconnection
--------------------------------------------------
Key: JBMESSAGING-1567
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1567
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0.CR1
Statically wired clusters have problems when a node fails, since the backup node will try and connect its bridges to the failed node when activated and just get into an endless loop doing that, since the connection manager will always try and connect on the first node
--
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
code cleanup - final fields and params
--------------------------------------
Key: JBMESSAGING-1316
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1316
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
Make sure final fields and properties are used where appropriate.
Also static inner classes are used, and fields made private.
--
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