EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature pack - Websphere

This is a discussion on EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature pack - Websphere ; Hi, I'm trying to migrate an EJB application from WAS 6.0 to WAS 6.1.0.15 with EJB3 service pack. Interestingly, what I found was, I could deploy the application on WAS 6.1.0.15 as long as EJB3 service pack is not installed ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature pack

  1. EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature pack

    Hi,



    I'm trying to migrate an EJB application from WAS 6.0 to WAS 6.1.0.15 with EJB3 service pack. Interestingly, what I found was, I could deploy the application on WAS 6.1.0.15 as long as EJB3 service pack is not installed on it. The moment I install EJB3 service pack on the server, application deployment is failing with one of the following exceptions com.ibm.websphere.naming.CannotInstantiateObjectEx ception or DuplicateHomeNameException.



    Did anyone come across this problem and found any resolution for the same?



    Thanks in advance,

    Chandra.

  2. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature p

    Hi, it would be more helpful to post which platform this is occurring and the actual log entries.



    Regards,

    Brian

  3. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature pack

    Offhand, I'd suggest checking for a corrupted installation or similar issues. 6.1.0.17 was recently released and customers have been successfully running the EJB 3.0 feature pack on 6.1.0.15 prior to this.

    Randy

    chandrasekhares@gmail.com wrote:
    > Hi,
    >
    >
    >
    > I'm trying to migrate an EJB application from WAS 6.0 to WAS 6.1.0.15 with EJB3 service pack. Interestingly, what I found was, I could deploy the application on WAS 6.1.0.15 as long as EJB3 service pack is not installed on it. The moment I install EJB3 service pack on the server, application deployment is failing with one of the following exceptions com.ibm.websphere.naming.CannotInstantiateObjectEx ception or DuplicateHomeNameException.
    >
    >
    >
    > Did anyone come across this problem and found any resolution for the same?
    >
    >
    >
    > Thanks in advance,
    >
    > Chandra.


  4. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature p

    Hi,

    I'm using Windows XP Operating System.

    Please have a look the stack trace below (with EJB3 feature pack is installed), and share your thoughts!!!



    6/12/08 17:51:44:814 IST 0000001b Helpers W NMSV0612W: A NameNotFoundException occurred on an indirect lookup on the name "java:comp/env/ejb/RulesEngine/MainController". The name "java:comp/env/ejb/RulesEngine/MainController" maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context. NameNotFoundException data follows:

    javax.naming.NameNotFoundException: Name "ejb/de/tcom/blw/resaledsl/controller/MainControllerLocalHome" not found in context "ejblocal:".

    at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal( NameSpace.java:1095)

    at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpac e.java:991)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1263)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1255)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1307)

    at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt( CNContextImpl.java:1558)

    at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory$1.run(IndirectJndiLookup ObjectFactory.java:374)

    at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:11 8)

    at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory.getObjectInstanceExt(Ind irectJndiLookupObjectFactory.java:224)

    at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :914)

    at com.ibm.ws.naming.urlbase.UrlContextHelper.process BoundObjectForLookup(UrlConte xtHelper.java:191)

    at com.ibm.ws.naming.java.javaURLContextRoot.processB oundObjectForLookup(javaURLCo ntextRoot.java:407)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1280)

    at com.ibm.ws.naming.java.javaURLContextImpl.lookup(j avaURLContextImpl.java:384)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:204)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:144)
    at javax.naming.InitialContext.lookup(InitialContext. java:363)

    at de.tcom.blw.resaledsl.util.ServiceLocator.getEJBHo me(ServiceLocator.java:66)

    at de.tcom.blw.resaledsl.controller.message.AbstractC onsumer. (AbstractConsum er.java:92)

    at de.tcom.blw.resaledsl.controller.message.FPConsume rBean. (FPConsumerBean.j ava:22)

    at java.lang.Class.newInstanceImpl(Native Method)

    at java.lang.Class.newInstance(Class.java:1300)

    at com.ibm.ejs.container.EJSContainer.loadBeanMetaDat a(EJSContainer.java:1675)

    at com.ibm.ejs.container.HomeOfHomes.loadBeanMetaData (HomeOfHomes.java:1073)

    at com.ibm.ejs.container.HomeRecord.getHomeAndInitial ize(HomeRecord.java:453)

    at com.ibm.ejs.container.EJSContainer.getHomeWrapperC ommon(EJSContainer.java:1315)

    at com.ibm.ejs.container.EJSContainer.getHomeInstance (EJSContainer.java:1224)

    at com.ibm.ejs.container.EJSContainer.startBean(EJSCo ntainer.java:1210)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star tBean(EJBContainerImpl.java:3 359)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star tModule(EJBContainerImpl.java :2567)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star t(EJBContainerImpl.java:3693)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl.st art(ApplicationMgrImpl.java:1 304)

    at com.ibm.ws.runtime.component.DeployedApplicationIm pl.fireDeployedObjectStart(De ployedApplicationImpl.java:1165)

    at com.ibm.ws.runtime.component.DeployedModuleImpl.st art(DeployedModuleImpl.java:5 87)

    at com.ibm.ws.runtime.component.DeployedApplicationIm pl.start(DeployedApplicationI mpl.java:832)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl.st artApplication(ApplicationMgr Impl.java:950)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl$Ap pInitializer.run(ApplicationM grImpl.java:2131)

    at com.ibm.wsspi.runtime.component.WsComponentImpl$_A synchInitializer.run(WsCompon entImpl.java:342)

    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)



    6/12/08 17:51:44:845 IST 0000001b Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:

    Context implementation: com.ibm.ws.naming.java.javaURLContextRoot

    Context method: lookup(Name)

    Context name: java:

    Target name: comp/env/ejb/RulesEngine/MainController

    Other data: ""

    Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectEx ception: A NameNotFoundException occurred on an indirect lookup on the name java:comp/env/ejb/RulesEngine/MainController. The name java:comp/env/ejb/RulesEngine/MainController maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context.

    at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :1003)

    at com.ibm.ws.naming.urlbase.UrlContextHelper.process BoundObjectForLookup(UrlConte xtHelper.java:191)

    at com.ibm.ws.naming.java.javaURLContextRoot.processB oundObjectForLookup(javaURLCo ntextRoot.java:407)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1280)

    at com.ibm.ws.naming.java.javaURLContextImpl.lookup(j avaURLContextImpl.java:384)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:204)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:144)
    at javax.naming.InitialContext.lookup(InitialContext. java:363)

    at de.tcom.blw.resaledsl.util.ServiceLocator.getEJBHo me(ServiceLocator.java:66)

    at de.tcom.blw.resaledsl.controller.message.AbstractC onsumer. (AbstractConsum er.java:92)

    at de.tcom.blw.resaledsl.controller.message.FPConsume rBean.(FPConsumerBean.j ava:22)

    at java.lang.Class.newInstanceImpl(Native Method)

    at java.lang.Class.newInstance(Class.java:1300)

    at com.ibm.ejs.container.EJSContainer.loadBeanMetaDat a(EJSContainer.java:1675)

    at com.ibm.ejs.container.HomeOfHomes.loadBeanMetaData (HomeOfHomes.java:1073)

    at com.ibm.ejs.container.HomeRecord.getHomeAndInitial ize(HomeRecord.java:453)

    at com.ibm.ejs.container.EJSContainer.getHomeWrapperC ommon(EJSContainer.java:1315)

    at com.ibm.ejs.container.EJSContainer.getHomeInstance (EJSContainer.java:1224)

    at com.ibm.ejs.container.EJSContainer.startBean(EJSCo ntainer.java:1210)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star tBean(EJBContainerImpl.java:3 359)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star tModule(EJBContainerImpl.java :2567)

    at com.ibm.ws.runtime.component.EJBContainerImpl.star t(EJBContainerImpl.java:3693)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl.st art(ApplicationMgrImpl.java:1 304)

    at com.ibm.ws.runtime.component.DeployedApplicationIm pl.fireDeployedObjectStart(De ployedApplicationImpl.java:1165)

    at com.ibm.ws.runtime.component.DeployedModuleImpl.st art(DeployedModuleImpl.java:5 87)

    at com.ibm.ws.runtime.component.DeployedApplicationIm pl.start(DeployedApplicationI mpl.java:832)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl.st artApplication(ApplicationMgr Impl.java:950)

    at com.ibm.ws.runtime.component.ApplicationMgrImpl$Ap pInitializer.run(ApplicationM grImpl.java:2131)

    at com.ibm.wsspi.runtime.component.WsComponentImpl$_A synchInitializer.run(WsCompon entImpl.java:342)

    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)

    Caused by: javax.naming.NameNotFoundException: Name "ejb/de/tcom/blw/resaledsl/controller/MainControllerLocalHome" not found in context "ejblocal:".

    at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal( NameSpace.java:1095)

    at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpac e.java:991)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1263)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1255)

    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1307)

    at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt( CNContextImpl.java:1558)

    at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory$1.run(IndirectJndiLookup ObjectFactory.java:374)

    at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:11 8)

    at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory.getObjectInstanceExt(Ind irectJndiLookupObjectFactory.java:224)

    at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :914)

    ... 29 more

  5. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature p

    Hi,
    From you're scenario, I'm gathering that you have an ejb-local-ref that you've named "ejb/RulesEngine/MainController", which you would like to be linked to a bean named "ejb/de/tcom/blw/resaledsl/controller/MainControllerLocalHome".

    If it would be OK, could you post the text of the following files from your EJB2 module that contains the ejb-local-ref (please post the actual contents rather than attaching the files):

    META-INF/ejb.jar.xml
    META-INF/ibm-ejb-jar-bnd.xmi

    and also, could you locate and post all the CNTR0167I messages in your SystemOut.log file from when you started the server (you may want to clear the file, then start the server again to get rid of old log entries). The CNTR0167I messages will indicate where the EJB container is binding each EJB home and EJB3 business interface (from your scenario I expect there will not be any EJB3 business interfaces, just homes).

    This will help in figuring out what the problem might be. You may also want to open a PMR with IBM Support. But if you can post the info here, it might help us determine if it's a misconfiguration in your files vs. a bug in WAS.

    Thanks, Randy

    chandrasekhares@gmail.com wrote:
    > Hi,
    >
    > I'm using Windows XP Operating System.
    >
    > Please have a look the stack trace below (with EJB3 feature pack is installed), and share your thoughts!!!
    >
    >
    >
    > 6/12/08 17:51:44:814 IST 0000001b Helpers W NMSV0612W: A NameNotFoundException occurred on an indirect lookup on the name "java:comp/env/ejb/RulesEngine/MainController". The name "java:comp/env/ejb/RulesEngine/MainController" maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context. NameNotFoundException data follows:
    >
    > javax.naming.NameNotFoundException: Name "ejb/de/tcom/blw/resaledsl/controller/MainControllerLocalHome" not found in context "ejblocal:".
    >
    > at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal( NameSpace.java:1095)
    >
    > at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpac e.java:991)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1263)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1255)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1307)
    >
    > at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt( CNContextImpl.java:1558)
    >
    > at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory$1.run(IndirectJndiLookup ObjectFactory.java:374)
    >
    > at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:11 8)
    >
    > at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory.getObjectInstanceExt(Ind irectJndiLookupObjectFactory.java:224)
    >
    > at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :914)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextHelper.process BoundObjectForLookup(UrlConte xtHelper.java:191)
    >
    > at com.ibm.ws.naming.java.javaURLContextRoot.processB oundObjectForLookup(javaURLCo ntextRoot.java:407)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1280)
    >
    > at com.ibm.ws.naming.java.javaURLContextImpl.lookup(j avaURLContextImpl.java:384)
    > at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:204)
    > at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:144)
    > at javax.naming.InitialContext.lookup(InitialContext. java:363)
    >
    > at de.tcom.blw.resaledsl.util.ServiceLocator.getEJBHo me(ServiceLocator.java:66)
    >
    > at de.tcom.blw.resaledsl.controller.message.AbstractC onsumer. (AbstractConsum er.java:92)
    >
    > at de.tcom.blw.resaledsl.controller.message.FPConsume rBean. (FPConsumerBean.j ava:22)
    >
    > at java.lang.Class.newInstanceImpl(Native Method)
    >
    > at java.lang.Class.newInstance(Class.java:1300)
    >
    > at com.ibm.ejs.container.EJSContainer.loadBeanMetaDat a(EJSContainer.java:1675)
    >
    > at com.ibm.ejs.container.HomeOfHomes.loadBeanMetaData (HomeOfHomes.java:1073)
    >
    > at com.ibm.ejs.container.HomeRecord.getHomeAndInitial ize(HomeRecord.java:453)
    >
    > at com.ibm.ejs.container.EJSContainer.getHomeWrapperC ommon(EJSContainer.java:1315)
    >
    > at com.ibm.ejs.container.EJSContainer.getHomeInstance (EJSContainer.java:1224)
    >
    > at com.ibm.ejs.container.EJSContainer.startBean(EJSCo ntainer.java:1210)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star tBean(EJBContainerImpl.java:3 359)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star tModule(EJBContainerImpl.java :2567)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star t(EJBContainerImpl.java:3693)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl.st art(ApplicationMgrImpl.java:1 304)
    >
    > at com.ibm.ws.runtime.component.DeployedApplicationIm pl.fireDeployedObjectStart(De ployedApplicationImpl.java:1165)
    >
    > at com.ibm.ws.runtime.component.DeployedModuleImpl.st art(DeployedModuleImpl.java:5 87)
    >
    > at com.ibm.ws.runtime.component.DeployedApplicationIm pl.start(DeployedApplicationI mpl.java:832)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl.st artApplication(ApplicationMgr Impl.java:950)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl$Ap pInitializer.run(ApplicationM grImpl.java:2131)
    >
    > at com.ibm.wsspi.runtime.component.WsComponentImpl$_A synchInitializer.run(WsCompon entImpl.java:342)
    >
    > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)
    >
    >
    >
    > 6/12/08 17:51:44:845 IST 0000001b Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
    >
    > Context implementation: com.ibm.ws.naming.java.javaURLContextRoot
    >
    > Context method: lookup(Name)
    >
    > Context name: java:
    >
    > Target name: comp/env/ejb/RulesEngine/MainController
    >
    > Other data: ""
    >
    > Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectEx ception: A NameNotFoundException occurred on an indirect lookup on the name java:comp/env/ejb/RulesEngine/MainController. The name java:comp/env/ejb/RulesEngine/MainController maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context.
    >
    > at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :1003)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextHelper.process BoundObjectForLookup(UrlConte xtHelper.java:191)
    >
    > at com.ibm.ws.naming.java.javaURLContextRoot.processB oundObjectForLookup(javaURLCo ntextRoot.java:407)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1280)
    >
    > at com.ibm.ws.naming.java.javaURLContextImpl.lookup(j avaURLContextImpl.java:384)
    > at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:204)
    > at com.ibm.ws.naming.java.javaURLContextRoot.lookup(j avaURLContextRoot.java:144)
    > at javax.naming.InitialContext.lookup(InitialContext. java:363)
    >
    > at de.tcom.blw.resaledsl.util.ServiceLocator.getEJBHo me(ServiceLocator.java:66)
    >
    > at de.tcom.blw.resaledsl.controller.message.AbstractC onsumer. (AbstractConsum er.java:92)
    >
    > at de.tcom.blw.resaledsl.controller.message.FPConsume rBean.(FPConsumerBean.j ava:22)
    >
    > at java.lang.Class.newInstanceImpl(Native Method)
    >
    > at java.lang.Class.newInstance(Class.java:1300)
    >
    > at com.ibm.ejs.container.EJSContainer.loadBeanMetaDat a(EJSContainer.java:1675)
    >
    > at com.ibm.ejs.container.HomeOfHomes.loadBeanMetaData (HomeOfHomes.java:1073)
    >
    > at com.ibm.ejs.container.HomeRecord.getHomeAndInitial ize(HomeRecord.java:453)
    >
    > at com.ibm.ejs.container.EJSContainer.getHomeWrapperC ommon(EJSContainer.java:1315)
    >
    > at com.ibm.ejs.container.EJSContainer.getHomeInstance (EJSContainer.java:1224)
    >
    > at com.ibm.ejs.container.EJSContainer.startBean(EJSCo ntainer.java:1210)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star tBean(EJBContainerImpl.java:3 359)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star tModule(EJBContainerImpl.java :2567)
    >
    > at com.ibm.ws.runtime.component.EJBContainerImpl.star t(EJBContainerImpl.java:3693)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl.st art(ApplicationMgrImpl.java:1 304)
    >
    > at com.ibm.ws.runtime.component.DeployedApplicationIm pl.fireDeployedObjectStart(De ployedApplicationImpl.java:1165)
    >
    > at com.ibm.ws.runtime.component.DeployedModuleImpl.st art(DeployedModuleImpl.java:5 87)
    >
    > at com.ibm.ws.runtime.component.DeployedApplicationIm pl.start(DeployedApplicationI mpl.java:832)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl.st artApplication(ApplicationMgr Impl.java:950)
    >
    > at com.ibm.ws.runtime.component.ApplicationMgrImpl$Ap pInitializer.run(ApplicationM grImpl.java:2131)
    >
    > at com.ibm.wsspi.runtime.component.WsComponentImpl$_A synchInitializer.run(WsCompon entImpl.java:342)
    >
    > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)
    >
    > Caused by: javax.naming.NameNotFoundException: Name "ejb/de/tcom/blw/resaledsl/controller/MainControllerLocalHome" not found in context "ejblocal:".
    >
    > at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal( NameSpace.java:1095)
    >
    > at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpac e.java:991)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1263)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1255)
    >
    > at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(Ur lContextImpl.java:1307)
    >
    > at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt( CNContextImpl.java:1558)
    >
    > at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory$1.run(IndirectJndiLookup ObjectFactory.java:374)
    >
    > at com.ibm.ws.security.util.AccessController.doPrivil eged(AccessController.java:11 8)
    >
    > at com.ibm.ws.naming.util.IndirectJndiLookupObjectFac tory.getObjectInstanceExt(Ind irectJndiLookupObjectFactory.java:224)
    >
    > at com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java :914)
    >
    > ... 29 more


  6. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3feature p

    Sorry, previous posting had a typo. The first filename should be META-INF/ejb-jar.xml, not ejb.jar.xml.

    Randy Schnier wrote:
    >
    > META-INF/ejb.jar.xml
    > META-INF/ibm-ejb-jar-bnd.xmi
    >


  7. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3

    Hi,



    Thanks for your reply. Your understanding about local references are absolutely correct. As you said, as of now we do not have any EJB3 business interfaces in the application.



    As requested by you I'm adding the contents of ejb-jar.xml, ibm-ejb-jar-bnd.xmi and CNTR0167I messages from SystemOut.log file here.



    ejb-jar.xml





    BLWController


    EntryConsumer
    de.tcom.blw.resaledsl.controller.message.EntryCons umerBean
    Container
    javax.jms.Queue


    acknowledgeMode
    Auto-acknowledge


    destinationType
    javax.jms.Queue


    subscriptionDurability
    Durable



    ejb/PersistenceFacade/CommonServices
    Session
    de.tcom.blw.resaledsl.persistence.facade.interface s.PersistenceFaca deLocalHome
    de.tcom.blw.resaledsl.persistence.facade.interface s.PersistenceFacadeLoc al
    Persistence_Facade.jar#CommonServices


    ejb/RulesEngine/MainController
    Session
    de.tcom.blw.resaledsl.controller.MainControllerLoc alHome
    de.tcom.blw.resaledsl.controller.MainControllerLoc al
    MainController


  8. Re: EJB2 Application deployment failing on WAS 6.1.0.15 with EJB3

    Hi Randy,



    please find the attachment in my previous post for all the information that you have requested. I had also pasted all the contents in my earlier reply, however after it got posted most of the contents related to xml is getting disappeared



    Best regards,

    Chandra.

+ Reply to Thread