hudson 版本上的 Cargo maven 插件问题

发布于 2024-11-02 17:05:04 字数 1058 浏览 3 评论 0原文

我正在尝试设置哈德森工作来发布项目。我有一个货物 Maven 插件的问题。在发布:准备和发布:执行时,它会运行两次集成测试。为了运行集成测试,我们使用 jboss 解压我们的工件,然后将 Ear 部署到实例运行测试,然后停止实例,取消部署 Ear。到这一步一切就OK了。但是,当第二次运行时,cargo maven 插件失败并出现这样的错误:

  [INFO] [ERROR] FATAL ERROR
  [INFO] [INFO] ------------------------------------------------------------------------
  [INFO] [INFO] Failed to create a JBoss 4.2.3 existing configuration
  ..
  The required web context is already in use by another application.
  [INFO]    at     org.codehaus.cargo.container.spi.deployer.AbstractCopyingInstalledLocalDeployer.deploy(AbstractCopyingInstalledLocalDeployer.java:139)
  [INFO]    at org.codehaus.cargo.container.spi.deployer.AbstractDeployer.deploy(AbstractDeployer.java:48)
  [INFO]    at org.codehaus.cargo.container.jboss.JBossExistingLocalConfiguration.doConfigure(JBossExistingLocalConfiguration.java:84)
  [INFO]    at org.codehaus.cargo.container.spi.configuration.AbstractLocalConfiguration.configure(AbstractLocalConfiguration.java:190)

所以我猜问题本身在于:所需的 Web 上下文已被另一个应用程序使用。也许有人对网络上下文有类似的问题?

i'm trying to setup hudson job to release out project. I have one problem with cargo maven plugin. On release:prepare and release:perform it runs twice our integration tests. To run integration tests we unpack our artifact with jboss, then we deploy ear to our instance run tests, then stop instance, undeploy our ear. On this step everything is ok. But when doing second run cargo maven plugin fails with such an error:

  [INFO] [ERROR] FATAL ERROR
  [INFO] [INFO] ------------------------------------------------------------------------
  [INFO] [INFO] Failed to create a JBoss 4.2.3 existing configuration
  ..
  The required web context is already in use by another application.
  [INFO]    at     org.codehaus.cargo.container.spi.deployer.AbstractCopyingInstalledLocalDeployer.deploy(AbstractCopyingInstalledLocalDeployer.java:139)
  [INFO]    at org.codehaus.cargo.container.spi.deployer.AbstractDeployer.deploy(AbstractDeployer.java:48)
  [INFO]    at org.codehaus.cargo.container.jboss.JBossExistingLocalConfiguration.doConfigure(JBossExistingLocalConfiguration.java:84)
  [INFO]    at org.codehaus.cargo.container.spi.configuration.AbstractLocalConfiguration.configure(AbstractLocalConfiguration.java:190)

So i guess the problem itself is in :The required web context is already in use by another application. Maybe someone had similar issue with webcontext?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

甜味拾荒者 2024-11-09 17:05:04

我有这样的问题。我有 2 个申请。当我检查 META-INF/context.xml 文件时,我发现两个应用程序的 Context 标记的 path 属性是相同的。当每个应用程序具有不同的上下文值时,问题就消失了。我希望它对你也有帮助。

I had such an issue. I had 2 applications. When I checked the META-INF/context.xml file, I saw that the path attribute of Context tag was same for both applications. When each application had different context value, the problem had gone. I hope it helps for you too.

魄砕の薆 2024-11-09 17:05:04

我遇到了同样的问题,但与货物插件版本有关。

出现错误

            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <version>1.6.3</version>

工作正常

            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <version>1.4.8</version>

I had the same problem but was related to cargo plugin version.

Error exhibited

            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <version>1.6.3</version>

Works correctly

            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <version>1.4.8</version>
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文