1

当我尝试将我的 Java EE 应用程序从最新的 Eclipse 版本(带有 Glassfish 适配器版本 1.7.1 的 Helios SR2)部署到最新的 Glassfish (3.1) 时,我遇到了一个奇怪的异常。如果我通过管理控制台手动将战争文件部署到服务器,一切正常。因此,应用程序本身或 Glassfish 配置中似乎没有错误:

SCHWERWIEGEND: Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.sun.ejb.containers.TimerBean/em] in the scope of the module called [MyCMS]. Please verify your application.
java.lang.RuntimeException: Could not resolve a persistence unit corresponding to the persistence-context-ref-name [com.sun.ejb.containers.TimerBean/em] in the scope of the module called [MyCMS]. Please verify your application.
    at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUViaEMRef(BundleDescriptor.java:693)
    at com.sun.enterprise.deployment.BundleDescriptor.findReferencedPUsViaPCRefs(BundleDescriptor.java:681)
    at com.sun.enterprise.deployment.WebBundleDescriptor.findReferencedPUs(WebBundleDescriptor.java:1056)
    at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:184)
    at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:166)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:870)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
    at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465)
    at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222)
    at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
    at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:619)

有没有人遇到过 Eclipse 的类似问题并找到了解决方案?

干杯,法比安

4

3 回答 3

1

感谢卢多的帮助!我解决了我的问题:由于某种原因,eclipse 工作区到 glassfist eclipseApp 文件夹的映射不正确。更新 eclipse 导致整个 Maven 依赖库被部署。由于 derby.jar [测试] 也部署到 glassfish,我得到了这个奇怪的错误。我无法再告诉这一切是如何发生的,以及为什么这是由更新 eclipse 引起的......无论如何我通过添加以下行属性 > 部署程序集解决了这个问题:/target/myapp/WEB-INF/lib -> WEB-INF /lib

于 2011-03-02T10:54:11.643 回答
1

在将我们的应用程序从 JBoss 6-M2 移植到 Glassfish 3.1.1 时,我遇到了这个错误。persistence.xml 文件存档在META-INF 基本目录下的 ear 文件中。JBoss 找到它没有问题,但 Glassfish 在此位置存在范围问题。解决方案是重建存档,以便将 persistence.xml 存储在特定 jar 的 META-INF 目录中。

于 2011-09-16T14:36:14.050 回答
0

它是 Web 应用程序还是完整的 EAR 应用程序?我猜你部署了爆炸目录。GF 服务器属性对话框中有一个新选项部署档案而不是展开目录。你能试试吗?这将告诉问题是否真的在 Eclipse 包装方面。似乎可能没有正确设置或部署 persistence.xml 文件?

您还可以在域目录中查看服务器使用的展开目录内容。检查 eclipsApps 子目录。

于 2011-03-01T15:54:02.720 回答