[EJB3] - Re: Random NameNotFoundException in jboss 6.1-SNAPSHOT
by legae
legae [http://community.jboss.org/people/legae] created the discussion
"Re: Random NameNotFoundException in jboss 6.1-SNAPSHOT"
To view the discussion, visit: http://community.jboss.org/message/601361#601361
--------------------------------------------------------------
10:48:26,196 INFO [STDOUT] myBeanLocal: Proxy to jboss.j2ee:ear=my.ear,jar=my.jar,name=MyDependBean,service=EJB3 implementing [interface com.app.ifaces.MyDependBeanLocal]
10:48:26,197 ERROR [CMTTxInterceptor] javax.ejb.EJBTransactionRolledbackException: javax.naming.NameNotFoundException: com.app.MyDependBean not bound
10:48:26,204 INFO [STDOUT] 10:48:26,201 ERROR [AService]
10:48:26,205 INFO [STDOUT] javax.ejb.EJBTransactionRolledbackException: javax.naming.NameNotFoundException: com.app.MyDependBean not bound
10:48:26,209 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:148)
10:48:26,211 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:227)
10:48:26,214 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.required(CMTTxInterceptor.java:353)
10:48:26,216 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:209)
10:48:26,218 INFO [STDOUT] at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
10:48:26,220 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,222 INFO [STDOUT] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
10:48:26,223 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,225 INFO [STDOUT] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
10:48:26,228 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,230 INFO [STDOUT] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:182)
10:48:26,232 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,234 INFO [STDOUT] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
10:48:26,235 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,238 INFO [STDOUT] at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
10:48:26,241 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,243 INFO [STDOUT] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
10:48:26,247 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,249 INFO [STDOUT] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
10:48:26,252 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,254 INFO [STDOUT] at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
10:48:26,257 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,260 INFO [STDOUT] at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:333)
10:48:26,262 INFO [STDOUT] at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:390)
10:48:26,265 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor437.invoke(Unknown Source)
10:48:26,266 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:48:26,268 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:597)
10:48:26,270 INFO [STDOUT] at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalContainerInvocation.invokeTarget(
SessionLocalProxyInvocationHandler.java:184)
10:48:26,274 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
10:48:26,276 INFO [STDOUT] at org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor.invoke(AsynchronousClientInterceptor.java:143)
10:48:26,279 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,281 INFO [STDOUT] at org.jboss.ejb3.proxy.impl.handler.session.SessionLocalProxyInvocationHandler$LocalInvokableContextHandler.invoke(Se
ssionLocalProxyInvocationHandler.java:159)
10:48:26,285 INFO [STDOUT] at $Proxy258.invoke(Unknown Source)
10:48:26,288 INFO [STDOUT] at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBas
e.java:185)
10:48:26,291 INFO [STDOUT] at $Proxy302.findAll(Unknown Source)
10:48:26,292 INFO [STDOUT] at com.app.AService.onCreate(AService.java:49)
10:48:26,294 INFO [STDOUT] at com.app.service.AbstractService.create(AbstractService.java:46)
10:48:26,297 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:48:26,299 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:48:26,302 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:48:26,304 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:597)
10:48:26,306 INFO [STDOUT] at org.jboss.ejb3.interceptors.aop.LifecycleCallbackBeanMethodInterceptor.invoke(LifecycleCallbackBeanMethodIntercepto
r.java:69)
10:48:26,310 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,313 INFO [STDOUT] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.ja
va:56)
10:48:26,320 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,322 INFO [STDOUT] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
10:48:26,325 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,327 INFO [STDOUT] at org.jboss.ejb3.singleton.aop.impl.ConstructionInvocationContextAdapter.proceed(ConstructionInvocationContextAdapter
.java:106)
10:48:26,331 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:247)
10:48:26,332 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:392)
10:48:26,334 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invoke(CMTTxInterceptor.java:211)
10:48:26,336 INFO [STDOUT] at org.jboss.ejb3.tx2.aop.CMTTxInterceptorWrapper.invoke(CMTTxInterceptorWrapper.java:52)
10:48:26,338 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,340 INFO [STDOUT] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
10:48:26,343 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,345 INFO [STDOUT] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
10:48:26,348 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,350 INFO [STDOUT] at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:90)
10:48:26,352 INFO [STDOUT] at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_19778444.invoke(Invocatio
nContextInterceptor_z_setup_19778444.java)
10:48:26,355 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,357 INFO [STDOUT] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
10:48:26,359 INFO [STDOUT] at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:80)
10:48:26,362 INFO [STDOUT] at org.jboss.ejb3.singleton.aop.impl.AOPBasedSingletonContainer.invokeCallback(AOPBasedSingletonContainer.java:1059)
10:48:26,364 INFO [STDOUT] at org.jboss.ejb3.EJBContainer.invokePostConstruct(EJBContainer.java:1396)
10:48:26,366 INFO [STDOUT] at org.jboss.ejb3.singleton.aop.impl.AOPBasedSingletonContainer.postConstruct(AOPBasedSingletonContainer.java:760)
10:48:26,367 INFO [STDOUT] at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java
:133)
10:48:26,371 INFO [STDOUT] at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.get(SingletonEJBInstanceManagerImpl.java:15
2)
10:48:26,375 INFO [STDOUT] at org.jboss.ejb3.singleton.deployer.StartupSingletonInitiator.start(StartupSingletonInitiator.java:84)
10:48:26,378 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:48:26,381 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:48:26,383 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:48:26,387 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:597)
10:48:26,390 INFO [STDOUT] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60)
10:48:26,395 INFO [STDOUT] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168)
10:48:26,398 INFO [STDOUT] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
10:48:26,401 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelController
ContextAction.java:257)
10:48:26,405 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
10:48:26,407 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextA
ction.java:125)
10:48:26,411 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.j
ava:72)
10:48:26,415 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202)
10:48:26,417 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
10:48:26,418 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
10:48:26,422 INFO [STDOUT] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction
.java:62)
10:48:26,426 INFO [STDOUT] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
10:48:26,428 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
10:48:26,432 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379)
10:48:26,435 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
10:48:26,437 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083)
10:48:26,439 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322)
10:48:26,441 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246)
10:48:26,443 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139)
10:48:26,445 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894)
10:48:26,447 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641)
10:48:26,450 INFO [STDOUT] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:182)
10:48:26,453 INFO [STDOUT] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58)
10:48:26,455 INFO [STDOUT] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:
63)
10:48:26,459 INFO [STDOUT] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
10:48:26,461 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
10:48:26,463 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832)
10:48:26,465 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550)
10:48:26,467 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571)
10:48:26,470 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1603)
10:48:26,472 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491)
10:48:26,474 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379)
10:48:26,477 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
10:48:26,479 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083)
10:48:26,481 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322)
10:48:26,484 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246)
10:48:26,486 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139)
10:48:26,489 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939)
10:48:26,491 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654)
10:48:26,493 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983)
10:48:26,496 INFO [STDOUT] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076)
10:48:26,498 INFO [STDOUT] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679)
10:48:26,500 INFO [STDOUT] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106)
10:48:26,504 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java
:143)
10:48:26,508 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151)
10:48:26,510 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94)
10:48:26,514 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
10:48:26,516 INFO [STDOUT] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
10:48:26,518 INFO [STDOUT] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction
.java:62)
10:48:26,522 INFO [STDOUT] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
10:48:26,524 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
10:48:26,527 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379)
10:48:26,529 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
10:48:26,532 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083)
10:48:26,534 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322)
10:48:26,536 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246)
10:48:26,539 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139)
10:48:26,541 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939)
10:48:26,543 INFO [STDOUT] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654)
10:48:26,546 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.
java:190)
10:48:26,549 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87)
10:48:26,551 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215)
10:48:26,554 INFO [STDOUT] at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159)
10:48:26,557 INFO [STDOUT] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:11
2)
10:48:26,560 INFO [STDOUT] at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87)
10:48:26,563 INFO [STDOUT] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91)
10:48:26,565 INFO [STDOUT] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.ja
va:132)
10:48:26,569 INFO [STDOUT] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.ja
va:56)
10:48:26,573 INFO [STDOUT] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827)
10:48:26,575 INFO [STDOUT] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417)
10:48:26,577 INFO [STDOUT] at java.lang.Thread.run(Thread.java:619)
10:48:26,579 INFO [STDOUT] Caused by: org.jboss.injection.manager.spi.InjectionException: javax.naming.NameNotFoundException: com.app.MyDependBean not bound
10:48:26,583 INFO [STDOUT] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:86)
10:48:26,585 INFO [STDOUT] at org.jboss.injection.manager.core.DefaultInjectionContext.proceed(DefaultInjectionContext.java:58)
10:48:26,588 INFO [STDOUT] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:58)
10:48:26,590 INFO [STDOUT] at org.jboss.injection.manager.core.DefaultInjectionManager.inject(DefaultInjectionManager.java:64)
10:48:26,592 INFO [STDOUT] at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:140)
10:48:26,595 INFO [STDOUT] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:125)
10:48:26,597 INFO [STDOUT] at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
10:48:26,601 INFO [STDOUT] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116)
10:48:26,603 INFO [STDOUT] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
10:48:26,605 INFO [STDOUT] at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:116)
10:48:26,607 INFO [STDOUT] at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1363)
10:48:26,610 INFO [STDOUT] at org.jboss.ejb3.stateless.StatelessContainer.createBeanContext(StatelessContainer.java:139)
10:48:26,613 INFO [STDOUT] at org.jboss.ejb3.pool.AbstractPool.createBeanContext(AbstractPool.java:94)
10:48:26,615 INFO [STDOUT] at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:81)
10:48:26,618 INFO [STDOUT] at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:62)
10:48:26,620 INFO [STDOUT] at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:57)
10:48:26,622 INFO [STDOUT] at org.jboss.ejb3.pool.ThreadlocalPool.create(ThreadlocalPool.java:54)
10:48:26,624 INFO [STDOUT] at org.jboss.ejb3.pool.ThreadlocalPool.get(ThreadlocalPool.java:86)
10:48:26,626 INFO [STDOUT] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58)
10:48:26,629 INFO [STDOUT] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
10:48:26,631 INFO [STDOUT] at org.jboss.ejb3.core.context.SessionInvocationContextAdapter.proceed(SessionInvocationContextAdapter.java:95)
10:48:26,634 INFO [STDOUT] at org.jboss.ejb3.tx2.impl.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:223)
10:48:26,636 INFO [STDOUT] ... 141 more
10:48:26,639 INFO [STDOUT] Caused by: javax.naming.NameNotFoundException: com.app.MyDependBean not bound
10:48:26,641 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
10:48:26,644 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
10:48:26,646 INFO [STDOUT] at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
10:48:26,649 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
10:48:26,651 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
10:48:26,653 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728)
10:48:26,655 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835)
10:48:26,657 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)
10:48:26,659 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:392)
10:48:26,661 INFO [STDOUT] at org.jboss.injection.injector.EEInjector.lookup(EEInjector.java:152)
10:48:26,663 INFO [STDOUT] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:132)
10:48:26,666 INFO [STDOUT] at org.jboss.injection.injector.EEInjector.inject(EEInjector.java:81)
10:48:26,668 INFO [STDOUT] ... 162 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/601361#601361]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 11 months
[EJB3] - 'You cannot commit during a managed transaction' issue
by Catalin Moga
Catalin Moga [http://community.jboss.org/people/mcatalin23] created the discussion
"'You cannot commit during a managed transaction' issue"
To view the discussion, visit: http://community.jboss.org/message/601302#601302
--------------------------------------------------------------
I'm using Jboss 6 and Ejb 3.1.
Session beans are deployed into jboss using deplyment descriptor xml-jar.xml.
The client is calling ejb methods using lookup:
+MyInterface sessionService = (MyInterface) namingContext.lookup(appname + MyBean.class.getSimpleName() + "/remote");+
The connection works well but I have an issue with the transaction while calling commit, rollback...:
+java.sql.SQLException: *You cannot commit during a managed transaction*!+
+ at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcCommit(BaseWrapperManagedConnection.java:661)+
+ at org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:496)+
+ at com.....MyBeanClass.MyBeanMethod(MyBeanClass.java:328)+
I've read that "+by default enterprise beans use container-managed transactions. Enterprise beans that use container-managed transaction demarcation must not use any transaction management methods that interfere with the container’s transaction demarcation boundaries. Examples of such methods are the commit, setAutoCommit, and rollback. If you require control over the transaction demarcation, you must use application-managed transaction demarcation.+"
The idea is that I want to use manually commit, rollback... but I don't know how. Is the information above the right direction for what I need? Should I use application managed transactions instead of container managed transactions which is default? How can I do this? Any documentation on this would help too. Thank you.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/601302#601302]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 11 months
[JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP
by Andre Dietisheim
Andre Dietisheim [http://community.jboss.org/people/adietish] modified the document:
"Create GWT Projects with JBoss Tools and Eclipse WTP"
To view the document, visit: http://community.jboss.org/docs/DOC-15794
--------------------------------------------------------------
h1. Use Eclipse WTP, get there with the standard
If you want to create GWT applications you unfortunately cannot do it the WTP way and create a so called dynamic web project. The Google plugins implement their own set of views, wizards, launchers and mostly duplicate what's already present and defacto standard in WTP. The consequence is that you'd have to deal with workarounds if you want to get functionalities (run/deploy on JBoss etc.) Google does not offer.
We therefore developed an experimental integration plugin for GWT that allows you to create GWT projects in the way most Eclipse users are used to: by creating Dynamic Web Projects.
> *Hint:* ** We currently offer a WTP facet for GWT in *JBoss Tools 3.2.1* only. JBoss Tools 3.3.x is based on Eclipse 3.7 / Indigo and Google only offers a GWT plugin for Eclipse 3.6 for now. We will catch up as soon as they'll release an Indigo compliant version.
h1. Preface
Eclipse offers nice tools to create web applications. The base framework's what we call the Eclipse Web Tools Platform (WTP). Eclipse WTP delivers a standard for most aspects involved when you create web applications.
The google web toolkit, GWT, is a nice framework to develop web applications. Google delivers a plugin for Eclipse and developing with GWT is a very pleasant experience. The GWT plugin uses an embedded jetty to run the application that you develop. Google unfortunately did not base its work on Eclipse WTP and does not comply to the Eclipse project structure for web application. So if you want to use JBoss instead of jetty, the approach to take is not as handy and intuitive as it could be. Furthermore there's no way to use and integrate into plugins that other solution providers offer. You mostly have to proceed by workarounds to get what Google does not offer.
We developed a set of (experimental) plugins that create GWT projects by extending Eclipse WTP. Our plugins implement well known usage patterns and integrate well with all Eclipse components that use the common standard for web projects. The most obvious benefit is that deploying to JEE application servers (and JBoss partcullarly) is as easy as it is with any other web project.
h1. Solution
Install and use the JBoss GWT Integration. You'll then be able to create GWT projects the WTP way and fully enjoy it's full-blow features and standardized usage patterns.
This How-To shows you all the steps to install the plugins and how to create a dynamic web project that's GWT enabled.
h2. Install Google Plugin for Eclipse
Add the Google update site
> http://dl.google.com/eclipse/plugin/3.6 http://dl.google.com/eclipse/plugin/3.6
And Install the Google Plugin for Eclipse 3.6 and the GWT SDK.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-161... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
h2. Install JBoss GWT Integration
Add the JBoss Tools 3.2.x update site:
> http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/ http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/
And Install the JBoss GWT Integration
http://community.jboss.org/servlet/JiveServlet/showImage/6254/Picture+4.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6254/Picture...
h2. Create a Dynamic Web Application Project
Make sure you have a JEE server (JBoss application server for instance) in your Eclipse environment. If not, download and declare it to your Eclipse IDE:
http://community.jboss.org/servlet/JiveServlet/showImage/6260/Picture+12.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6260/Picture...
http://community.jboss.org/servlet/JiveServlet/showImage/6259/Picture+11.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6259/Picture...
You're now ready to create a *Dynamic Web Project*.
http://community.jboss.org/servlet/JiveServlet/showImage/6256/Picture+5.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6256/Picture...
The wizard picks your server (runtime) and allows you to configure the various characteristic of your web project.
The *configuration* group allows you to pick the different facets of your project. We provide a *Google Web Toolkit* facet that will configure the GWT related characteristics.
Hit *Modify...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
and select the *Google Web Toolkit* facet.
http://community.jboss.org/servlet/JiveServlet/showImage/6262/Picture+14.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6262/Picture...
A few wizard steps further, you may choose to get some GWT *sample code*.
http://community.jboss.org/servlet/JiveServlet/showImage/6411/generate-sa... http://community.jboss.org/servlet/JiveServlet/downloadImage/6411/generat...
You get the Hello World sample that you get when you use the Google Wizard. We just put it to the *WebContent* folder you configured in your Dynamic Web Project wizard (WTP default opposed to what Google does in their plugin). The sample's a fully working GWT application that allows you to get a first impression of what developing with GWT looks like.
h1. Cross compile to Javascript
GWT is about programming in Java and getting javascript for the browser. GWT achieves this with a cross-compiler that creates the javascript for you.
In order to get the project up and running you now need to cross compile the sample's client java code to javascript. Our project has the *GWT nature* and therefore offers the Google compiler in the context menu.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
h1. Deploy to JBoss
We are now ready to deploy our application. We strictly use the standard Eclipse *WTP* infrastructure in our setup, So you may deploy your GWT application in the same manner you usually deploy and run classic web applications with Eclipse WTP. You have to add the application to a server that's registered in the WTP *servers view*. We deploy our application to our JBoss application server by selecting it in the and choosing *Add and Remove...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
You can now add the GWT application to your server. WTP will make sure that it gets deployed and the deployed artifacts are in sync with your workspace (even when you change code, resources, configurations, etc.)
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
h1. Run your application and launch your browser
You may now run your application. We completely comply to the views and steps Eclipse WTP offers to web developers. So there's no custom way to start a server in our setup. We select our JBoss instance in the *Servers view* and *start* it.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
You can now point your browser to the address and port that your JBoss server's bound to.
http://community.jboss.org/servlet/JiveServlet/showImage/6271/Picture+2.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6271/Picture...
h2. Speed up my development cycle!
The approach we've choosen so far uses an extra cross compile step to deploy the application after each change. That's very reliable but it gets tedious at development time. Google delivers a so called hosted/development mode. Its major benefit is that you dont need to cross compile on each change but you can change and test on the fly. This magic is achieved with a browser plugin and a google runtime that interprets your java code at runtime. Changing, testing, changing, testing etc. gets much faster and pleasant, the cross-compilation step's not needed any more.
h2. Launch GWT Codeserver
If you launch your application as Google Web Application, you'll be able to code and test on the fly. The GWT browser plugin will communicate with the GWT code server and execute your changes on the fly.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
You need to tell the browser plugin where your code server may be reached. You do that by using an *additional url parameter*. Your browser URL now reads as follows:
> http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997
Point your browser to this URL and you'll get the same page as before, nothing spectacular so far.
Now get back to your client code and change the button label, to see if changes are picked on the fly now.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
Do not cross-compile, get back to your browser and reload. What you see reflects the changes in your code. You don't need to cross compile to develop your app!
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-22-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-22...
To be picky on the issue you could now go to the launch configuration and disable the jetty google usually uses to serve your GWT application:
http://community.jboss.org/servlet/JiveServlet/showImage/6413/disable-bui... http://community.jboss.org/servlet/JiveServlet/downloadImage/6413/disable...
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15794]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 11 months
[JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP
by Andre Dietisheim
Andre Dietisheim [http://community.jboss.org/people/adietish] modified the document:
"Create GWT Projects with JBoss Tools and Eclipse WTP"
To view the document, visit: http://community.jboss.org/docs/DOC-15794
--------------------------------------------------------------
h1. Use Eclipse WTP, get there with the standard
If you want to create GWT applications you unfortunately cannot do it the WTP way and create a so called dynamic web project. The Google plugins implement their own set of views, wizards, launchers and mostly duplicate what's already present and defacto standard in WTP. The consequence is that you'd have to deal with workarounds if you want to get functionalities (run/deploy on JBoss etc.) Google does not offer.
We therefore developed an experimental integration plugin for GWT that allows you to create GWT projects in the way most Eclipse users are used to: by creating Dynamic Web Projects.
h1. Preface
Eclipse offers nice tools to create web applications. The base framework's what we call the Eclipse Web Tools Platform (WTP). Eclipse WTP delivers a standard for most aspects involved when you create web applications.
The google web toolkit, GWT, is a nice framework to develop web applications. Google delivers a plugin for Eclipse and developing with GWT is a very pleasant experience. The GWT plugin uses an embedded jetty to run the application that you develop. Google unfortunately did not base its work on Eclipse WTP and does not comply to the Eclipse project structure for web application. So if you want to use JBoss instead of jetty, the approach to take is not as handy and intuitive as it could be. Furthermore there's no way to use and integrate into plugins that other solution providers offer. You mostly have to proceed by workarounds to get what Google does not offer.
We developed a set of (experimental) plugins that create GWT projects by extending Eclipse WTP. Our plugins implement well known usage patterns and integrate well with all Eclipse components that use the common standard for web projects. The most obvious benefit is that deploying to JEE application servers (and JBoss partcullarly) is as easy as it is with any other web project.
h1. Solution
Install and use the JBoss GWT Integration. You'll then be able to create GWT projects the WTP way and fully enjoy it's full-blow features and standardized usage patterns.
This How-To shows you all the steps to install the plugins and how to create a dynamic web project that's GWT enabled.
h2. Install Google Plugin for Eclipse
Add the Google update site
> http://dl.google.com/eclipse/plugin/3.6 http://dl.google.com/eclipse/plugin/3.6
And Install the Google Plugin for Eclipse 3.6 and the GWT SDK.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-161... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
h2. Install JBoss GWT Integration
Add the JBoss Tools 3.2.x update site:
> http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/ http://download.jboss.org/jbosstools/updates/nightly/3.2_stable_branch/
And Install the JBoss GWT Integration
http://community.jboss.org/servlet/JiveServlet/showImage/6254/Picture+4.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6254/Picture...
h2. Create a Dynamic Web Application Project
Make sure you have a JEE server (JBoss application server for instance) in your Eclipse environment. If not, download and declare it to your Eclipse IDE:
http://community.jboss.org/servlet/JiveServlet/showImage/6260/Picture+12.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6260/Picture...
http://community.jboss.org/servlet/JiveServlet/showImage/6259/Picture+11.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6259/Picture...
You're now ready to create a *Dynamic Web Project*.
http://community.jboss.org/servlet/JiveServlet/showImage/6256/Picture+5.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6256/Picture...
The wizard picks your server (runtime) and allows you to configure the various characteristic of your web project.
The *configuration* group allows you to pick the different facets of your project. We provide a *Google Web Toolkit* facet that will configure the GWT related characteristics.
Hit *Modify...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
and select the *Google Web Toolkit* facet.
http://community.jboss.org/servlet/JiveServlet/showImage/6262/Picture+14.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6262/Picture...
A few wizard steps further, you may choose to get some GWT *sample code*.
http://community.jboss.org/servlet/JiveServlet/showImage/6411/generate-sa... http://community.jboss.org/servlet/JiveServlet/downloadImage/6411/generat...
You get the Hello World sample that you get when you use the Google Wizard. We just put it to the *WebContent* folder you configured in your Dynamic Web Project wizard (WTP default opposed to what Google does in their plugin). The sample's a fully working GWT application that allows you to get a first impression of what developing with GWT looks like.
h1. Cross compile to Javascript
GWT is about programming in Java and getting javascript for the browser. GWT achieves this with a cross-compiler that creates the javascript for you.
In order to get the project up and running you now need to cross compile the sample's client java code to javascript. Our project has the *GWT nature* and therefore offers the Google compiler in the context menu.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
h1. Deploy to JBoss
We are now ready to deploy our application. We strictly use the standard Eclipse *WTP* infrastructure in our setup, So you may deploy your GWT application in the same manner you usually deploy and run classic web applications with Eclipse WTP. You have to add the application to a server that's registered in the WTP *servers view*. We deploy our application to our JBoss application server by selecting it in the and choosing *Add and Remove...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
You can now add the GWT application to your server. WTP will make sure that it gets deployed and the deployed artifacts are in sync with your workspace (even when you change code, resources, configurations, etc.)
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
h1. Run your application and launch your browser
You may now run your application. We completely comply to the views and steps Eclipse WTP offers to web developers. So there's no custom way to start a server in our setup. We select our JBoss instance in the *Servers view* and *start* it.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
You can now point your browser to the address and port that your JBoss server's bound to.
http://community.jboss.org/servlet/JiveServlet/showImage/6271/Picture+2.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6271/Picture...
h2. Speed up my development cycle!
The approach we've choosen so far uses an extra cross compile step to deploy the application after each change. That's very reliable but it gets tedious at development time. Google delivers a so called hosted/development mode. Its major benefit is that you dont need to cross compile on each change but you can change and test on the fly. This magic is achieved with a browser plugin and a google runtime that interprets your java code at runtime. Changing, testing, changing, testing etc. gets much faster and pleasant, the cross-compilation step's not needed any more.
h2. Launch GWT Codeserver
If you launch your application as Google Web Application, you'll be able to code and test on the fly. The GWT browser plugin will communicate with the GWT code server and execute your changes on the fly.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
You need to tell the browser plugin where your code server may be reached. You do that by using an *additional url parameter*. Your browser URL now reads as follows:
> http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997
Point your browser to this URL and you'll get the same page as before, nothing spectacular so far.
Now get back to your client code and change the button label, to see if changes are picked on the fly now.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
Do not cross-compile, get back to your browser and reload. What you see reflects the changes in your code. You don't need to cross compile to develop your app!
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-21-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-21...
To be picky on the issue you could now go to the launch configuration and disable the jetty google usually uses to serve your GWT application:
http://community.jboss.org/servlet/JiveServlet/showImage/6413/disable-bui... http://community.jboss.org/servlet/JiveServlet/downloadImage/6413/disable...
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15794]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 11 months
