January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1457) Having unexistent destinations in one node may leave the cluster in an un usable situation

by Clebert Suconic (JIRA)

Having unexistent destinations in one node may leave the cluster in an un usable situation ------------------------------------------------------------------------------------------ Key: JBMESSAGING-1457 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1457 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP04 Reporter: Clebert Suconic Assignee: Howard Gao Priority: Minor Fix For: 1.4.0.SP3.CP05 MessagePostOffice::performFailover will interrupt the failover process, if a Queue is deployed in one node, but not in all nodes.. Even if the queue is not being used. I know users are required to deploy the clustered queues in all nodes But we should at least give a bigger warning here: //Cannot failover if there is no queue deployed. throw new IllegalStateException("Cannot failover " + queue.getName() + " since it does not exist on this node. " + "You must deploy your clustered destinations on ALL nodes of the cluster"); Or maybe just stopping the merge for that specific queue (with a big warning with the mistake made) and keep merging the other queues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-10) can't find resource

by Tom Baeyens (JIRA)

can't find resource ------------------- Key: GPD-10 URL: http://jira.jboss.com/jira/browse/GPD-10 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assigned To: Koen Aers i don't know why, but when trying to deploy the example process websale after modifying the form.create.xhtml, i got this exception that disabled depoyment of the process. java.lang.NullPointerException at org.jbpm.ui.util.ProcessDeployer.addClassOrResource(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.addClassesAndResources(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.createParBytes(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.access$1(Unknown Source) at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479) at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source) at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source) at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (GPD-23) deployment with problems still gives "process was deployed successfull"

by Koen Aers (JIRA)

deployment with problems still gives "process was deployed successfull" ----------------------------------------------------------------------- Key: GPD-23 URL: http://jira.jboss.com/jira/browse/GPD-23 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 Add more meaningful result notifications upon deploying process archives. -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (GPD-32) Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)

by Koen Aers (JIRA)

Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+) ------------------------------------------------------------------------------- Key: GPD-32 URL: http://jira.jboss.com/jira/browse/GPD-32 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 When trying to lookup the class implementing an action handler, the class chooser dialog fails to see classes other than those in jBPM-3.1.1. This applies to task assignments as well. To re-create, create an action handler in a different eclipse project, place that project on the classpath of the process project, and invoke the class chooser for an action in a process definition. Typing the short name of the class does not cause the list of candidates to appear. Nor does typing the fully qualified name. Typing in "ActionHandler" causes candidates from the jBPM-3.1.1 jar file to appear. Classpath is proven to be complete, because pasting the fully qualified class name into the handler class field causes the designer to display the configuration fields that are available. This is also the workaround. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1328) Alias build-test.xml target "test" to point to "one-test"

by Andrew Lee Rubinger (JIRA)

Alias build-test.xml target "test" to point to "one-test" --------------------------------------------------------- Key: EJBTHREE-1328 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1328 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 The classpaths are different, and "one-test" is supported (as stated in Wiki). Leads to confusion, alias "test" to antcall "one-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

17 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1639) IsLocalInterceptor should no longer support @Deprecated dynamicInvoke to Service Containers

by Andrew Lee Rubinger (JIRA)

IsLocalInterceptor should no longer support @Deprecated dynamicInvoke to Service Containers ------------------------------------------------------------------------------------------- Key: EJBTHREE-1639 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1639 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 Now that @Service beans are considered by ejb3-proxy, remove the following bit from IsLocalInterceptor and ensure service invocations work properly in the newer dynamicInvoke. /* * EJBTHREE-1385 * * Integration of EJB3 Proxy changed the invocation model, * so SessionSpecContainers now are supported via * dynamicInvoke(Invocation), where all other * SessionContainers use the @deprecated * dynamicInvoke(Object,Invocation) */ if (container instanceof SessionSpecContainer) { SessionSpecContainer ssc = (SessionSpecContainer) container; response = ssc.dynamicInvoke(copy); } else { response = ((SessionContainer) container).dynamicInvoke(null, copy); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1616) Create a pluggable @EJB Reference Resolver

by Andrew Lee Rubinger (JIRA)

Create a pluggable @EJB Reference Resolver ------------------------------------------ Key: EJBTHREE-1616 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1616 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 @EJB References should be able to be resolved from metadata and a given scope in a reusable fashion. Create: * SPI * Factory * Default Implementations Clients requiring resolution may then be decoupled by looking up the resolver as an MC bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1530) MBean 'start' method calls not honouring dependencies

by Hubert Holierhoek (JIRA)

MBean 'start' method calls not honouring dependencies ----------------------------------------------------- Key: EJBTHREE-1530 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1530 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: 1.0.0-Beta4 Environment: AS 5.0.0.CR2, EJB3 1.0.0-Beta4, JDK1.6.0_07 Reporter: Hubert Holierhoek MBean start methods may not be called in dependency order. See forum topic http://www.jboss.com/index.html?module=bb&op=viewtopic&t=143931 for details and a test case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-884) Provide Gossip Router Command Line Options For Backlog, Socket Read Timeout, and Socket Linger Timeout

by Jimmy Wilson (JIRA)

Provide Gossip Router Command Line Options For Backlog, Socket Read Timeout, and Socket Linger Timeout ------------------------------------------------------------------------------------------------------ Key: JGRP-884 URL: https://jira.jboss.org/jira/browse/JGRP-884 Project: JGroups Issue Type: Feature Request Affects Versions: 2.7, 2.6.7, 2.5.2, 2.4.4 Reporter: Jimmy Wilson Assignee: Jimmy Wilson Fix For: 2.4.5, 2.6.8, 2.8 Gossip Router currently provides options to set the backlog, socket read timeout, and socket linger timeout programmatically, but they are not command line options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1795) Not possible to resolve declared types on different packages

by Edson Tirelli (JIRA)

Not possible to resolve declared types on different packages ------------------------------------------------------------ Key: JBRULES-1795 URL: https://jira.jboss.org/jira/browse/JBRULES-1795 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.0.0.M2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.0.0.M3 Reported by Michal Bali: ---------------------------- Hi, Should it be possible to declare an event role to an existing type that is outside of the current rule package? Example: In the following file: http://fisheye.jboss.org/browse/JBossRules/trunk/drools-compiler/src/test... change the first line to: package org.droolsssssss; //this makes sure that StockTick is in different package now, the test org.drools.integrationtests.StreamsTest.testEventAssertion() throws following exception: org.drools.RuntimeDroolsException: unable to resolve Type Declaration class 'StockTick' at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:484) at org.drools.reteoo.ReteooRuleBase.addPackage(ReteooRuleBase.java:381) at org.drools.integrationtests.StreamsTest.loadRuleBase(StreamsTest.java:93) at org.drools.integrationtests.StreamsTest.testEventAssertion(StreamsTest.java:101) 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:597) 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:130) 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) Best Regards, Michal -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
2
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 2009