January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1090) Add appropriate Exception handling when hitting MaxSize

by Jay Howell (JIRA)

Add appropriate Exception handling when hitting MaxSize ------------------------------------------------------- Key: JBMESSAGING-1090 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.GA Reporter: Jay Howell Assigned To: Tim Fox When using MaxSize for a queue and topic the following behaviors exist Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null. This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint. Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint. What this means is that anyone who wants to put hooks in to gather the messages dropped can't. Either because the exception is too generic or because one is not thrown at all. I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions. We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException. Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException). Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize. -- 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

16 years, 10 months

4
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1149) Singleton consumer on queue/topic

by Tim Fox (JIRA)

Singleton consumer on queue/topic --------------------------------- Key: JBMESSAGING-1149 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1149 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP2 A last minute requirement came up from the AS team (Carlo and Bill DeCoste). JBoss MQ uses HA singleton to provide a singleton consumer on a queue/topic. If that node fails, the consumer should failover onto another single node. Currently this isn't supported in JBM. -- 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

16 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-753) Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh

by Galder Zamarreno (JIRA)

Similar to JBC/JGroups, add an ant-dist folder and build.bat/build.sh --------------------------------------------------------------------- Key: JBMESSAGING-753 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-753 Project: JBoss Messaging Issue Type: Feature Request Components: Build System Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor Fix For: 1.2.1 Add to source and make messaging add it to the binary distribution under util directory. That should speed up patching AS for customers and would guarantee that they use the Ant version that we want them to use. This is currently implemented in JBC and JGroups and I find it very useful. -- 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

16 years, 10 months

6
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1194) Investigate quorum for mitigating split brain

by Tim Fox (JIRA)

Investigate quorum for mitigating split brain --------------------------------------------- Key: JBMESSAGING-1194 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1194 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox 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

16 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBBUILD-419) Enable module unit tests for app server builds

by Paul Gier (JIRA)

Enable module unit tests for app server builds ---------------------------------------------- Key: JBBUILD-419 URL: http://jira.jboss.com/jira/browse/JBBUILD-419 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Several app server modules contain unit tests. Test scope dependencies should be added to the poms for these tests, and the tests should be enabled with the surefire plugin. -- 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

16 years, 10 months

1
8
0 / 0

[JBoss JIRA] Created: (BPEL-244) Support for BPEL process instance monitoring in jBPM admin console

by Meghana Joglekar (JIRA)

Support for BPEL process instance monitoring in jBPM admin console ------------------------------------------------------------------ Key: BPEL-244 URL: http://jira.jboss.com/jira/browse/BPEL-244 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Reporter: Meghana Joglekar Assigned To: Alejandro Guizar One can currently run BPEL processes on jBPM engine and check the log files to see the runtime report. But this process is not efficient in monitoring how the process is doing, what processes are running, what went wrong when a fault occurred etc. It will be nice to have administration console to see this information. The administration console can then list the process instances that are running, show visual graph of the instance and for each node in the graph more information about it. ActiveBPEL and OracleBPEL both provide such consoles and they are great tools for administrators. It will be nice if it also provides 'delete' functionality for stalled processes or old processes. The list could go on but in its basic form, processes listing, process instance listing and then more information about them [instances] will be useful. -- 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

16 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-447) Create pom for testsuite

by Paul Gier (JIRA)

Create pom for testsuite ------------------------ Key: JBBUILD-447 URL: http://jira.jboss.com/jira/browse/JBBUILD-447 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server The testsuite module of the app server build needs a maven pom. -- 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

16 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-759) CLONE -Unable to add package after it was added and removed

by Brugger Antony (JIRA)

CLONE -Unable to add package after it was added and removed ----------------------------------------------------------- Key: JBRULES-759 URL: http://jira.jboss.com/jira/browse/JBRULES-759 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Environment: Windows2000 Advanced Server JBRules3.0.4 Reporter: Brugger Antony Assigned To: Edson Tirelli Fix For: 3.0.5 Unable remove a rule package when it was added after it has been added and removed. I have seen the issue [#JBRULES-358]. My test go a little far than [#JBRULES-358]. I remove the package again when it was added for the seconn time, then an exception was thrown. My test case is: public void testRuleBaseRemove() throws Exception { RuleBase ruleBase = RuleBaseFactory.newRuleBase(); File file = new File("test.drl"); //add and remove PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); Package pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); //add and remove again builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); } the exception is throw: java.lang.NullPointerException at org.drools.reteoo.HashedObjectSinkList.remove(HashedObjectSinkList.java:102) at org.drools.reteoo.ObjectTypeNode.remove(ObjectTypeNode.java:245) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.LeftInputAdapterNode.remove(LeftInputAdapterNode.java:285) at org.drools.reteoo.TerminalNode.remove(TerminalNode.java:297) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:589) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:244) at org.drools.common.AbstractRuleBase.removePackage(AbstractRuleBase.java:338) at com.zte.ums.uep.pal.fm.osf.rules.core.RuleBaseTest.testRuleBaseRemove(RuleBaseTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1373) Rename feasibleScoreFinish

by Geoffrey De Smet (JIRA)

Rename feasibleScoreFinish -------------------------- Key: JBRULES-1373 URL: http://jira.jboss.com/jira/browse/JBRULES-1373 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional scoreReachedFinish might be more appropriate and less confusing with "feasible solutions" because a feasible solution would be able to have an unfeasible score?!? -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-912) ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods

by Andrew Redhead (JIRA)

ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods --------------------------------------------------------------------------- Key: EJBTHREE-912 URL: http://jira.jboss.com/jira/browse/EJBTHREE-912 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: Identified on jboss-4.0.5.GA from jems installer 1.2.GA, still present in head from svn co http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/ as of 13th March 2007. Tests run agains JDK 1.5 on Win XP (sp2) Reporter: Andrew Redhead Using an ejb-jar.xml file to inject an EntityManger into an EJB3 stateless session bean succeeds for bean interface methods but fails for @PostConstruct methods. In both cases the reference to the EntityManager is non-null, however in the @PostConstruct method, accessing the EnityManger underlying delegate fails. The test cases provide both an "API" interface case (which passes) and an @PostConstruct case, which currently fails. -- 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

16 years, 11 months

3
5
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 January 2008