January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1781) JMS failover recovery handling failed on cluster setup when the server running with JBOss + MySQL crashes.

by saravanan muthusamy (JIRA)

JMS failover recovery handling failed on cluster setup when the server running with JBOss + MySQL crashes. ---------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1781 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1781 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.3.GA Environment: java version "1.6.0_17" JBoss version 5.1.0.GA Operating System: Solaris & Linux Reporter: saravanan muthusamy JBoss Messaging failover recovery handling failed on cluster setup when the server running with JBOss + MySQL crashes. Setup details server1: JBoss App server + MySQL server2: JBoss App server server1 was crashed for some hardware failure, server2 detects that the server1 leaves the cluster and starts the failover recovery operation, failover recovery involves clean up operation from its local map and database, how ever MySQL is down at this moment so the clean up operation failed with some re-tries. Restarting the crashed server does not help to join the existing cluster group, the reason being failover recovery has failed. 009-11-24 21:43:24,101 ERROR [main]-[org.jboss.messaging.util.ExceptionUtil] org.jboss.messaging.core.jmx.MessagingPostOfficeService@1a67848 startService java.lang.IllegalArgumentException: Cannot start post office since there is already a post office in the cluster with the same node id (215). Are you sure you have given each node a unique node id during installation? at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.start(MessagingPostOffice.java:372) at org.jboss.messaging.core.jmx.MessagingPostOfficeService.startService(MessagingPostOfficeService.java:462) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:269) 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy38.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) 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:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:619) -- 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

13 years

4
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1780) When i change the default db schemas of jbm tables the DLQ - if it contains message - run in deadlock by the next server restart, because it wants to use the default schema instead of the modified db schema

by Karl Max (JIRA)

When i change the default db schemas of jbm tables the DLQ - if it contains message - run in deadlock by the next server restart, because it wants to use the default schema instead of the modified db schema ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1780 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1780 Project: JBoss Messaging Issue Type: Bug Environment: JBoss 5.1.GA+Seam 2.1.1.GA+mysql 5.1 Reporter: Karl Max At first, I modified the default schema of jbm tables in mysql-persistence-service.xml so, I changed the sql properties JBM_DUAL to newSchema.JBM_DUAL and so on... Everything works fine with the modified schema, until I add a posion message to the dead letter queue. Then I want to restart the JBoss server, I get an exception to it run in dead lock, because didn't find the jbm_msg tables (but it would be newSchema.jbm_msg ) -- 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

13 years

4
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1777) Error in addMessageIDInHeader while bridging from JBossMQ

by Pedro Gontijo (JIRA)

Error in addMessageIDInHeader while bridging from JBossMQ --------------------------------------------------------- Key: JBMESSAGING-1777 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1777 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.3.GA Environment: JBoss AS 5.1.0.GA Reporter: Pedro Gontijo When addMessageIDInHeader is set to true in a JBossMQ->JBM bridge scenerio the following error occurs: WARN [org.jboss.jms.server.bridge.Bridge] (Thread-27) jboss.messaging:name=MyBridge,service=Bridge Failed to send + acknowledge batch, closing JMS objects javax.jms.JMSException: Illegal property name: JMSXDeliveryCount at org.jboss.mq.SpyMessage.checkProperty(Unknown Source) at org.jboss.mq.SpyMessage.setObjectProperty(Unknown Source) at org.jboss.jms.server.bridge.Bridge.addMessageIDInHeader(Bridge.java:1481) at org.jboss.jms.server.bridge.Bridge.sendMessages(Bridge.java:1391) at org.jboss.jms.server.bridge.Bridge.sendBatchNonTransacted(Bridge.java:1261) at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1375) at org.jboss.jms.server.bridge.Bridge.access$1900(Bridge.java:68) at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1638) at java.lang.Thread.run(Thread.java:595) As you can see the error is due JMSX properties, actually, because the addMessageIDInHeader sets then in the MQ message (which is not allowed). -- 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

13 years

