[jboss-jira] [JBoss JIRA] (WFLY-9399) EJB remote and local methods are not calling through Threads

[David Lloyd (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd closed WFLY-9399.
-----------------------------
    Resolution: Rejected


This is not a help forum, this is a bug tracker.  If you are looking for help, try this link: [http://wildfly.org/gethelp/]

> EJB remote and local methods are not calling through Threads
> ------------------------------------------------------------
>
>                 Key: WFLY-9399
>                 URL: https://issues.jboss.org/browse/WFLY-9399
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EJB
>    Affects Versions: 9.0.2.Final
>            Reporter: Karthika Udayasankar
>            Priority: Blocker
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Hi,
> We are migrated from JBoss 5.1 to WildFly 9.0.2. After migrating I'm facing exception while calling EJB methods when it is coming through *Thread* concept otherwise it is working fine. 
> 2017-09-28 16:03:38,981 ERROR [SIRAHULOG] (Thread-149) Thread ID:398:EjbUtils:getEJBInstance:Exception raised for name:java:app/app-model-1.0-SNAPSHOT/FirmBaseEJB!com.sirahu.apptivo.model.ejb.common.session.FirmBaseEJBRemote: javax.naming.NameNotFoundException: java:app/app-model-1.0-SNAPSHOT/FirmBaseEJB!com.sirahu.apptivo.model.ejb.common.session.FirmBaseEJBRemote
> 	at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:189)
> 	at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:411)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:411)
> 	at com.sirahu.apptivo.view.framework.util.EjbUtils.getEJBInstance(EjbUtils.java:563)
> 	at com.sirahu.apptivo.view.framework.util.EjbUtils.getEjb(EjbUtils.java:498)
> 	at com.sirahu.apptivo.view.framework.util.EjbUtils.getRemoteEjb(EjbUtils.java:527)
> 	at com.sirahu.apptivo.view.framework.util.EjbUtils.getFirmOrCFRemoteEjb(EjbUtils.java:535)
> 	at com.sirahu.apptivo.view.framework.util.AppClusterEJBFactory.getFirmBaseEJBRemote(AppClusterEJBFactory.java:1105)
> 	at com.sirahu.apptivo.view.dao.service.BusinessAttributeService.getBusinessAtrributeMap(BusinessAttributeService.java:52)
> 	at com.sirahu.apptivo.view.action.common.MessageTemplateCommonService.getObjectMessageTemplateMap(MessageTemplateCommonService.java:124)
> 	at com.sirahu.apptivo.view.dao.service.MessageTemplateService.processMessageTemplate(MessageTemplateService.java:3033)
> 	at com.sirahu.apptivo.view.dao.service.MessageTemplateService.replaceMessageTemplate(MessageTemplateService.java:340)
> 	at com.sirahu.apptivo.view.dao.service.MessageTemplateService.replaceMessageTemplate(MessageTemplateService.java:167)
> 	at com.sirahu.apptivo.view.dao.servlet.v6.UpdateEmployeeSignatureThread.run(EmployeesServlet.java:7012)
> 	at java.lang.Thread.run(Thread.java:745)
> Is there anything need to config for Thread concepts.? Can anybody help me to fix this issue?
>  



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)