Make STOP_FLUSH phase in FLUSH asynchronous
-------------------------------------------
Key: JGRP-337
URL: http://jira.jboss.com/jira/browse/JGRP-337
Project: JGroups
Issue Type: Task
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
Revert back from synchronous. Only possible if we make the STOP_FLUSH message *out-of-band* !
--
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
Define performance criteria for Remoting
----------------------------------------
Key: JBMESSAGING-718
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-718
Project: JBoss Messaging
Issue Type: Task
Components: JMS Remoting
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.CR1
Tom Elrod: Another thing I think we need to work out is some kind of criteria for knowing when remoting has reached the performance level required for messaging. Currently I have no way of knowing at what point remoting would be sufficiently fast enough.
--
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
JMS DDL should be made public and available as a script.
--------------------------------------------------------
Key: JBMESSAGING-509
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-509
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.0.1.CR4
Environment: All
Reporter: Joel Lindheimer
Assigned To: Ovidiu Feodorov
JMS DDL should be made public and available as a script. Other jboss projects like jbpm have the option of generating ddl at server startup, or not, also supply ddl generation capability. Recently (CR4) there was a release that made schema changes and problems occured from said changes. Had there been ddl files available diffs could have been done easily and the problem would have been apparent right away.
--
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
Introduce data schema backward compatibility tests
--------------------------------------------------
Key: JBMESSAGING-524
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-524
Project: JBoss Messaging
Issue Type: Task
Components: Messaging Core Persistence
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.1
Fill the database with messages using the old version and then start the new version in top of 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
centralize cache configurations
-------------------------------
Key: JBPM-787
URL: http://jira.jboss.com/jira/browse/JBPM-787
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM 3.2
Attachments: jpwh-replicated-cache-excerpt.pdf
for easier update of the cache configurations. see attachment
--
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
ByValueInvocationTestCase is broken
-----------------------------------
Key: JBREM-683
URL: http://jira.jboss.com/jira/browse/JBREM-683
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: general
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto), 2.2.0.Alpha6
The ByValueInvocationTestCase has two tests, one for jboss and one for java serialization. In each test, a remoting connector is created, but never destroyed, so on the next test run, that connector still remains (still using the same bound port).
--
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
A server needs redundant information to detect a one way invocation
-------------------------------------------------------------------
Key: JBREM-685
URL: http://jira.jboss.com/jira/browse/JBREM-685
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Minor
Fix For: 2.2.0.Alpha7
An oneway invocation is correctly processed on the server side only if:
1. It wraps an OnewayInvocation instance
2. It contains Client.ONEWAY_FLAG in its request payload metadata
This is redundant.
--
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
org.jboss.remoting.transport.socket.ServerThread keeps reference to org.jboss.ejb3.StatelessBeanContext
-------------------------------------------------------------------------------------------------------
Key: JBREM-682
URL: http://jira.jboss.com/jira/browse/JBREM-682
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.GA (Boon)
Environment: AS 4.2 (20070122)
Reporter: Carlo de Wolf
Assigned To: Tom Elrod
Priority: Critical
After undeployment, remoting still has a reference to a bean context.
--
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