4
19
0 / 0

[JBoss JIRA] Created: (JBBUILD-357) Eclipse PDE integration into Maven and unit test failure

by Mark Proctor (JIRA)

Eclipse PDE integration into Maven and unit test failure -------------------------------------------------------- Key: JBBUILD-357 URL: http://jira.jboss.com/jira/browse/JBBUILD-357 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Mark Proctor Assigned To: Paul Gier Eclipse plugin building and testing is automated by ant, executed by the Eclipse antRunner. Inside of Maven we have antRunner called in two different phases. When the test phase has unit test failures, they are not propagated up to maven, so failures are not flagged and a sucecssful build reported. Look in the drools-eclipse module of jboss rules 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

13 years

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-470) Release plugin doesn't pickup compile plugin configuration from parent

by Carlo de Wolf (JIRA)

Release plugin doesn't pickup compile plugin configuration from parent ---------------------------------------------------------------------- Key: JBBUILD-470 URL: http://jira.jboss.com/jira/browse/JBBUILD-470 Project: JBoss Build System Issue Type: Bug Environment: 4-beta2 Reporter: Carlo de Wolf Assigned To: Paul Gier Compile configuration defined in a parent pom does not get picked up by the release plugin during release. -- 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

13 years

2
4
0 / 0

[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree

by Andrew Lee Rubinger (JIRA)

Move JBossAS Maven Plugins into their own tree ---------------------------------------------- Key: JBASMP-12 URL: https://jira.jboss.org/jira/browse/JBASMP-12 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Currently under maven/plugins/jboss/trunk is: drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire -rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml Those prefixed with "maven-jboss-as" should be in their own tree -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-7) Break out Deployment-related Plugins into their own Project

by Andrew Lee Rubinger (JIRA)

Break out Deployment-related Plugins into their own Project ----------------------------------------------------------- Key: JBASMP-7 URL: http://jira.jboss.com/jira/browse/JBASMP-7 Project: JBoss AS Maven Plugins Issue Type: Task Components: control-plugin Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: 0.1.0 The Control Plugin currently houses Deployment Mojos; these should have their own 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

13 years

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-478) Create "deploy" Mojo for maven-jboss-as-control-plugin

by Andrew Lee Rubinger (JIRA)

Create "deploy" Mojo for maven-jboss-as-control-plugin ------------------------------------------------------ Key: JBBUILD-478 URL: http://jira.jboss.com/jira/browse/JBBUILD-478 Project: JBoss Build System Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The JBoss AS Control Plugin currently has Mojos for "createConfiguration", "start", and "stop". We need to add a "deploy" Mojo which delegates to congruent functionality from jboss-test. Existing Mojos: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk/maven-jboss-as-c... Root Checkout Location: http://anonsvn.jboss.org/repos/maven/plugins/jboss/trunk After the "deploy" Mojo is created, configuration to use it should be added to the "maven-jboss-as-control-example" project, following examples already in place in the POM. This is the self-documenting usage project which may also prove its validity. -- 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

13 years

3
14
0 / 0

[JBoss JIRA] Created: (JBASMP-5) Rename folder structure of modules

by Andrew Lee Rubinger (JIRA)

Rename folder structure of modules ---------------------------------- Key: JBASMP-5 URL: http://jira.jboss.com/jira/browse/JBASMP-5 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Modules are currently namespaced with "maven-jboss-as-", which is unnecessary due to the groupId and folder structure. For instance: maven-jboss-as-build ...should become: build -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBASMP-8) Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable

by Andrew Lee Rubinger (JIRA)

Switch Log4J/Commons Logging in favor of AbstractMojo.getLog() where applicable ------------------------------------------------------------------------------- Key: JBASMP-8 URL: https://jira.jboss.org/jira/browse/JBASMP-8 Project: JBoss AS Maven Plugins Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.0 Replace all instances of non-Maven Logging code to AbstractMojo.getLog() within the Mojos themselves -- 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

13 years

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 January 2010