March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5272) EAR containing a MDB(listening to a topic) fails to deploy because of the order of deployment

by jaikiran pai (JIRA)

EAR containing a MDB(listening to a topic) fails to deploy because of the order of deployment --------------------------------------------------------------------------------------------- Key: JBAS-5272 URL: http://jira.jboss.com/jira/browse/JBAS-5272 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta4 Environment: JBoss-5.0 Beta 4, Sun Java 1.5, Windows 2003 Server Reporter: jaikiran pai A simple EAR containing an MDB which listens on a topic fails to deploy. The MDB is as follows: package org.myapp.ejb.impl; import javax.ejb.ActivationConfigProperty; import javax.ejb.MessageDriven; import javax.jms.Message; import javax.jms.MessageListener; import org.apache.log4j.Logger; @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic"), @ActivationConfigProperty(propertyName="destination", propertyValue="topic/testTopic") }) public class MyMDB implements MessageListener { private static Logger logger = Logger.getLogger(MyMDB.class); /** * Default constructor * */ public MyMDB() { } /** * */ public void onMessage(Message arg0) { System.out.println("onMessage of MyMDB called"); logger.info("onMessage of MyMDB called"); } } The sample EAR that i used for testing was named EJB3Persistence.ear and was placed in the deploy folder of JBoss. The topic was configured in destinations-service.xml which is inside deploy\messaging folder. Started JBoss. While deploying the application, JBoss threw this exception: 2008-03-04 11:29:51,416 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.myapp.ejb.impl.MyMDB ejbName: MyMDB 2008-03-04 11:29:51,416 DEBUG [org.jboss.ejb3.mdb.MessagingContainer] Initializing 2008-03-04 11:29:51,463 DEBUG [org.jboss.ejb.txtimer.EJBTimerServiceImpl] createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@1099c38 2008-03-04 11:29:51,510 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=EJB3Persistence.ear,jar=myapp_ejb3.jar,name=MyMDB,service=EJB3 state=Create org.jboss.deployment.DeploymentException: Unable to create activation spec ra=jboss.jca:service=RARDeployment,name='jms-ra.rar' messaging-type=javax.jms.MessageListener properties={destination=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@aac6440e{destination}, destinationType=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@96f19068{destinationType}} at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:299) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:192) at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:187) at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:151) at org.jboss.ejb3.mdb.MDB.start(MDB.java:123) 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.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.system.ServiceController.doChange(ServiceController.java:659) at org.jboss.system.ServiceController.start(ServiceController.java:431) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:150) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:108) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408) at org.jboss.Main.boot(Main.java:208) at org.jboss.Main$1.run(Main.java:534) at java.lang.Thread.run(Thread.java:595) Caused by: javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name='jms-ra.rar' is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662) at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:294) ... 54 more This appears to be because the topic defined in the deploy\messaging folder is created at a later stage during deployment: 2008-03-04 11:30:08,479 DEBUG [org.jboss.jms.server.destination.TopicService] Starting jboss.messaging.destination:service=Topic,name=testTopic 2008-03-04 11:30:08,494 DEBUG [org.jboss.jms.server.DestinationJNDIMapper] topic testTopic registered 2008-03-04 11:30:08,494 DEBUG [org.jboss.jms.server.DestinationJNDIMapper] topic bound in JNDI as /topic/testTopic As a workaround, i renamed the EAR file to ZEJB3Persistence.ear (note that the filename now starts with Z), so that this file is picked up for deployment *after* deploying the topic in the messaging folder. I then restarted JBoss with came up fine without any errors and deployed the EAR and MDB. Please see the forum reference for more details. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5132) Jboss 4.2.2 JSF RI did not work for clicking links w/ target=_blank

by Dave Chen (JIRA)

Jboss 4.2.2 JSF RI did not work for clicking links w/ target=_blank ------------------------------------------------------------------- Key: JBAS-5132 URL: http://jira.jboss.com/jira/browse/JBAS-5132 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-4.2.2.GA Environment: Linux Federa Core 6, MySQL Reporter: Dave Chen Assigned To: Stan Silvert Priority: Critical Everything works fine for myfaces on Jboss 4.0.5GA. After I moved to JBoss 4.2.2 with faces RI. I got issues when clicking a command link with target=_blank. First time clicking the link is ok, but clicking the link again did not work, did not go to the Invoke Application phase to execute action. http://www.nabble.com/Jboss-4.2.2-RI-did-not-work-for-clicking-links-w--t... -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=comments#action_12401222 ] Adrian Brock commented on JBAS-3352: ------------------------------------ Questions go in the forums (where you will find it already answered). > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=all ] Adrian Brock updated JBAS-3352: ------------------------------- Comment: was deleted > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3352) Provide better validation of the redelivery parameters on JBossMQ queues and topics

