在Eclipse Helios SR2之外部署Glassfish失败
当我尝试将Java应用程序从最新的Eclipse版本(Helios适配器版本为1.7.1)部署到最新的Glassfish (3.1)时，我遇到了一个奇怪的异常。如果我通过管理控制台手动将war文件部署到服务器，则一切正常。因此，似乎不是由于应用程序本身或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中遇到过类似的问题，并找到了解决方案？
干杯，法比安
回答 3
Stack Overflow用户
发布于 2011-03-02 18:54:12
谢谢Ludo的帮助！我解决了我的问题:由于某些原因，eclipse工作区到glassfist eclipseApp文件夹的映射不正确。更新eclipse会导致部署整个Maven依赖库。因为derby.jar测试也被部署到glassfish上，所以我得到了这个奇怪的bug。我不知道这一切是如何发生的，以及为什么这是由更新eclipse...anyway引起的。我通过添加以下行属性>部署程序集解决了这个问题: /target/myapp/WEB-INF/lib -> WEB-INF/lib
Stack Overflow用户
发布于 2011-09-16 22:36:14
在将我们的应用程序从JBoss 6-M2移植到Glassfish 3.1.1时，我遇到了这个错误。persistence.xml文件存档在META-INF基目录下的ear文件中。JBoss找到它没有问题，但Glassfish在这个位置有作用域问题。解决方案是重新构建归档文件，以便将persistence.xml存储在特定jar的META-INF目录中。
Stack Overflow用户
发布于 2011-03-01 23:54:03
它是Web应用程序还是完整的EAR应用程序？我猜你是用分解目录部署的。在GF服务器属性对话框中有一个新的选项，用于部署存档文件而不是分解目录。你能试试吗？这将告诉我们问题是否真的存在于Eclipse打包方面。可能是persistence.xml文件没有正确设置或部署？
您还可以在域目录中查看服务器使用的分解目录内容。检查eclipsApps子目录。
https://stackoverflow.com/questions/5154828
复制相似问题
腾讯云开发者
