December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-133) Hosting trailblazer on docs site

by Mark Little (JIRA)

Hosting trailblazer on docs site -------------------------------- Key: JBESB-133 URL: http://jira.jboss.com/jira/browse/JBESB-133 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Testing Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Daniel Brum Priority: Minor Fix For: 4.0 We should look at hosting the TB here along with some good writeup on it, diagrams explaining each step of the way, etc... http://www.jboss.com/docs/demos -- 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

17 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-274) Make sure code is more defensive against errors

by Mark Little (JIRA)

Make sure code is more defensive against errors ----------------------------------------------- Key: JBESB-274 URL: http://jira.jboss.com/jira/browse/JBESB-274 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- 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

17 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-277) Add more QA.

by Mark Little (JIRA)

Add more QA. ------------ Key: JBESB-277 URL: http://jira.jboss.com/jira/browse/JBESB-277 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBADMCON-149) Support JBoss Messaging

by chi lin (JIRA)

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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-628) Investigate message priority in presence of prefetching

by Tim Fox (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

17 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-324) Thrown Annotation

by Flavia Rainone (JIRA)

Thrown Annotation ----------------- Key: JBAOP-324 URL: http://jira.jboss.com/jira/browse/JBAOP-324 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Need to decide another name for this annotation. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-168) Recovery extensions mentioned more than once in property file.

by Mark Little (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

17 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-616) Race in creating new counters

by Tim Fox (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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-700) Delivery count is not updated for transactional sessions on close

by Tim Fox (JIRA)

Delivery count is not updated for transactional sessions on close ----------------------------------------------------------------- Key: JBMESSAGING-700 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-700 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2 When closing a transactional session which still has uncomitted deliveries in it, then these end up being cancelled when the session closes on the server, therefore losing any delivery count information. Instead, we should explicitly cancel any messages in the transactional state as part of the close protocol, as we currently do with non transactional remaining deliveries. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-817) ContextInstance.setVariable() behaves very inperformant

by Mirco Graf (JIRA)

ContextInstance.setVariable() behaves very inperformant ------------------------------------------------------- Key: JBPM-817 URL: http://jira.jboss.com/jira/browse/JBPM-817 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: Mirco Graf Assigned To: Tom Baeyens When setting a process variable, jBPM tries to map the variable to a jBPM-internal data-type (StringVariable, LongVariable etc.). When comparing the given variable-value to existing jBPM-types, the Class org.jbpm.context.exe.JbpmType always performs an XML-parsing of the ressource "resource.varmapping" to get all available types without any caching. The types usually should be cached as the property "jbpm.types", but it seems like jbpm never uses the cache and always performs an XML-parsing. In the following method of Class org.jbpm.context.exe.JbpmType the else-case is *always* executed, seems like the property "jbpm.types" is not set correctly. public static List getJbpmTypes() { List jbpmTypes = null; if (JbpmConfiguration.Configs.hasObject("jbpm.types")) { jbpmTypes = (List) JbpmConfiguration.Configs.getObject("jbpm.types"); } else { jbpmTypes = getDefaultJbpmTypes(); } return jbpmTypes; } While profiling my app i realized that getJbpmTypes()-Operations took about 30% of the whole application-runtime, about 15ms in average. -- 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

17 years, 9 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006