Update thirdparty depedencies for Naming 5.1.0.Beta1
----------------------------------------------------
Key: JBNAME-29
URL: https://jira.jboss.org/jira/browse/JBNAME-29
Project: JBoss Naming
Issue Type: Task
Components: build
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: 5.1.0.Beta1
--
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 to jboss-test 1.1.4.GA
------------------------------
Key: JBMETA-193
URL: https://jira.jboss.org/jira/browse/JBMETA-193
Project: JBoss Metadata
Issue Type: Thirdparty Change
Security Level: Public (Everyone can see)
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 1.0.0.GA
Upgrade to the latest jboss-test release.
--
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
[ https://jira.jboss.org/jira/browse/JBMETA-192?page=com.atlassian.jira.plu... ]
Alexey Loubyansky closed JBMETA-192.
------------------------------------
Resolution: Done
Done.
> create a common schema resolver for the testsuite
> -------------------------------------------------
>
> Key: JBMETA-192
> URL: https://jira.jboss.org/jira/browse/JBMETA-192
> Project: JBoss Metadata
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.0.CR18
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 1.0.0.GA
>
>
> A lot of tests are duplicating schema resolver initialization. Instead they could use a common resolver and if necessary customize it.
--
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
Improve concurrency on queue
----------------------------
Key: JBMESSAGING-1332
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1332
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta
Need to improve concurrency on queue, by implementing it with a concurrent structure.
Unfortunately ConcurrentLinkedQueue does not allow inserting elements at the head.
We can consider some kind of ConcurrentLinkedDeque
--
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
[ https://jira.jboss.org/jira/browse/JBMESSAGING-152?page=com.atlassian.jir... ]
Tim Fox updated JBMESSAGING-152:
--------------------------------
Fix Version/s: 2.0.0.CR1
(was: 2.0.0 Beta)
> Refactor exception handling
> ---------------------------
>
> Key: JBMESSAGING-152
> URL: https://jira.jboss.org/jira/browse/JBMESSAGING-152
> Project: JBoss Messaging
> Issue Type: Task
> Components: JMS Facade
> Reporter: Tim Fox
> Assignee: Tim Fox
> Priority: Minor
> Fix For: 2.0.0.CR1
>
> Original Estimate: 1 day, 4 hours
> Remaining Estimate: 1 day, 4 hours
>
> We should audit the exception handling.
> In some areas it is quite sloppy including anti-patterns such as:
> 1. Logging errors when they're not being handled
> 2. Rethrowing with less information. E.g. losing the message or original exception.
> 3. Too much usage of "throws Throwable" or "throws Exception" where probably unnecessary.
> 4. Swallowing exceptions.
> We need to go through the whole of the code, auditing and changing as necessary.
--
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
Consolidate all thread pools
----------------------------
Key: JBMESSAGING-1525
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1525
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
Currently we have too many thread pools/
These should be consolidated into a single scheduled pool and a non scheduled pool. We should also be able to specify a hard max limit on the pools
--
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