Unit Testing: Added and modified methods in TransactionRepository
-----------------------------------------------------------------
Key: JBMESSAGING-679
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-679
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Juha Lindfors
Assigned To: Juha Lindfors
Fix For: 1.0.2.CR1
Write unit tests to the new and/or modified methods in TransactionRepository introduced by JBMESSAGING-407
--
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
Unit Testing: Added and modified methods in JDBCPersistenceManager
------------------------------------------------------------------
Key: JBMESSAGING-680
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-680
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Juha Lindfors
Assigned To: Juha Lindfors
Fix For: 1.0.2.CR1
Add unit tests to the added and/or modified methods in JDBCPersistenceManager
--
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
Split bridge test into multiple tests to prevent timeouts
---------------------------------------------------------
Key: JBMESSAGING-829
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-829
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.2.0.Beta2
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
The bridge test can take up to an hour to run, depending on hardware and database used.
This means junit timeout has to be increased to a large value to prevent timeouts.
Instead we should split the bridge test into smaller tests to prevent us having to have such a high timeout value.
--
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
Need to add tests for failed over queues in DefaultRouter and RoundRobinRouter
------------------------------------------------------------------------------
Key: JBMESSAGING-889
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-889
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.CR1
Reporter: Tim Fox
Assigned To: Ovidiu Feodorov
Fix For: 1.2.1
Currently there are no tests that test the new failed over queue functionality that was added
--
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
Null Pointer Exception in"org.drools.reteoo.RuleTerminalNode.retractTuple"
--------------------------------------------------------------------------
Key: JBRULES-749
URL: http://jira.jboss.com/jira/browse/JBRULES-749
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m1
Environment: Windows XP SP2, JVM1.4
Reporter: Michael Anstis
Assigned To: Mark Proctor
Attachments: Re rules-users Null Pointer Exceptioninorg.drools.reteoo.RuleTerminalNode.retractTuple.txt
Null Pointer Exception thrown when running rule "Rule-4 (Null Pointer Exception)" see attachment for complete, re-producible example.
--
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
Invalid JAXB API in jboss-messaging-client.jar
----------------------------------------------
Key: JBMESSAGING-626
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-626
Project: JBoss Messaging
Issue Type: Bug
Reporter: Thomas Diesler
Assigned To: Ovidiu Feodorov
JAXB-1.0 api leaks from jboss-messaging-client into jbossall-client.jar, which breaks the CTS
Messaging should have a dependency on jaxb-api.jar and not redistribute the jaxb api
Please fix in jbossas/branches/JEE5_TCK
--
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
InVM callbackserver
-------------------
Key: JBMESSAGING-454
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-454
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.0.1.CR3
Reporter: Tim Fox
Fix For: 1.0.2
When running with both client and server invm and using the socket transport, a callbackserver is opened on the client and creates several sockets to listen for incoming requests.
This uses up system resources (threads and sockets) which are never used for the invm case.
--
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
Description support on node elements
------------------------------------
Key: GPD-55
URL: http://jira.jboss.com/jira/browse/GPD-55
Project: JBoss jBPM GPD
Issue Type: Feature Request
Affects Versions: jBPM JPDL Designer 3.1.0.alpha2
Reporter: Koen Aers
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.alpha3
--
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