March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1133) Set up test framework

by Tim Fox (JIRA)

Set up test framework --------------------- Key: JBMESSAGING-1133 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1133 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Andy Taylor Fix For: Performance metrics, benchmarks and scalability testing Set up DTF or JBM performance test framework as appropriate. Define a set of simple tests which test JBM both clustered and non clustered. The tests should exercise most common use cases. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5049) NoInitialContextException on deployment of EAR that contains MDB and persistence.xml

by Alan Feng (JIRA)

NoInitialContextException on deployment of EAR that contains MDB and persistence.xml ------------------------------------------------------------------------------------ Key: JBAS-5049 URL: http://jira.jboss.com/jira/browse/JBAS-5049 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3 Affects Versions: JBossAS-4.2.2.GA Environment: Windows XP SP2, JDK1.5.0_09, JBoss AS-4.2.2.GA, SEAM 2.0.0.GA Reporter: Alan Feng Assigned To: Dimitris Andreadis When deploy an EAR that contains EJB3 MDB, you may receive NoInitialContextException on the deployment of other EJB3 elements. In my particular case, I have a persistence.xml file that configures the EntityManager. The deployment of this persistence.xml throws the NoInitialContextException. Depending on the contents of the EAR, it may be other deployment unit that is throwing this exception. Tracing into the deployment code shows that the problem is with the latest code change in the org.jboss.ejb3.EJBContainer class. This class has method named getInitialContext(). In the previous release it returns a newly constructed InitialConext object. In the 4.2.2.GA, it returns the shared static InitialContext object from the InitialContextFactory class. The MDB deployer class org.jboss.ejb3.mdb.MessagingContainer.getJMSProviderAdapter() method calls this method to obtain a InitialContext object and closes this InitialContext object after using it. This results in that the shared InitialContext object been closed prematurely as it is used later on to deploy other EJB3 units, such as the persistence.xml file in my case. Suggested fix: Change the org.jboss.ejb3.mdb.MessagingContainer.getJMSProviderAdapter() method as follows: Change the line (around line # 586): Context context = getInitialContext(); to: Context context = initialContextProperties == null ? new InitialContext() : new InitialContext(initialContextProperties); The above suggested change is copied from the previous implementation of the EJBContainer.getInitialContext() method. -- 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

16 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1158) Solver ScoreCalculator should work with Number instead of double

by Geoffrey De Smet (JIRA)

Solver ScoreCalculator should work with Number instead of double ---------------------------------------------------------------- Key: JBRULES-1158 URL: http://jira.jboss.com/jira/browse/JBRULES-1158 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE The type of Number should be consistent in a single solver. Most of the current examples will benefit from using Integer's instead of double. Note that the timeGradients etc stay a double. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5225) status function must return non-zero when jbossas is not running

by Brenton Leanhardt (JIRA)

status function must return non-zero when jbossas is not running ---------------------------------------------------------------- Key: JBAS-5225 URL: http://jira.jboss.com/jira/browse/JBAS-5225 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-4.2.2.GA Environment: OS: RHEL5 U1 RPM: jbossas-4.3.0-1.ep1.8 Reporter: Brenton Leanhardt Assigned To: Dimitris Andreadis Priority: Trivial I surveyed a few traditional unix services' status function and all returned either 1 or 3 when the service was not running. While this is extremely trivial it's a great help for high level tooling that deals with heterogeneous environments (I noticed this when Puppet was not able to detect if jbossas was running or not). -- 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

16 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-497) Joda datetime API integration

by Michael Neale (JIRA)

Joda datetime API integration ----------------------------- Key: JBRULES-497 URL: http://jira.jboss.com/jira/browse/JBRULES-497 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Michael Neale Assigned To: Mark Proctor http://joda-time.sourceforge.net/userguide.html Would be VERY nice to have this working at the parser level to parser dates in a string, but also possibly in our expression language to overload "+", "-" etc for subtracting dates/fragments of dates: eg: today - "6Months" -- 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

16 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1090) Add appropriate Exception handling when hitting MaxSize

by Jay Howell (JIRA)

Add appropriate Exception handling when hitting MaxSize ------------------------------------------------------- Key: JBMESSAGING-1090 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.GA Reporter: Jay Howell Assigned To: Tim Fox When using MaxSize for a queue and topic the following behaviors exist Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null. This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint. Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint. What this means is that anyone who wants to put hooks in to gather the messages dropped can't. Either because the exception is too generic or because one is not thrown at all. I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions. We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException. Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException). Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize. -- 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

16 years, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1149) Singleton consumer on queue/topic

by Tim Fox (JIRA)

Singleton consumer on queue/topic --------------------------------- Key: JBMESSAGING-1149 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1149 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP2 A last minute requirement came up from the AS team (Carlo and Bill DeCoste). JBoss MQ uses HA singleton to provide a singleton consumer on a queue/topic. If that node fails, the consumer should failover onto another single node. Currently this isn't supported in JBM. -- 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

16 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-753) Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh

by Galder Zamarreno (JIRA)

Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh --------------------------------------------------------------------- Key: JBMESSAGING-753 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-753 Project: JBoss Messaging Issue Type: Feature Request Components: Build System Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 1.2.1 Add to source and make messaging add it to the binary distribution under util directory. That should speed up patching AS for customers and would guarantee that they use the Ant version that we want them to use. This is currently implemented in JBC and JGroups and I find it very useful. -- 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

16 years, 11 months

6
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1194) Investigate quorum for mitigating split brain

by Tim Fox (JIRA)

Investigate quorum for mitigating split brain --------------------------------------------- Key: JBMESSAGING-1194 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1194 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta -- 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

16 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBBUILD-419) Enable module unit tests for app server builds

by Paul Gier (JIRA)

Enable module unit tests for app server builds ---------------------------------------------- Key: JBBUILD-419 URL: http://jira.jboss.com/jira/browse/JBBUILD-419 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Several app server modules contain unit tests. Test scope dependencies should be added to the poms for these tests, and the tests should be enabled with the surefire plugin. -- 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

16 years, 11 months

1
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008