March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-380) Use JBoss retro

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-380?page=all ] Ovidiu Feodorov updated JBMESSAGING-380: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Use JBoss retro > --------------- > > Key: JBMESSAGING-380 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-380 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > We should consider using JBossRetro in JBossMessaging. This will allow us to use JDK1.5 specific features in the code base, but will still run on JDK1.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

19 years, 1 month

1
0
0 / 0

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

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-225?page=all ] Ovidiu Feodorov updated JBMESSAGING-225: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > 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: Unscheduled > > -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-265) Soak tests

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-265?page=all ] Ovidiu Feodorov updated JBMESSAGING-265: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Soak tests > ---------- > > Key: JBMESSAGING-265 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-265 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > > A test that runs long enough and sends a significant number of messages into the server; used to detect memory leaks and failure under load -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-152) Revisit exception handling

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-152?page=all ] Ovidiu Feodorov updated JBMESSAGING-152: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Revisit exception handling > -------------------------- > > Key: JBMESSAGING-152 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-152 > Project: JBoss Messaging > Issue Type: Task > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > We should audit the exception handling. > In some areas it is quite sloppy including anti-patterns such as: > 1. Logging errors when they're not being handled > 2. Rethrowing with less information. E.g. losing the message or original exception. > 3. Too much usage of "throws Throwable" or "throws Exception" where probably unnecessary. > 4. Swallowing exceptions. > We need to go through the whole of the code, auditing and changing as necessary. -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-322) Deploying an MDB for a destination that doesn't exist fails.

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-322?page=all ] Ovidiu Feodorov updated JBMESSAGING-322: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Deploying an MDB for a destination that doesn't exist fails. > ------------------------------------------------------------ > > Key: JBMESSAGING-322 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-322 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the destination an MDB is configured with doesn't exist, the MDB Container's JMSContainerInvoker tries to create the destination and fails because uses a non-portable interface that only works with JBossMQ. > Line 1201, org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination() > // invoke the server to create the destination > server.invoke(new ObjectName("jboss.mq:service=DestinationManager"), ..... > -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-352) @Consumer example

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-352?page=all ] Ovidiu Feodorov updated JBMESSAGING-352: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > @Consumer example > ----------------- > > Key: JBMESSAGING-352 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-352 > Project: JBoss Messaging > Issue Type: Sub-task > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add a Consumer example, as described in http://docs.jboss.org/ejb3/app-server/tutorial/consumer/consumer.html -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-85) Merge JBossMQ new feature requests into Messaging's list

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-85?page=all ] Ovidiu Feodorov updated JBMESSAGING-85: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Merge JBossMQ new feature requests into Messaging's list > -------------------------------------------------------- > > Key: JBMESSAGING-85 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-85 > Project: JBoss Messaging > Issue Type: Task > Components: JMS Facade > Reporter: Ovidiu Feodorov > Fix For: Unscheduled > > -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-354) Start a database with use case info

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-354?page=all ] Ovidiu Feodorov updated JBMESSAGING-354: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Start a database with use case info > ----------------------------------- > > Key: JBMESSAGING-354 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-354 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > -- 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

19 years, 1 month

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: Unscheduled (was: 1.2.1) > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-91) Administrative destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-91?page=all ] Ovidiu Feodorov updated JBMESSAGING-91: --------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Administrative destinations > --------------------------- > > Key: JBMESSAGING-91 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-91 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Implement special destinations to allow administration over the jms protocol itself. e.g. You can send a request/response message to the "AdminQueue" that says create me a destination or change my password, etc. -- 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

19 years, 1 month

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 March 2007