Automate the trailblazer as part of QA
--------------------------------------
Key: JBESB-145
URL: http://jira.jboss.com/jira/browse/JBESB-145
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Examples, Testing
Affects Versions: 4.0 Beta 1
Reporter: Mark Little
Assigned To: Daniel Brum
Fix For: 4.0
--
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
Update trailblazer to include FTP support (maybe a separate scenario)
---------------------------------------------------------------------
Key: JBESB-166
URL: http://jira.jboss.com/jira/browse/JBESB-166
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Mark Little
Assigned To: Daniel Brum
Priority: Minor
Fix For: 4.0
--
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
Hosting trailblazer on docs site
--------------------------------
Key: JBESB-133
URL: http://jira.jboss.com/jira/browse/JBESB-133
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation, Testing
Affects Versions: 4.0 Beta 1
Reporter: Mark Little
Assigned To: Daniel Brum
Priority: Minor
Fix For: 4.0
We should look at hosting the TB here along with some good writeup on it, diagrams explaining each step of the way, etc...
http://www.jboss.com/docs/demos
--
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
Make sure code is more defensive against errors
-----------------------------------------------
Key: JBESB-274
URL: http://jira.jboss.com/jira/browse/JBESB-274
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: ESB Core
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 5.0
--
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
Support JBoss Messaging
-----------------------
Key: JBADMCON-149
URL: http://jira.jboss.com/jira/browse/JBADMCON-149
Project: JBoss Admin Console
Issue Type: Feature Request
Components: General Console
Affects Versions: 1.1 alpha
Reporter: chi lin
Assigned To: chi lin
Fix For: 1.1 alpha
Since JBoss Messaging will be the default JMS provider for JBoss AS 5.x, the Admin Console should support JBoss Messaging instead of (or in addition to) JBossMQ.
--
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
Investigate message priority in presence of prefetching
-------------------------------------------------------
Key: JBMESSAGING-628
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-628
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.0.Beta1
A user has observed non optimal delivery of messages based on priority.
We need to investigate to see if there is indeed an issue here, and if/what we need to do about it.
--
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
Recovery extensions mentioned more than once in property file.
--------------------------------------------------------------
Key: JBTM-168
URL: http://jira.jboss.com/jira/browse/JBTM-168
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.2
Reporter: Mark Little
Assigned To: Kevin Conner
Priority: Minor
Fix For: 4.4
--
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
Race in creating new counters
-----------------------------
Key: JBMESSAGING-616
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-616
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.0.Beta1
When creating a new counter with the same name from different nodes in a clustered config, it is possible they could be created at the same time (since the select.. for update) needs an actual row to lock.
--
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