August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-168) Message tests derive from MessageTestBase

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-168?page=all ] Ovidiu Feodorov updated JBMESSAGING-168: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Message tests derive from MessageTestBase > ----------------------------------------- > > Key: JBMESSAGING-168 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-168 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The jms message tests, e.g. JMSExpirationHeaderTest inherit from MessageTest. > Therefore all the tests in MessageTest are being re-run for each of the subtypes. > The hierarchchy of tests is overly complex and confusing. > We have messagetest, messagetestbase, jmstest, messagingtestcase...... (!) > The structure should be flattened and simplified to aid comprehension. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-307) Down cache optimisation

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-307?page=all ] Ovidiu Feodorov updated JBMESSAGING-307: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Down cache optimisation > ----------------------- > > Key: JBMESSAGING-307 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-307 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db > and just transfer from the downcache to the in memory list when loading -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Ovidiu Feodorov updated JBMESSAGING-375: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-332) Consider how best to factor paging logic out of channel state

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-332?page=all ] Ovidiu Feodorov updated JBMESSAGING-332: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Consider how best to factor paging logic out of channel state > ------------------------------------------------------------- > > Key: JBMESSAGING-332 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-332 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Need to consider whether to make paging strategy pluggable and factor current implementation out into a concrete implementation. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-377) Competing consumer on subscriptions

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ] Ovidiu Feodorov updated JBMESSAGING-377: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Competing consumer on subscriptions > ----------------------------------- > > Key: JBMESSAGING-377 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-268) Convert destinations to ints in message instance

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-268?page=all ] Ovidiu Feodorov updated JBMESSAGING-268: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Convert destinations to ints in message instance > ------------------------------------------------ > > Key: JBMESSAGING-268 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-268 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers. > When sending a message the destination (and possibly the replyto) need to be serialized with the message. > If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize. > This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-374) AOP stack should be specifiable per connection factory

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-374?page=all ] Ovidiu Feodorov updated JBMESSAGING-374: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > AOP stack should be specifiable per connection factory > ------------------------------------------------------ > > Key: JBMESSAGING-374 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-374 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > It should be possible to specifty the entire client and server aop stack configuration per connection factory -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-271) Modifying a server/**/*Advised.java or a client/**/**Delegate.java file breaks the incremental build, because of AOPC failure

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-271?page=all ] Ovidiu Feodorov updated JBMESSAGING-271: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Modifying a server/**/*Advised.java or a client/**/**Delegate.java file breaks the incremental build, because of AOPC failure > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-271 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-271 > Project: JBoss Messaging > Issue Type: Bug > Components: Build System > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > > Modifying a class that is going to be AOPCed (server/**/*Advised.java or a client/**/**Delegate.java) breaks the incremental build, as the AOPC fails to process it: > compile-classes: > [javac] Compiling 1 source file to C:\work\src\cvs\jboss-head\jms\output\classes > [aopc] java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned. > [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093) > [aopc] at javassist.CtClassType.defrost(CtClassType.java:272) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96) > [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78) > [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59) > [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137) > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654) > [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835) > [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747) > [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90) > [aopc] [error] failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate.. Do verbose mode if you want full stack trace. > [aopc] java.lang.RuntimeException: failed to transform: org.jboss.jms.client.delegate.ClientBrowserDelegate > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:728) > [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:835) > [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:747) > [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:345) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:234) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:90) > [aopc] Caused by: java.lang.RuntimeException: defrost(): org.jboss.jms.client.delegate.ClientBrowserDelegate$close_N4742752445160157748 was pruned. > [aopc] at javassist.CtClassType.checkPruned(CtClassType.java:1093) > [aopc] at javassist.CtClassType.defrost(CtClassType.java:272) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.defrostClassIfExists(OptimizedInvocations.java:66) > [aopc] at org.jboss.aop.instrument.OptimizedInvocations.makeInvocationClass(OptimizedInvocations.java:96) > [aopc] at org.jboss.aop.instrument.OptimizedMethodInvocations.createOptimizedInvocationClass(OptimizedMethodInvocations.java:78) > [aopc] at org.jboss.aop.instrument.OptimizedMethodExecutionTransformer.transformMethod(OptimizedMethodExecutionTransformer.java:59) > [aopc] at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:137) > [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:654) > [aopc] ... 5 more > [aopc] Exception in thread "main" > BUILD FAILED > C:\work\src\cvs\jboss-head\jms\build.xml:339: Java returned: 1 > The workaround in this case is to do a ant clean and then rebuild everything from scratch, which is very inefficient. > Must be fixed properly -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-342) Functional tests bundled with the release should be functional

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-342?page=all ] Ovidiu Feodorov updated JBMESSAGING-342: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > Functional tests bundled with the release should be functional > -------------------------------------------------------------- > > Key: JBMESSAGING-342 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-342 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The functional tests whose source code comes with the release should be compilable and runnable, so they can validate the release at unpacking. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-170) JCA 1.5 Message Inflow

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-170?page=all ] Ovidiu Feodorov updated JBMESSAGING-170: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.6) > JCA 1.5 Message Inflow > ---------------------- > > Key: JBMESSAGING-170 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-170 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > See related task. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006