November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-942) Performance comparisons between MINA and JBR

by Tim Fox (JIRA)

Performance comparisons between MINA and JBR -------------------------------------------- Key: JBMESSAGING-942 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: Miscellaneous Perform performance coparisons between Apache MINA and JBoss Remoting. -- 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

15 years, 4 months

2
8
0 / 0

[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

15 years, 4 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

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1427) Optimiza Journal for Lazy-destinations

by Clebert Suconic (JIRA)

Optimiza Journal for Lazy-destinations -------------------------------------- Key: JBMESSAGING-1427 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1427 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 2.0.0 Alpha Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 2.0.0 Beta Attachments: optimize-lazy-destinations.patch If a destination is lazy, not consuming messages for a long time, the journal will grow until those messages are consumed. This would be a problem with DLQs or messages taking days before they are consumed. Since we inform the TransactionSummary on commits, we could change the journal to support multiple current-files based on configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
23
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

15 years, 5 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

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1568) after EJB3 is not found, forget that wrong session and create new one

by Radoslav Husar (JIRA)

after EJB3 is not found, forget that wrong session and create new one --------------------------------------------------------------------- Key: EJBTHREE-1568 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1568 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1563) check why test sometimes hangs up

by Radoslav Husar (JIRA)

check why test sometimes hangs up --------------------------------- Key: EJBTHREE-1563 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1563 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
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

15 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (SECURITY-256) Optimization: Precreate authorization modules in the JBossAuthorizationManager

by Anil Saldhana (JIRA)

Optimization: Precreate authorization modules in the JBossAuthorizationManager ------------------------------------------------------------------------------ Key: SECURITY-256 URL: http://jira.jboss.com/jira/browse/SECURITY-256 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.CR6 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR8 The JBossAuthorizationManager should have initialization steps to precreate the authorization modules if the configuration is available for the security domain. There needs to be an external mechanism to clear the authorization modules. -- 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

15 years, 5 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008