April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-210) ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-210?page=all ] Tim Fox updated JBMESSAGING-210: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > ServerPeer.createTopic(...)/createQueue(...) implementation suboptimal > ---------------------------------------------------------------------- > > Key: JBMESSAGING-210 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-210 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > ServerPeer.createTopic(...)/createQueue(...) are JMX managed operations that allow to programatically create a JMS destination. The implementation is suboptimal in that it parses a literal representation of an destination MBean configuration and deploys the resulted org.w3c.dom.Element. It also accesses directly ServiceCreator and UnifiedClassLoader3 interfaces. Review the 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

19 years, 3 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-222?page=all ] Tim Fox updated JBMESSAGING-222: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > 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: 2.0.0 Beta 1 > > 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-620) Remove unneeded org/jboss/mx classes from jboss-messaging-client.jar

by Ovidiu Feodorov (JIRA)

Remove unneeded org/jboss/mx classes from jboss-messaging-client.jar -------------------------------------------------------------------- Key: JBMESSAGING-620 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-620 Project: JBoss Messaging Issue Type: Task Components: Build System Affects Versions: 1.0.1.GA, 1.2.0.Alpha1 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 -- 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, 3 months

3
6
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-152?page=all ] Tim Fox updated JBMESSAGING-152: -------------------------------- Summary: Refactor exception handling (was: Revisit exception handling) Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Refactor 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: 2.0.0 Beta 1 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-216) Prepare Messaging to replace JBossMQ in the JBoss Mail distribution

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-216?page=all ] Tim Fox closed JBMESSAGING-216. ------------------------------- Resolution: Won't Fix > Prepare Messaging to replace JBossMQ in the JBoss Mail distribution > ------------------------------------------------------------------- > > Key: JBMESSAGING-216 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-216 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > > Andy's input: > does jboss messaging: > 1. recover from outages with incomplete blobs being written? > 2. avoid making 3 copies of a message in memory? > 3. install cleanly on JBoss 4.0.3SP1/JDK5? > 4. work with Postgresql, MySQL, Hypersonic? > 5. perform better/on par with JBossMQ when used locally (no remote invocation) > 6. Have a reasonably simple method of swapping out its persistence layer ? > #1 is a particularly bad problem (in my view it should be detected and moved to the DMQ with a the blob truncated and a reference to the orgininal record [which should be excluded from mainstream processing by a flag]) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ] Tim Fox updated JBMESSAGING-287: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > RemotingTest.testConnectionListener() invalid > --------------------------------------------- > > Key: JBMESSAGING-287 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid. > After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-558) Possible performance degradation relative to JBossMQ when using contested queues and selectors

by Ovidiu Feodorov (JIRA)

Possible performance degradation relative to JBossMQ when using contested queues and selectors ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-558 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-558 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.0.1.CR5, 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Problem described on the forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91326 -- 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, 3 months

4
8
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Tim Fox updated JBMESSAGING-412: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Priority: Minor > Fix For: 1.2.1.CR1 > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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, 3 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 Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-271?page=all ] Tim Fox updated JBMESSAGING-271: -------------------------------- Fix Version/s: Miscellaneous (was: Unscheduled) > 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: Miscellaneous > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-218) Persistent services are very noisy in the logs when the table(s) they are trying to create already exists

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-218?page=all ] Tim Fox closed JBMESSAGING-218. ------------------------------- Resolution: Won't Fix set createTablesOnStartup to false if you don't want to attempt to create tables every time. Note the excpetions are logged at DEBUG - so change your log4j settings if you don't like them. > Persistent services are very noisy in the logs when the table(s) they are trying to create already exists > --------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-218 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-218 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core Persistence > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > JDBCDurableSubscriptionStore, JDBCMessageStore, JDBCTransactionLog try to create their corresponding tables during their inialization procedure and litter the logs with SQLException stack traces if the corresponding tables exist: > java.sql.SQLException: Table already exists: TRANSACTION in statement [CREATE TABLE TRANSACTION] > at org.hsqldb.jdbc.Util.sqlException(Util.java:61) > at org.hsqldb.jdbc.jdbcStatement.fetchResult(jdbcStatement.java:1580) > ..... > Use a less noisy way to insure the tables exist. Swallowing the SQLException is not a solution, since it may signal other problems with the database. -- 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, 3 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 April 2007