Time sensitive queue
--------------------
Key: JBMESSAGING-1324
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1324
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
Add a time sensitive queue type.
with this queue, specify a header JBM_TIME_LIMITED and only latest message with value of this header is retained - internally can use LinkedHashMap instead of LinkedQueue.
--
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
Store the reference to the object instead of serializing object upon JBossObjectMessage.setObject.
--------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1167
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1167
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP1
Reporter: Jay Howell
Assigned To: Tim Fox
Object Serialization happens in the JBossObjectMessage.setObject and then the reference to the object is set to null. This means that if you are delivering messages within the same JVM, the objects still have to go through serialization. This request is to delay serialization until it needs to be sent across the wire.
This is a performance optimization aimed at preventing unnecessary serialization.
--
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
Redeploying queues with different attribute values
--------------------------------------------------
Key: JBMESSAGING-1336
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1336
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
When deploying a queue using JMSManager that already exists but has a different attribute like clustered - do we update the value of the attribute in the journal?
--
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
Reconnect to same server
------------------------
Key: JBMESSAGING-1443
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1443
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
Add reconnect to same server functionality to ClientSessionFactoryImpl.
Same failover code can be used.
--
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
JBM peer to peer mode
---------------------
Key: JBMESSAGING-1312
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1312
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
We should provide a peer to peer mode for JBM.
Can start a server in the local process and use invm transport to talk to it. The server has null persistence manager, and communicates using JGroups or UDP to other peers for fast peer to peer transport
--
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
Portlet Instance Detail Screen Break in header
----------------------------------------------
Key: JBPORTAL-2190
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2190
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.7.0 CR1
Reporter: Wesley Hales
Assignee: Wesley Hales
Keywords break when too long forcing the ui to not stretch
--
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
Open console support
--------------------
Key: JBAS-5246
URL: http://jira.jboss.com/jira/browse/JBAS-5246
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Management services, ProfileService
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.CR1
A container task for management issues affecting the open console work for CR1
--
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
Generic flags per message
-------------------------
Key: JGRP-858
URL: https://jira.jboss.org/jira/browse/JGRP-858
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
Investigate whether we can add generic flags to a message. Currently, we have a byte field and a few predefined flags (OOB, LOW_PRIO, HIGH_PRIO) in each message, but that means we only have a limited number of flags available to us.
Goal: find a way to add an infinite number of flags to a message, possibly even used defined flags. EnumSet ?
--
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
Upgrade jpa-deployers to 0.1.3
------------------------------
Key: JBAS-6112
URL: https://jira.jboss.org/jira/browse/JBAS-6112
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering, EJB3
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.0.0.GA
Update to pick up JBAS-6111 fix.
--
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
Upgrade EJB3 to its final version for AS5 GA
--------------------------------------------
Key: JBAS-6020
URL: https://jira.jboss.org/jira/browse/JBAS-6020
Project: JBoss Application Server
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: EJB3
Reporter: Dimitris Andreadis
Assignee: Carlo de Wolf
Priority: Critical
Fix For: JBossAS-5.0.0.GA
Whichever will be the final version for AS5 GA and passes EJB3's own testsuite.
--
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