Weblogic10.3.5上发布EJB项目出错,找不到数据源

问题描述

Jndi数据源:OracleDs数据源正常。<?xmlversion="1.0"encoding="UTF-8"?><persistencexmlns="http://java.sun.com/xml/ns/persistence"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://java.sun.com/xml/ns/persistencehttp://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"version="2.0"><persistence-unitname="report"transaction-type="JTA"><provider>org.hibernate.ejb.HibernatePersistence</provider><jta-data-source>java:/OracleDs</jta-data-source><properties><propertyname="hibernate.transaction.manager_lookup_class"value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/><propertyname="hibernate.dialect"value="org.hibernate.dialect.Oracle10gDialect"/></properties></persistence-unit></persistence>

解决方案二:
#<2012-3-30下午03时32分08秒CST><Error><Deployer><MICROSOF-11756B><AdminServer><[ACTIVE]ExecuteThread:'0'forqueue:'weblogic.kernel.Default(self-tuning)'><<WLSKernel>><><><1333092728437><BEA-149231><Unabletosettheactivationstatetotruefortheapplication'reportService'.javax.naming.NameNotFoundException:remainingname:/OracleDsatweblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)atweblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)atweblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)atweblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:64)atweblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)atweblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)atjavax.naming.InitialContext.lookup(InitialContext.java:392)atorg.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:75)atorg.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:137)atorg.hibernate.ejb.InjectionSettingsFactory.createConnectionProvider(InjectionSettingsFactory.java:29)atorg.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:89)atorg.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)atorg.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1325)atorg.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)atorg.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)atorg.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132)atweblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)atweblogic.deployment.BasePersistenceUnitInfoImpl.activate(BasePersistenceUnitInfoImpl.java:788)atweblogic.deployment.PersistenceUnitInfoImpl.activate(PersistenceUnitInfoImpl.java:19)atweblogic.ejb.container.deployer.EJBModule.reconfigPersistenceUnits(EJBModule.java:554)atweblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:538)atweblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)atweblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)atweblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)atweblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)atweblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)atweblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)atweblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)atweblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)atweblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)atweblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)atweblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)atweblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)atweblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)atweblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)atweblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)atweblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)atweblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)atweblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)atweblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)atweblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)atweblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)atweblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)atweblogic.work.ExecuteThread.execute(ExecuteThread.java:209)atweblogic.work.ExecuteThread.run(ExecuteThread.java:178)CausedBy:javax.naming.NameNotFoundException:remainingname:/OracleDsatweblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)atweblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)atweblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)atweblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:64)atweblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)atweblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)atjavax.naming.InitialContext.lookup(InitialContext.java:392)atorg.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:75)atorg.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:137)atorg.hibernate.ejb.InjectionSettingsFactory.createConnectionProvider(InjectionSettingsFactory.java:29)atorg.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:89)atorg.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)atorg.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1325)atorg.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)atorg.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)atorg.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132)atweblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)atweblogic.deployment.BasePersistenceUnitInfoImpl.activate(BasePersistenceUnitInfoImpl.java:788)atweblogic.deployment.PersistenceUnitInfoImpl.activate(PersistenceUnitInfoImpl.java:19)atweblogic.ejb.container.deployer.EJBModule.reconfigPersistenceUnits(EJBModule.java:554)atweblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:538)atweblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)atweblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)atweblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)atweblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)atweblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)atweblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)atweblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)atweblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)atweblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)atweblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)atweblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)atweblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)atweblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)atweblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)atweblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)atweblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)atweblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)atweblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)atweblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)atweblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)atweblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)atweblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)atweblogic.work.ExecuteThread.execute(ExecuteThread.java:209)atweblogic.work.ExecuteThread.run(ExecuteThread.java:178)>

时间: 2024-10-23 12:46:46

Weblogic10.3.5上发布EJB项目出错,找不到数据源的相关文章

在IIS上发布silverlight项目,本机可正常访问,可在其他机子用浏览器输入地址访问却报错的问题

