November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-306) Supports recovery flag

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ] Tim Fox closed JBMESSAGING-306. ------------------------------- Resolution: Out of Date > Supports recovery flag > ---------------------- > > Key: JBMESSAGING-306 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-306 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Should have flag "supports XA recovery" on persistencemanager. > If = false then only tx id, not all xid fields are persisted on prepare. This should improve performance when xa recovery is not required. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-158) Tidy up tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-158?page=all ] Tim Fox closed JBMESSAGING-158. ------------------------------- Resolution: Out of Date > Tidy up tests > ------------- > > Key: JBMESSAGING-158 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-158 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Affects Versions: 1.0.0 alpha PR3 > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta > > Original Estimate: 2 days, 4 hours > Remaining Estimate: 2 days, 4 hours > > Tidy up tests: > - Some test classes (and notably MessageConsumerTest) do a lot of Connection/Session/Consumer/Producer creation in setUp(). The original idea was to separate as much boilerplate code as possible, but this leads to hard to understand tests and may lead to unexpected behavior, since the test my get "hidden" intialization it doesn't want. Refactor them and re-write each test to be as independent as possible. > - For tests that send messages in a loop, use a centrally-configured loop counter, which can be easily globally modified. Stress test are more likely to exhibit edge cases and race conditions as the number of message increases, and it should be easy to control that number globally. > Example > public class Global > { > public static final int GENERAL_COUNTER = 100; > .... > } > public class MyTest extends MessagingTestCase > { > // override if it doesn't makes sense locally > protected int NUM_MESSAGES = Global.GENERAL_COUNTER; > ... > } > > - Some tests are not in the right file. > When refactor tests, take extra care not to break their semantics, though. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-225) Explore integrating Adrian's Microcontainer with the Messaging testing environment

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-225?page=all ] Tim Fox closed JBMESSAGING-225. ------------------------------- Resolution: Duplicate Issue > Explore integrating Adrian's Microcontainer with the Messaging testing environment > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-225 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-225 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-186) Check that all TODOs and FIXMEs correspond to known JIRA tasks

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-186?page=all ] Tim Fox closed JBMESSAGING-186. ------------------------------- Resolution: Rejected We don't need a JIRA task to tell us this > Check that all TODOs and FIXMEs correspond to known JIRA tasks > -------------------------------------------------------------- > > Key: JBMESSAGING-186 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-186 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta > > > .. and if not, create appropriate JIRA tasks. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-309) Rename createXXXDelegate methods

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-309?page=all ] Tim Fox updated JBMESSAGING-309: -------------------------------- Priority: Trivial (was: Major) > Rename createXXXDelegate methods > -------------------------------- > > Key: JBMESSAGING-309 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-309 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Trivial > Fix For: 2.0.0 Beta > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Rename createXXXDelegate methods in ServerXXEndpoint classes to createXXXEndpoint, since they create endpoints, not delegates. -- 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

18 years, 2 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-271?page=all ] Tim Fox closed JBMESSAGING-271. ------------------------------- Resolution: Out of Date > 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: Unscheduled > > > 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-835) Simple test suite configuration

by Tim Fox (JIRA)

Simple test suite configuration ------------------------------- Key: JBMESSAGING-835 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-835 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA The test suite configuration needs to be simplified. Currently, the same settings can be specified in enrvironment variables, properties file, build.xml, system properties, and in container.xml, with a complex precedence hierarchy determining which setting overrides another setting. Also some settings are specified redundantly - e.g. test database is inferred from the jdbc connection url but is already specified in the container.xml. We should have one place and one place only where configuration settings are specified. -- 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

18 years, 2 months

2
6
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-123) Unify the "ServiceContainer" testing framework with similar efforts in other projects

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-123?page=all ] Tim Fox closed JBMESSAGING-123. ------------------------------- Resolution: Out of Date > Unify the "ServiceContainer" testing framework with similar efforts in other projects > ------------------------------------------------------------------------------------- > > Key: JBMESSAGING-123 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-123 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > JBoss Messaging is currently using for tests a "ServiceContainer", which is able to instantiate a scaled-down version of the microkernel and essential services (transactions, inmemory database, JNDI, etc), while using for these services actual implementations available from other JBoss projects/thirdparty archives. > * Try to integrate this effort with what is being done in other projects. > * Possible use Bill's work: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63480 > * Other reference http://jira.jboss.com/jira/browse/JBAS-1768 > * Move whatever infrastructure is required by this from src/org/jboss/messaging/tools to tests/src ..... -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-222) Run "findbugs" on the code base

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-222?page=all ] Tim Fox closed JBMESSAGING-222. ------------------------------- Resolution: Rejected We don't need a JIRA task to tell us this > Run "findbugs" on the code base > ------------------------------- > > Key: JBMESSAGING-222 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-222 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Attachments: build.xml, findbugs-0.9.5.zip, findbugs.patch, findbugs.patch, report-fb.xml > > > Run "findbugs" or similar regularily on the code base. Integrate it in the continous build process. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-208) Example of custom client-side/server-side interceptors

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-208?page=all ] Tim Fox closed JBMESSAGING-208. ------------------------------- Resolution: Out of Date > Example of custom client-side/server-side interceptors > ------------------------------------------------------ > > Key: JBMESSAGING-208 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-208 > Project: JBoss Messaging > Issue Type: Task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Provide an example of writing and configuring a custom client-side and server-side AOP interceptor. > Add the example to docs/examples so it can be used as an integration test. -- 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

18 years, 2 months

1
0
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 November 2007