来源：蜘蛛抓取(WebSpider)
时间：2016-05-02 04:00
标签：
jboss7 ejb
spring + ejb3.x + jboss7.1 初始化不了本地的Local
[问题点数：40分，结帖人ws]
spring + ejb3.x + jboss7.1 初始化不了本地的Local
[问题点数：40分，结帖人ws]
不显示删除回复
显示所有回复
显示星级回复
显示得分回复
只显示楼主
匿名用户不能发表回复！|
每天回帖即可获得10分可用分！小技巧：
你还可以输入10000个字符
(Ctrl+Enter)
请遵守CSDN，不得违反国家法律法规。
转载文章请注明出自“CSDN（www.csdn.net）”。如是商业用途请联系原作者。EJB、JBoss和J2EE_百度知道
EJB、JBoss和J2EE
谢谢这三者是什么关系啊？有什么好的相关论坛吗？如果学JBoss，应该装哪些软件呢
提问者采纳
如jboss，所以被很多开发者抛弃，而选择了spring但EJB3.0问世后，随便copy个过来，EJB不是ERPEJB是企业级的javabean，可以很方便的被共享建议你去下载“EJB3，题目也没看清楚，EJB组件可以部署到EJB容器中，楼上这位仁兄明显外行，（tomcat只是个web容器，有了很大的改善，不支持ejb）EJB2的上手相对比较困难.0入门经典”晕，只能部署在ejb容器
提问者评价
其他类似问题
为您推荐：
其他1条回答
ERP是Enterprise Resource Planning （企业资源计划）简称，ERP是针对物资资源管理（物流）、人力资源管理（人流）、财务资源管理（财流）、信息资源管理（信息流）集成一体化的企业管理软件。它的前身——MRP和MRPⅡ。财务管理模块、生产控制管理模块、物流管理模块、采购管理、生产计划、供应链管理、成本管理。
ERP管理思想：其实质是在mrpii(manufacturing resources planning,“制造资源计划” )基础上进一步发展而成的面向供应链（supply chain）的管理思想；
软件产品：是综合应用了客户机、服务器体系、关系数据库结构、面向对象技术、图形用户界面、第四代语言（4gl）、网络通讯等信息产业成果，以erp管理思想为灵魂的软件产品；
管理系统：是整合了企业管理理念、业务流程、基础数据、人力物力、计...
ejb的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁17:22:44,076 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-2) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManagerBean': Invocation o nested exception is javax.naming.NameNotFoundException: Error looking up SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal, service service jboss.naming.context.java.global."SecurityTraceability_EAR_1.0_Alpha"."SecurityTraceability_Core_1.0_Alpha"."userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1482) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:610) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
Caused by: javax.naming.NameNotFoundException: Error looking up SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal, service service jboss.naming.context.java.global."SecurityTraceability_EAR_1.0_Alpha"."SecurityTraceability_Core_1.0_Alpha"."userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_05]
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1541) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1479) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
... 20 more
17:22:44,120 INFO
[org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-1) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
17:22:44,118 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (MSC service thread 1-2) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManagerBean': Invocation o nested exception is javax.naming.NameNotFoundException: Error looking up SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal, service service jboss.naming.context.java.global."SecurityTraceability_EAR_1.0_Alpha"."SecurityTraceability_Core_1.0_Alpha"."userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1482) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:610) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) [spring-web-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
Caused by: javax.naming.NameNotFoundException: Error looking up SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal, service service jboss.naming.context.java.global."SecurityTraceability_EAR_1.0_Alpha"."SecurityTraceability_Core_1.0_Alpha"."userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)
at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_05]
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:201) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:187) [spring-context-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1541) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1479) [spring-beans-3.2.4.RELEASE.jar:3.2.4.RELEASE]
... 20 more
17:22:44,134 INFO
[org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-1) HHH000397: Using ASTQueryTranslatorFactory
17:22:44,215 INFO
[org.hibernate.validator.util.Version] (MSC service thread 1-1) Hibernate Validator 4.2.0.Final
17:22:44,481 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart
17:22:44,498 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [] startup failed due to previous errors
17:22:44,528 INFO
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (MSC service thread 1-2) Closing Spring root WebApplicationContext
17:22:44,535 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
17:22:45,456 INFO
[org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
17:22:45,456 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 12883ms - Started 684 of 772 services (2 services failed or missing dependencies, 84 services are passive or on-demand)
17:22:45,670 INFO
[org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "SecurityTraceability_EAR_1.0_Alpha.ear" was rolled back with failure message {"JBAS014671: Failed services" =& {"jboss.web.deployment.default-host./" =& "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: JBAS018040: Failed to start context"}}
17:22:45,711 INFO
[org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'SecurityTraceability_EAR_1.0_Alpha.ear/SecurityTraceability_Core_1.0_Alpha.jar#SecurityTraceability_JPA_1.0_Alpha'
17:22:45,753 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment SecurityTraceability_Core_1.0_Alpha.jar in 92ms
17:22:45,776 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment SecurityTraceability_Platform_1.0_Alpha.war in 115ms
17:22:45,778 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment SecurityTraceability_EAR_1.0_Alpha.ear in 117ms
17:22:45,780 INFO
[org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777:
Services which failed to start:
service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: JBAS018040: Failed to start context
17:22:45,783 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" =& {"Operation step-2" =& {"JBAS014671: Failed services" =& {"jboss.web.deployment.default-host./" =& "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: JBAS018040: Failed to start context"}}}}
貌似类加载权限的问题，lz是用ear部署的吗？
引用 4 楼 yys79 的回复:
貌似类加载权限的问题，lz是用ear部署的吗？
是的。用的是ear部署的。
引用 4 楼 yys79 的回复:
貌似类加载权限的问题，lz是用ear部署的吗？
之前开发的工程师用的是 jboss 6.1
我现在需要部署到jboss7.1上开发。然后就出现这个问题了。
ejb 和 war 都在 一个 ear里面部署的。
"userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
这个错误应该是ejb找不到。你说的ejb可以启动成功，看看控制台有没有这个userManagerBean!com.ampthon.st.service.UserManagerLocal。我spring调用ejb也没做过，javaee平台我都使用cdi的。spring说实话不爱用
引用 7 楼 yys79 的回复:
"userManagerBean!com.ampthon.st.service.UserManagerLocal" is not started
这个错误应该是ejb找不到。你说的ejb可以启动成功，看看控制台有没有这个userManagerBean!com.ampthon.st.service.UserManagerLocal。我spring调用ejb也没做过，javaee平台我都使用cdi的。spring说实话不爱用
17:22:41,420 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named userManagerBean in deployment unit subdeployment "SecurityTraceability_Core_1.0_Alpha.jar" of deployment "SecurityTraceability_EAR_1.0_Alpha.ear" are as follows:
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:app/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:module/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:app/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:module/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:jboss/exported/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
这个是错误信息，我是说启动ejb的时候那些信息，应该包含哪个ejb的地址才能启动成功。
引用 9 楼 yys79 的回复:
这个是错误信息，我是说启动ejb的时候那些信息，应该包含哪个ejb的地址才能启动成功。
刚刚发的就是info信息。
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal
这就是 info信息提示的。
比如我的ejb部署时候输出的信息：
22:50:32,598 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named UserInfoServiceBean in deployment unit subdeployment "healthrec-ejb.jar" of deployment "healthrec-ear.ear" are as follows:
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:app/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:module/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean
java:app/healthrec-ejb/UserInfoServiceBean
java:module/UserInfoServiceBean
不像你的那种啊，我用的是eap-6.2跟7.1差不多的
引用 11 楼 yys79 的回复:
比如我的ejb部署时候输出的信息：
22:50:32,598 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named UserInfoServiceBean in deployment unit subdeployment "healthrec-ejb.jar" of deployment "healthrec-ear.ear" are as follows:
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:app/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:module/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean
java:app/healthrec-ejb/UserInfoServiceBean
java:module/UserInfoServiceBean
不像你的那种啊，我用的是eap-6.2跟7.1差不多的
如果用jboss 6.0跑 信息给你一样。 但是用7.1跑的时候就是我这样的信息了。
不是jboss6.0.是Jboss EAP 6.2大概对应的jbossas版本是7.3
7.1.1Final我也试过，输出与Eap6.2一样的
引用 14 楼 yys79 的回复:
7.1.1Final我也试过，输出与Eap6.2一样的
可是我启动 ejb的时候 都是info信息啊。 也没用什么错误信息啊。都是以下的信息
17:22:41,418 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named creditEao in deployment unit subdeployment "SecurityTraceability_Core_1.0_Alpha.jar" of deployment "SecurityTraceability_EAR_1.0_Alpha.ear" are as follows:
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/creditEao!com.ampthon.st.eao.CreditEao
java:app/SecurityTraceability_Core_1.0_Alpha/creditEao!com.ampthon.st.eao.CreditEao
java:module/creditEao!com.ampthon.st.eao.CreditEao
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/creditEao
java:app/SecurityTraceability_Core_1.0_Alpha/creditEao
java:module/creditEao
17:22:41,420 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named userManagerBean in deployment unit subdeployment "SecurityTraceability_Core_1.0_Alpha.jar" of deployment "SecurityTraceability_EAR_1.0_Alpha.ear" are as follows:
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:app/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:module/userManagerBean!com.ampthon.st.service.UserManagerLocal
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:app/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:module/userManagerBean!com.ampthon.st.service.UserManagerRemote
java:jboss/exported/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/userManagerBean!com.ampthon.st.service.UserManagerRemote
17:22:41,430 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named reportsManagerBean in deployment unit subdeployment "SecurityTraceability_Core_1.0_Alpha.jar" of deployment "SecurityTraceability_EAR_1.0_Alpha.ear" are as follows:
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/reportsManagerBean!com.ampthon.st.service.ReportsManagerLocal
java:app/SecurityTraceability_Core_1.0_Alpha/reportsManagerBean!com.ampthon.st.service.ReportsManagerLocal
java:module/reportsManagerBean!com.ampthon.st.service.ReportsManagerLocal
java:global/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/reportsManagerBean!com.ampthon.st.service.ReportsManagerRemote
java:app/SecurityTraceability_Core_1.0_Alpha/reportsManagerBean!com.ampthon.st.service.ReportsManagerRemote
java:module/reportsManagerBean!com.ampthon.st.service.ReportsManagerRemote
java:jboss/exported/SecurityTraceability_EAR_1.0_Alpha/SecurityTraceability_Core_1.0_Alpha/reportsManagerBean!com.ampthon.st.service.ReportsManagerRemote
引用 12 楼 ws 的回复:
Quote: 引用 11 楼 yys79 的回复:
比如我的ejb部署时候输出的信息：
22:50:32,598 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named UserInfoServiceBean in deployment unit subdeployment "healthrec-ejb.jar" of deployment "healthrec-ear.ear" are as follows:
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:app/healthrec-ejb/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:module/UserInfoServiceBean!com.test.healthrec.service.UserInfoService
java:global/healthrec-ear/healthrec-ejb/UserInfoServiceBean
java:app/healthrec-ejb/UserInfoServiceBean
java:module/UserInfoServiceBean
不像你的那种啊，我用的是eap-6.2跟7.1差不多的
如果用jboss 6.0跑 信息给你一样。 但是用7.1跑的时候就是我这样的信息了。
你这些都是本地Local Bean吧。我还需要远程连接的注解Remote
所以有可能info信息不一样吧。
能看看你的userManagerBean是怎么被spring使用的吗？唉，也就是个老项目，否则我劝你真的别用spring了。
引用 14 楼 yys79 的回复:
7.1.1Final我也试过，输出与Eap6.2一样的
我现在发现了一个问题。 就是我在本机 win7下面可以跑通。为什么到linux下面就跑不通了呢？ 是不是有什么权限问题？
引用 17 楼 yys79 的回复:
能看看你的userManagerBean是怎么被spring使用的吗？唉，也就是个老项目，否则我劝你真的别用spring了。
就是把环境从linux上拷贝下来 放到 win7下面就直接能跑起来。
对了，你们项目不用spring 那用什么架构啊
我这个程序是 ejb3.x + jboss7.1 + springMVC + Hibernate
+ nginx 这种架构。
我是说你spring怎么注入ejb的。spring事务管理有数据源死锁的bug，所以不用。而且用了spring，cdi没法用，guice也几乎没法用（guice几乎是藐视spring)。我们就是cdi,ejb3,struts2
引用 20 楼 yys79 的回复:
我是说你spring怎么注入ejb的。spring事务管理有数据源死锁的bug，所以不用。而且用了spring，cdi没法用，guice也几乎没法用（guice几乎是藐视spring)。我们就是cdi,ejb3,struts2
我现在发现了一个问题。 就是我在本机 win7下面可以跑通。为什么到linux下面就跑不通了呢？ 是不是有什么权限问题？
跑不通？你是说启动不了？
引用 22 楼 yys79 的回复:
跑不通？你是说启动不了？
就是在linux上 会出现我一开始报的那个spring 找不到jndi的错误。然后拷贝到win7下。就可以跑通了。也就是说
jboss里的web程序可以正常访问 ejb 的 jar了。
linux是不是需要开启什么关于 jndi或者是 jboss需要开启什么jndi的东西？我现在很费解。。。
其它技术资料
如果您喜欢IT行业或者对IT行业感兴趣，想开拓技术视野，欢迎加入本站官方QQ群：，在群里认识新朋友和交流技术^_^
Powered by && & 2013 &&&
