[jira] [Updated] (GERONIMO-5929) org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war on G3.0
[ https://issues.apache.org/jira/browse/GERONIMO-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang updated GERONIMO-5929: Attachment: hudson_DD.xml There are still errors when accessing Hudson, update the DD. org.apache.geronimo.kernel.config.LiefcycleException when starting Hudson.war on G3.0 - Key: GERONIMO-5929 URL: https://issues.apache.org/jira/browse/GERONIMO-5929 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0 Environment: Sun JDK 1.6.0_21, GBuild 04/19 Reporter: Chi Runhua Assignee: Shawn Jiang Attachments: hudson_DD.xml, hudson_DD.xml Hudson.war can be deployed successfully, however, it fails to start because of the following exception: 2011-04-22 10:26:13,093 ERROR [DeploymentPortlet] The application was not successfully started. start of hudson/hudson/1.384/war failed org.apache.geronimo.kernel.config.LifecycleException: start of hudson/hudson/1.384/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:718) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:681) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:521) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:702) ... 3 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration hudson/hudson/1.384/war failed to start due to the following reasons: The service J2EEApplication=null,j2eeType=WebModule,name=hudson/hudson/1.384/war did not start because ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.io.IOException: Context did not start for an unknown reason java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.io.IOException: Context did not start for an unknown reason at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:816) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:787) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:310) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:569) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:975) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:301) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:546) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at
[jira] [Created] (GERONIMO-5950) AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory
AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory --- Key: GERONIMO-5950 URL: https://issues.apache.org/jira/browse/GERONIMO-5950 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.1.7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.1.8 AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory Avoid connection creation while creating XAResource if the connection factory is not xa connection factory, also, if it is xa connection, I think that the connection should not be closed as the new created xa resource holds reference to connection. --- When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to the following are noticed: 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept connection from /127.0.0.1:48012: java.io.IOException: The transport is not running. java.io.IOException: The transport is not running. at org.apache.activemq.transport.TransportSupport.checkStarted (TransportSupport.java:103) at org.apache.activemq.transport.tcp.TcpTransport.oneway (TcpTransport.java:117) at org.apache.activemq.transport.InactivityMonitor.oneway (InactivityMonitor.java:145) at org.apache.activemq.transport.TransportFilter.oneway (TransportFilter.java:80) at org.apache.activemq.transport.WireFormatNegotiator.oneway (WireFormatNegotiator.java:93) at org.apache.activemq.transport.MutexTransport.oneway (MutexTransport.java:47) at org.apache.activemq.broker.TransportConnection.dispatch (TransportConnection.java:1138) at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805) at org.apache.activemq.broker.TransportConnection.start (TransportConnection.java:885) at org.apache.activemq.broker.TransportConnector$1.onAccept (TransportConnector.java:148) at org.apache.activemq.transport.tcp.TcpTransportServer.run (TcpTransportServer.java:162) at java.lang.Thread.run(Thread.java:736) This is because the connection used to create xa resources is closed immediately. A fix AMQ-3121-v412.patch has been posted to AMQ JIRA. The issue is resolved by (1) creating the connection only when the factory is XA and (2) caching the connection used to create xa resources and closing it when the resource adapter is stopped. This Geronimo JIRA is created to merge AMQ-3121 into our private build of AMQ and track the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5950) AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory
[ https://issues.apache.org/jira/browse/GERONIMO-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-5950: -- Description: AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory Avoid connection creation while creating XAResource if the connection factory is not xa connection factory, also, if it is xa connection, I think that the connection should not be closed as the new created xa resource holds reference to connection. --- When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to the following are noticed: 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept connection from /127.0.0.1:48012: java.io.IOException: The transport is not running. java.io.IOException: The transport is not running. at org.apache.activemq.transport.TransportSupport.checkStarted (TransportSupport.java:103) at org.apache.activemq.transport.tcp.TcpTransport.oneway (TcpTransport.java:117) at org.apache.activemq.transport.InactivityMonitor.oneway (InactivityMonitor.java:145) at org.apache.activemq.transport.TransportFilter.oneway (TransportFilter.java:80) at org.apache.activemq.transport.WireFormatNegotiator.oneway (WireFormatNegotiator.java:93) at org.apache.activemq.transport.MutexTransport.oneway (MutexTransport.java:47) at org.apache.activemq.broker.TransportConnection.dispatch (TransportConnection.java:1138) at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805) at org.apache.activemq.broker.TransportConnection.start (TransportConnection.java:885) at org.apache.activemq.broker.TransportConnector$1.onAccept (TransportConnector.java:148) at org.apache.activemq.transport.tcp.TcpTransportServer.run (TcpTransportServer.java:162) at java.lang.Thread.run(Thread.java:736) This is because the connection used to create xa resources is closed immediately. A fix AMQ-3121-v412.patch (https://issues.apache.org/jira/secure/attachment/12478376/AMQ-3121-v412.patch) has been posted to AMQ JIRA. The issue is resolved by (1) creating the connection only when the factory is XA and (2) caching the connection used to create xa resources and closing it when the resource adapter is stopped. This Geronimo JIRA is created to merge AMQ-3121 into our private build of AMQ and track the issue. was: AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory Avoid connection creation while creating XAResource if the connection factory is not xa connection factory, also, if it is xa connection, I think that the connection should not be closed as the new created xa resource holds reference to connection. --- When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to the following are noticed: 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept connection from /127.0.0.1:48012: java.io.IOException: The transport is not running. java.io.IOException: The transport is not running. at org.apache.activemq.transport.TransportSupport.checkStarted (TransportSupport.java:103) at org.apache.activemq.transport.tcp.TcpTransport.oneway (TcpTransport.java:117) at org.apache.activemq.transport.InactivityMonitor.oneway (InactivityMonitor.java:145) at org.apache.activemq.transport.TransportFilter.oneway (TransportFilter.java:80) at org.apache.activemq.transport.WireFormatNegotiator.oneway (WireFormatNegotiator.java:93) at org.apache.activemq.transport.MutexTransport.oneway (MutexTransport.java:47) at org.apache.activemq.broker.TransportConnection.dispatch (TransportConnection.java:1138) at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805)
[jira] [Commented] (GERONIMO-5950) AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory
[ https://issues.apache.org/jira/browse/GERONIMO-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029895#comment-13029895 ] Vamsavardhana Reddy commented on GERONIMO-5950: --- Completed: At revision: 1100170 in server/branches/2.1 GERONIMO-5950 AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory o Create a customized ActiveMQ 4.1.2 build for Geronimo 2.1.8. Jars changed are activemq-core and activemq-ra. o Update server poms to use this build 4.1.2-G20110506. AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory --- Key: GERONIMO-5950 URL: https://issues.apache.org/jira/browse/GERONIMO-5950 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.1.8 AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory Avoid connection creation while creating XAResource if the connection factory is not xa connection factory, also, if it is xa connection, I think that the connection should not be closed as the new created xa resource holds reference to connection. --- When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to the following are noticed: 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept connection from /127.0.0.1:48012: java.io.IOException: The transport is not running. java.io.IOException: The transport is not running. at org.apache.activemq.transport.TransportSupport.checkStarted (TransportSupport.java:103) at org.apache.activemq.transport.tcp.TcpTransport.oneway (TcpTransport.java:117) at org.apache.activemq.transport.InactivityMonitor.oneway (InactivityMonitor.java:145) at org.apache.activemq.transport.TransportFilter.oneway (TransportFilter.java:80) at org.apache.activemq.transport.WireFormatNegotiator.oneway (WireFormatNegotiator.java:93) at org.apache.activemq.transport.MutexTransport.oneway (MutexTransport.java:47) at org.apache.activemq.broker.TransportConnection.dispatch (TransportConnection.java:1138) at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805) at org.apache.activemq.broker.TransportConnection.start (TransportConnection.java:885) at org.apache.activemq.broker.TransportConnector$1.onAccept (TransportConnector.java:148) at org.apache.activemq.transport.tcp.TcpTransportServer.run (TcpTransportServer.java:162) at java.lang.Thread.run(Thread.java:736) This is because the connection used to create xa resources is closed immediately. A fix AMQ-3121-v412.patch (https://issues.apache.org/jira/secure/attachment/12478376/AMQ-3121-v412.patch) has been posted to AMQ JIRA. The issue is resolved by (1) creating the connection only when the factory is XA and (2) caching the connection used to create xa resources and closing it when the resource adapter is stopped. This Geronimo JIRA is created to merge AMQ-3121 into our private build of AMQ and track the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5950) AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory
[ https://issues.apache.org/jira/browse/GERONIMO-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029901#comment-13029901 ] Vamsavardhana Reddy commented on GERONIMO-5950: --- Completed: At revision: 1100181 in server/branches/2.1 GERONIMO-5950 AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory o Update repository pom so that custom activemq-ra jar gets copied over to local maven repo during build AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory --- Key: GERONIMO-5950 URL: https://issues.apache.org/jira/browse/GERONIMO-5950 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ Affects Versions: 2.1.7 Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.1.8 AMQ-3121: Avoid connection creation while creating XAResource if the connection factory is not an xa connection factory Avoid connection creation while creating XAResource if the connection factory is not xa connection factory, also, if it is xa connection, I think that the connection should not be closed as the new created xa resource holds reference to connection. --- When an MDB EJB is deployed in Geronimo 2.1.7, some IOExceptions similar to the following are noticed: 2011-03-17 10:25:05,035 ERROR [TransportConnector] Could not accept connection from /127.0.0.1:48012: java.io.IOException: The transport is not running. java.io.IOException: The transport is not running. at org.apache.activemq.transport.TransportSupport.checkStarted (TransportSupport.java:103) at org.apache.activemq.transport.tcp.TcpTransport.oneway (TcpTransport.java:117) at org.apache.activemq.transport.InactivityMonitor.oneway (InactivityMonitor.java:145) at org.apache.activemq.transport.TransportFilter.oneway (TransportFilter.java:80) at org.apache.activemq.transport.WireFormatNegotiator.oneway (WireFormatNegotiator.java:93) at org.apache.activemq.transport.MutexTransport.oneway (MutexTransport.java:47) at org.apache.activemq.broker.TransportConnection.dispatch (TransportConnection.java:1138) at org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805) at org.apache.activemq.broker.TransportConnection.start (TransportConnection.java:885) at org.apache.activemq.broker.TransportConnector$1.onAccept (TransportConnector.java:148) at org.apache.activemq.transport.tcp.TcpTransportServer.run (TcpTransportServer.java:162) at java.lang.Thread.run(Thread.java:736) This is because the connection used to create xa resources is closed immediately. A fix AMQ-3121-v412.patch (https://issues.apache.org/jira/secure/attachment/12478376/AMQ-3121-v412.patch) has been posted to AMQ JIRA. The issue is resolved by (1) creating the connection only when the factory is XA and (2) caching the connection used to create xa resources and closing it when the resource adapter is stopped. This Geronimo JIRA is created to merge AMQ-3121 into our private build of AMQ and track the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] trunk: Failed for Revision: 1100425
Geronimo Revision: 1100425 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110506/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110506/unit-test-reports at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.maven.wagon:wagon-provider-api:jar': Cannot find parent: org.apache.maven:maven-parent for project: org.apache.maven.wagon:wagon:pom:1.0-beta-2 for project org.apache.maven.wagon:wagon:pom:1.0-beta-2 org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), central (http://repo1.maven.org/maven2), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), openqa-releases (http://nexus.openqa.org/content/repositories/releases), jetty.oss.sonatype.org (http://oss.sonatype.org/content/groups/jetty-with-staging), java.net2 (http://download.java.net/maven/2/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 2) org.apache.maven:maven-project:jar:2.0.7 3) org.apache.maven:maven-artifact-manager:jar:2.0.7 at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:430) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:835) at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1629) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582) ... 15 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.maven.wagon:wagon-provider-api:jar': Cannot find parent: org.apache.maven:maven-parent for project: org.apache.maven.wagon:wagon:pom:1.0-beta-2 for project org.apache.maven.wagon:wagon:pom:1.0-beta-2 at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387) ... 23 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.maven:maven-parent for project: org.apache.maven.wagon:wagon:pom:1.0-beta-2 for project org.apache.maven.wagon:wagon:pom:1.0-beta-2 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1407) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163) ... 25 more Caused
[BUILD] branches/2.2: Failed for Revision: 1100411
Geronimo Revision: 1100411 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110507/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110507/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.activemq:activemq-web-console:war:5.4.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.activemq -DartifactId=activemq-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.activemq -DartifactId=activemq-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT 2) org.apache.activemq:activemq-web-console:war:5.4.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.activemq:activemq-web-console:war:5.4.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.activemq -DartifactId=activemq-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.activemq -DartifactId=activemq-web-console -Dversion=5.4.2 -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT 2) org.apache.activemq:activemq-web-console:war:5.4.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole:war:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at