首页 文章

Glassfish,Netbeans 7.4:尚未部署模块

提问于
浏览
0

我是java ee的新手 . 制作了我的第一个持久性应用程序,但无法部署 .

错误是:

NetBeans: Deploying on GlassFish Server
    profile mode: false
    debug mode: false
    force redeploy: true
In-place deployment at C:\Users\HussainAli\Documents\NetBeansProjects\mavenproject4\target\classes
GlassFish Server, deploy, null, false
The module has not been deployed.
See the server log for details.
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:238)
    at org.netbeans.modules.maven.j2ee.ExecutionChecker.performDeploy(ExecutionChecker.java:205)
    at org.netbeans.modules.maven.j2ee.ExecutionChecker.executionResult(ExecutionChecker.java:123)
    at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:235)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)

Glassfish窗口日志(无效资源):

com.sun.appserv.connectors.internal.api.ConnectorRuntimeException:在org.glassfish.jdbcruntime.service JDBC / zoodb__pm在org.glassfish.jdbcruntime.service.JdbcDataSource.validateResource(JdbcDataSource.java:81):通过引起无效的资源位于com.sun.enterprise.connectors.ConnectorRuntime.lookupDataSourceInDAS(ConnectorRuntime.java:589)的org.glassfish.jdbcruntime.JdbcRuntimeExtension.lookupDataSourceInDAS(JdbcRuntimeExtension.java:136)的.JdbcDataSource.setResourceInfo(JdbcDataSource.java:62)...还有45个

严重:准备应用程序时出现异常:资源无效:jdbc / zoodb__pm com.sun.appserv.connectors.internal.api.ConnectorRuntimeException:无效资源:org.glassfish.jdbcruntime.service.JdbcDataSource.validateResource(JdbcDataSource.java)中的jdbc / zoodb__pm :81)atg.glassfish.jdbcruntime.service.JdbcDataSource.setResourceInfo(JdbcDataSource.java:62)at com.gun.enterprise.connectors.ConnectorRuntime的org.glassfish.jdbcruntime.JdbcRuntimeExtension.lookupDataSourceInDAS(JdbcRuntimeExtension.java:136) . lookupDataSourceInDAS(ConnectorRuntime.java:589)在com.sun.enterprise.connectors.ConnectorRuntime.lookupPMResource(ConnectorRuntime.java:517)在org.glassfish.persistence.common.PersistenceHelper.lookupPMResource(PersistenceHelper.java:63)在org.glassfish位于org.glassfish.persis的org.glassfish.persistence.jpa.PersistenceUnitInfoImpl . (PersistenceUnitInfoImpl.java:108)的.persistence.jpa.ProviderContainerContractInfoBase.lookupDataSource(ProviderContainerContractInfoBase.java:71)位于org.glassfish.persistence.jpa.PersistenceUnitLoader . (PersistenceUnitLoader.java:107)的tence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:142)org.glassfish.persistence.jpa.JPADeployer $ 1.visitPUD(JPADeployer.java: 223)在org.glassfish.persistence.jpa.JPADeployer $ PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:510)在org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:230)在org.glassfish.persistence.jpa .JPADeployer.prepare(JPADeployer.java:168)在com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:922)在com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java :431)com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)位于com.sun.enterprise的org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491) . com3.unmin.CommandRunnerImpl $ 2 $ 1 .run(CommandRunnerImpl.java:523)at java.security.AccessController.doPrivileged(Native Method)at javax.security.auth.Subject.doAs(Subject.java:360)at com.sun.enterprise.v3.admin.CommandRunnerImpl在com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:546)在com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java $ 2.execute(CommandRunnerImpl.java:522): 1423)在com.sun.enterprise.v3.admin.CommandRunnerImpl.access $ 1500(CommandRunnerImpl.java:108)com.sun.enterprise.v3.admin.CommandRunnerImpl $ ExecutionContext.execute(CommandRunnerImpl.java:1762)at com . 在com.sun.enterprise.v3的com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534)的sun.enterprise.v3.admin.CommandRunnerImpl $ ExecutionContext.execute(CommandRunnerImpl.java:1674) . admin.AdminAdapter.onMissingResource(AdminAdapter.java:224)位于com.sun.enterprise.v3.services.impl.Co的org.glassfish.grizzly.http.server.StaticHttpHandler.service(StaticHttpHandler.java:297) ntainerMapper.service(ContainerMapper.java:246)位于org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191)org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java: 168)在org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189)在org.glassfish.grizzly.filterchain.ExecutorResolver $ 9.execute(ExecutorResolver.java:119)在org.glassfish.grizzly . filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288)org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206)at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136)在org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114)在org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)在org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent( TCPNIOTransport.java:838)在org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115)在org.glassfish.grizzly .strategies.WorkerThreadIOStrategy.access $ 100(WorkerThreadIOStrategy.java:55)在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy $ WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135)在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.doWork( AbstractThreadPool.java:564)在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.run(AbstractThreadPool.java:544)在java.lang.Thread.run(Thread.java:745)

1 回答

  • 1

    这是因为一些错误的NetBeans和在GlassFish处理,因为在GlassFish中无法看到的我的SQL数据库,即使你告诉他正确地 Build 它因此要解决这个问题,你一定要到服务器面板去GlassFish服务器右击它,去"view Domain Admin Console"喜欢这里:example与任何浏览器中打开,现在选择JDBC和扩大它喜欢这里:example现在你应该创造一个新的"JDBC Resource "和新"JDBC connection Pool"那么它最终将正常工作!

相关问题