by Jaroslaw Kijanowski (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3352?page=comments#action_12401220 ] Jaroslaw Kijanowski commented on JBAS-3352: ------------------------------------------- The redelivery limit is set to -1 by default. Why is this value not allowed to be set via the jmx-console? > Provide better validation of the redelivery parameters on JBossMQ queues and topics > ----------------------------------------------------------------------------------- > > Key: JBAS-3352 > URL: http://jira.jboss.com/jira/browse/JBAS-3352 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.2.0.CR1 > > > The JBossMQ Queues and Topics have parameters for redelivery delay and limit. > Both accept any value. There should be validation that errors attempts to use negative values. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREFLECT-19) Move the DependencyBuilder to the kernel project

by Adrian Brock (JIRA)

Move the DependencyBuilder to the kernel project ------------------------------------------------ Key: JBREFLECT-19 URL: http://jira.jboss.com/jira/browse/JBREFLECT-19 Project: JBoss Reflection Issue Type: Task Components: Config Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossReflection.2.0.0.CR1 The DependencyBuilder should really be in the kernel project. It will be moved to there and the AOP callback updated according. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-248) Include the DependencyBuilder in the kernel project

by Adrian Brock (JIRA)

Include the DependencyBuilder in the kernel project --------------------------------------------------- Key: JBMICROCONT-248 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-248 Project: JBoss MicroContainer Issue Type: Task Components: Dependency Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 Move the DependencyBuilder from the reflection project and update aop-mc-int accordingly. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-70) Make JBossCache an XAResource

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-70?page=all ] Manik Surtani updated JBCACHE-70: --------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131825#4131825 Complexity: High > Make JBossCache an XAResource > ----------------------------- > > Key: JBCACHE-70 > URL: http://jira.jboss.com/jira/browse/JBCACHE-70 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.2.0 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1295) implement JBossCache as an XA resource, rather than standard JTA Synchronizations

by Mircea Markus (JIRA)

implement JBossCache as an XA resource, rather than standard JTA Synchronizations --------------------------------------------------------------------------------- Key: JBCACHE-1295 URL: http://jira.jboss.com/jira/browse/JBCACHE-1295 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani this is a quirk in that we actually finish committing state to the cache in afterCompletion() which is actually incorrect - but since this involves replication informing remote caches to commit their state as well, we can only be sure of this success in afterCompletion(). -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1229) Allow names for queues and topics to contain slashes

by Martin Landua (JIRA)

Allow names for queues and topics to contain slashes ---------------------------------------------------- Key: JBMESSAGING-1229 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1229 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Destination Manager Affects Versions: 1.4.0.SP3 Environment: JBoss Messaging 1.4.0.SP3 on JBoss AS 4.2.2.GA Reporter: Martin Landua Assigned To: Tim Fox Priority: Minor When defining a queue or topic, the JNDI name is automatically derived from the queue/topic's name. It is often convenient for JNDI names to contain slashes to form a queue/topic hierarchy. However, the JMX-name of a queue/topic must not contain slashes because in this case the automatic registration in JNDI fails due to missing parent contexts. Please consider the enclosed patch that would fix this problem. The patch renders everything backward compatible. Index: D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java =================================================================== --- D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java (revision 3658) +++ D:/JBossIDE/workspace_jb42/jboss-messaging-1.4.0.SP3a/src/main/org/jboss/jms/server/DestinationJNDIMapper.java (working copy) @@ -99,20 +99,18 @@ jndiNameInContext = destination.getName(); jndiName = parentContext + "/" + jndiNameInContext; } - else - { - // TODO more solid parsing + test cases - int sepIndex = jndiName.lastIndexOf('/'); - if (sepIndex == -1) - { - parentContext = ""; - } - else - { - parentContext = jndiName.substring(0, sepIndex); - } - jndiNameInContext = jndiName.substring(sepIndex + 1); - } + + // TODO more solid parsing + test cases + int sepIndex = jndiName.lastIndexOf('/'); + if (sepIndex == -1) + { + parentContext = ""; + } + else + { + parentContext = jndiName.substring(0, sepIndex); + } + jndiNameInContext = jndiName.substring(sepIndex + 1); destination.setJndiName(jndiName); -- 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, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008