Create a set of deadlock-detecting unit tests
---------------------------------------------
Key: JBCACHE-759
URL: http://jira.jboss.com/jira/browse/JBCACHE-759
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 1.4.0
Reporter: Manik Surtani
Assigned To: Manik Surtani
Fix For: 2.0.0
>From email thread:
"Okay, found out that jconsole also supports it:
MBeans --> java.lang --> Threading --> Operations --> findMonitorDeadlockedThreads().
Of course, if we could integrate this into our test suites to regularly check for deadlocks..."
Article from JavaSpecialists:
http://www.javaspecialists.co.za/archive/newsletter.do?issue=130&locale=e...
--
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
First concurrent call doesn't throw exception
---------------------------------------------
Key: EJBTHREE-697
URL: http://jira.jboss.com/jira/browse/EJBTHREE-697
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Carlo de Wolf
Priority: Critical
Fix For: EJB 3.0 RC10 - FD
Concurrency check is in the server interceptor, while identity is established in the proxy after the first call. So if the first call is concurrent no exception is thrown. (see unit test concurrent)
--
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
Wizard for autopopulating a decision table
------------------------------------------
Key: JBRULES-479
URL: http://jira.jboss.com/jira/browse/JBRULES-479
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Decision tables
Reporter: Michael Neale
Assigned To: Mark Proctor
Priority: Minor
This could be done quite easily by a contributor.
Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates 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
Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation
--------------------------------------------------------------------------------------------
Key: JGRP-297
URL: http://jira.jboss.com/jira/browse/JGRP-297
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik).
This can be run every N seconds, and is useful in both stress testing and possibly also during operation.
--
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
Use a file based transaction logger instead of logging in the database
----------------------------------------------------------------------
Key: JBMESSAGING-543
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-543
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
Currently we are logging prepared state transactions in the database.
Instead, we should utilise a tried and tested transaction logger for performance reasons.
We should evaluate both JBoss TS objectstore, and HOWL to take this role
--
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
Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException
---------------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-661
URL: http://jira.jboss.com/jira/browse/EJBTHREE-661
Project: EJB 3.0
Issue Type: Bug
Components: Security
Affects Versions: EJB 3.0 RC7 - FD
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: EJB 3.0 RC9 - FD
When setting up security in a EJB3 bean, it is mandatory adding the
org.jboss.ejb3.security.SecurityDomain tag. Failure to do so results
on a NullPointerException.
AS should log a more meaningful message rather than a
NullPointerException.
--
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
Streamable based serialization for HAPartitionImpl
--------------------------------------------------
Key: JBAS-3540
URL: http://jira.jboss.com/jira/browse/JBAS-3540
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
JGroups has some utility functions that optimize serialization of its classes that implement its Streamable interface. But, HAPartitionImpl has to bypass those opimizations due to the need to use MarshalledValueInputStream. We should look into adding similar optimizations into a Marshaller for HAPartitionImpl.
--
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 include all the transports within the tests.versioning ant target
-------------------------------------------------------------------------
Key: JBREM-557
URL: http://jira.jboss.com/jira/browse/JBREM-557
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
Due to a problem with the test setup, some of the versioning tests (for rmi and socket) do not pass when running the versioning tests. Know these actually work when run manually, so need to investigate why automated tests are failing.
--
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
Inject DRM and DS into ClusterPartition
---------------------------------------
Key: JBAS-3532
URL: http://jira.jboss.com/jira/browse/JBAS-3532
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta
DRM and DS are now independent services. Inject them into ClusterPartiton so they can be exposed via HAPartition.
ClusterPartition in create or start must confirm that the injected DRM and DS are using the same JChannelFactory and stack that it is.
--
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