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
support value classes in EJBQLToSQL92Compiler
---------------------------------------------
Key: JBAS-3983
URL: http://jira.jboss.com/jira/browse/JBAS-3983
Project: JBoss Application Server
Issue Type: Support Patch
Security Level: Public (Everyone can see)
Components: CMP service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Alexey Loubyansky
Assigned To: Alexey Loubyansky
The EJBQLToSQL92Compiler doesn't support value classes in paths.
--
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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-122?page=all ]
Jerry Gauthier resolved JBCLUSTER-122.
--------------------------------------
Resolution: Done
This work was completed by Brian when he modified the ClusterPartition implementation to use a multiplexed channel. Consequently the partition and the HA-JNDI implementations share a channel.
> Modify HA-JNDI TreeCache implementation so that it doesn't use RpcTreeCache
> ---------------------------------------------------------------------------
>
> Key: JBCLUSTER-122
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-122
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Jerry Gauthier
> Assigned To: Jerry Gauthier
>
> JBCLUSTER-4 modified HA-JNDI implementation to be based upon RpcTreeCache. It needs to be modified to use TreeCache instead with RPC functionaiity obtained from multiplexer channel used by HAPartition.
--
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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-122?page=all ]
Jerry Gauthier closed JBCLUSTER-122.
------------------------------------
> Modify HA-JNDI TreeCache implementation so that it doesn't use RpcTreeCache
> ---------------------------------------------------------------------------
>
> Key: JBCLUSTER-122
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-122
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Jerry Gauthier
> Assigned To: Jerry Gauthier
>
> JBCLUSTER-4 modified HA-JNDI implementation to be based upon RpcTreeCache. It needs to be modified to use TreeCache instead with RPC functionaiity obtained from multiplexer channel used by HAPartition.
--
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
[ http://jira.jboss.com/jira/browse/JBRULES-360?page=comments#action_12351220 ]
cgs commented on JBRULES-360:
-----------------------------
Is this a huge project? Does anyone else care about this? Are there any major pitfalls or concerns that would make this more difficult than it seems?
> Add support for nested properties in rules
> ------------------------------------------
>
> Key: JBRULES-360
> URL: http://jira.jboss.com/jira/browse/JBRULES-360
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Reporter: Jacek Olszak
> Assigned To: Mark Proctor
>
> Add support for nested properties in rules:
> for example:
> class Person {
> private Room room;
> ...
> }
> class Room {
> private String name
> ...
> }
> rule "some rule" {
> when
> Person(room.name="asdasdasd")
> then
> . ...
> }
--
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
better logging for business interface problems
----------------------------------------------
Key: EJBTHREE-839
URL: http://jira.jboss.com/jira/browse/EJBTHREE-839
Project: EJB 3.0
Issue Type: Feature Request
Affects Versions: EJB 3.0 RC9 - Patch 1
Reporter: William DeCoste
Assigned To: William DeCoste
Priority: Minor
Fix For: EJB 3.0 RC10 - FD
Logging for business interface problems does not include the ejb name
--
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