问题描述 在IIS上发布silverlight项目,本机访问正常,可在其他机子用浏览器输入地址访问却报错,如图: 解决方案 解决方案二:求各路大神解答!什么跨文件域的clientaccesspolicy.xmlcrossdomain.xml都已经放根目录了!解决方案三:我还是很好奇,为啥都喜欢把xap所在的站点和WCF站点分开--解决方案四:引用1楼xqf567765的回复: 求各路大神解答!什么跨文件域的clientaccesspolicy.xmlcrossdomain.xml都已经放根目录了

服务器上报404错误-vs2013开发的项目,服务器上发布报404错误

问题描述 vs2013开发的项目,服务器上发布报404错误 vs2013开发的项目,在本地发布运行正常,但是发布到服务器上,登陆成功后,跳转后报404错误,找不到文件.网上搜了解决404错误的解决方法,基本上都试过了,还是没找到解决方法,不知道哪位大神也遇到过这样的问题,比较着急.我的登录成功的跳转实在登录页的前端设置的 $(":button").click(function () { $.ajax({ type: "GET", url: "/Handle

javaweb-在linux服务器上重新发布java项目运行的代码不是最新的

问题描述 在linux服务器上重新发布java项目运行的代码不是最新的 我在方法中加了print打印,重新编译后在本机运行可以打印出来内容,但是把class文件重新部署到服务器上就不行了,tomcat也重启了,服务器也reboot了,项目也重新部署了几次,但是执行的代码不是最新的,控制台也没输出打印的内容 解决方案 服务器不要有print输出语句,你想看结果就用日志,服务器不推荐用print

跪求大神-关于websphere上发布项目的问题

问题描述 关于websphere上发布项目的问题 websohere装在服务器上,为linux系统,websphere部署项目正常,可以从客户端上访问到项目的主页,但是页面的的静态文件(.js .css)还有图片的路径全部失效.求大神提供解决办法!!!!! 解决方案 http://wenku.baidu.com/link?url=oifr7snZbrOdVN3YPpo5wL4ZQbd_PgeMACKTmDavz86njXuqbF8KhOM-0kuXsTzdZJ14ab0-9nHpOzoYxIyi

java-在myeclipse上导入web项目发布后运行很慢

问题描述 在myeclipse上导入web项目发布后运行很慢 我在myeclipse导入了一个web项目,发布完成后,输入网址运行,打开一次登录页面要很久,提交一次登录也要好久,大概半个小时,是怎么了呀?谢谢了 解决方案 如果你是把项目部署到Tomcat服务器的话,就去Tomcat的目录下将webapps文件夹的文件和work文件夹下的全部文件全部删除,在重新部署就好了.

ejb项目发布到websphere服务器失败

问题描述 ejb项目发布到websphere服务器失败,异常如下,各位帮我看看[11-5-513:51:08:765CST]0000003cApplicationMgAWSVR0200I:正在启动应用程序:EnfoCRMEAR[11-5-513:51:09:046CST]0000003cEJBContainerIIWSVR0207I:正在准备启动EJBjar:EnfoCRMEJB.jar[11-5-513:51:09:062CST]0000003cEJBContainerIIWSVR0037I:

MyEclipse 8.6在WebLogic10上部署SSH2项目出现了一下错误:

问题描述 MyEclipse8.6在WebLogic10上部署SSH2项目出现了一下错误:java.lang.ClassNotFoundException:javax.faces.webapp.UIComponentBodyTag在网search一下,解决ClassNotFoundException异常最常用的办法就是将出现异常类所在的jar包入到weblogic环境中的classpath最前面加载,将相应的antlr-2.7.6.jar.hibernate-jpa-2.0-api-1.0.0.

exception-eclipse+wildfly10创建简单Ejb实例出错

问题描述 eclipse+wildfly10创建简单Ejb实例出错 package ejb3;//HelloWorld接口 public interface HelloWorld { public String SayHello(String name); } package ejb3.impl;//HelloWorldBean实现接口HelloWorld import ejb3.HelloWorld; import javax.ejb.*; @Stateless @Remote({HelloW

java-windows2008发布JAVA项目-SSH 可以吗

问题描述 windows2008发布JAVA项目-SSH 可以吗 JAVA项目使用SSH框架开发.数据用的是SqlServer的.本来想用MySql的..是数据量大..有引起表有上百万或上千万的记录. 解决方案 你不知道Java是所谓的跨平台的吗??