@Ejb is not supported in weblogic 12.2.x

ZeroTurnaround Homepage Forums JRebel Support @Ejb is not supported in weblogic 12.2.x

This topic contains 1 reply, has 2 voices, and was last updated by  eresh.gorantla 1 year, 6 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #58045

    Hi
    Recently we have migrated our application to Wl 1221. Initially faced an issue of bootstrap issue with weblogic . After looking in to change logs I came to know that jebel needs upgrade to 6.4.3 .

    I upgraded to that version and application failed in EJB where ever @EJB used in SSB.
    If jrebel is turned off it worked fine.

    In previous version of jrebel 6.1.2 and weblogic 12.1.3 the application started successfully. Due to bootstrap issue in weblogic 122x jrebel is upgraded to 6.4.3.

    Please provide some pointers to overcome this issue.

    Error stack trace.

    
    <Failure occu
    rred in the execution of deployment request with ID "17400702877054" for task "0
    " on [partition-name: DOMAIN]. Error is: "weblogic.management.DeploymentExceptio
    n: weblogic.application.naming.ReferenceResolutionException: [J2EE:160199]Error
    resolving ejb-ref "com.sample.app.CardProdMgmtApiSSB/tra
    nsitEntityMgr" from module "nbmsEjb.jar" of application "nbms". The ejb-ref does
     not have an ejb-link and the JNDI name of the target Bean has not been specifie
    d."
    weblogic.management.DeploymentException: weblogic.application.naming.ReferenceRe
    solutionException: [J2EE:160199]Error resolving ejb-ref "com.cubic.ncs.webservic
    es.cardprodmgmt.CardProdMgmtApiSSB/transitEntityMgr" from module "nbmsEjb.jar" o
    f application "nbms". The ejb-ref does not have an ejb-link and the JNDI name of
     the target Bean has not been specified.
            at weblogic.application.internal.flow.ReferenceResolutionFlow.resolveRef
    erences(ReferenceResolutionFlow.java:42)
            at weblogic.application.internal.flow.ReferenceResolutionFlow.prepare(Re
    ferenceResolutionFlow.java:31)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
    va:731)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:45)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
    ava:243)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.application.naming.ReferenceResolutionException: [J2EE:16019
    9]Error resolving ejb-ref "com.sample.app.CardProdMgmtAp
    iSSB/transitEntityMgr" from module "nbmsEjb.jar" of application "nbms". The ejb-
    ref does not have an ejb-link and the JNDI name of the target Bean has not been
    specified.
            at weblogic.application.naming.EnvUtils.findInfo(EnvUtils.java:758)
            at weblogic.application.naming.EnvUtils.findInfoByReferenceClass(EnvUtil
    s.java:691)
            at weblogic.application.naming.EjbReferenceResolver.resolveEjbRef(EjbRef
    erenceResolver.java:90)
            at weblogic.application.naming.EjbReferenceResolver.resolve(EjbReference
    Resolver.java:74)
            at weblogic.application.internal.flow.ReferenceResolutionFlow.resolveRef
    erences(ReferenceResolutionFlow.java:40)
            Truncated. see log file for complete stacktrace
    >
    <Jul 13, 2016, 4:33:19,916 PM IST> <Warning> <Deployer> <BEA-149004> <Failures w
    ere detected while initiating deploy task for application "nbms".>
    <Jul 13, 2016, 4:33:19,916 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trac
    e for message 149004
    weblogic.management.DeploymentException: weblogic.application.naming.ReferenceRe
    solutionException: [J2EE:160199]Error resolving ejb-ref "com.sample.app.CardProdMgmtApiSSB/transitEntityMgr" from module "nbmsEjb.jar" o
    f application "nbms". The ejb-ref does not have an ejb-link and the JNDI name of
     the target Bean has not been specified.
            at weblogic.application.internal.flow.ReferenceResolutionFlow.resolveRef
    erences(ReferenceResolutionFlow.java:42)
            at weblogic.application.internal.flow.ReferenceResolutionFlow.prepare(Re
    ferenceResolutionFlow.java:31)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
    va:731)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:45)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
    ava:243)
            Truncated. see log file for complete stacktrace
    Caused By: weblogic.application.naming.ReferenceResolutionException: [J2EE:16019
    9]Error resolving ejb-ref "com.sample.app.CardProdMgmtAp
    iSSB/transitEntityMgr" from module "nbmsEjb.jar" of application "nbms". The ejb-
    ref does not have an ejb-link and the JNDI name of the target Bean has not been
    specified.
            at weblogic.application.naming.EnvUtils.findInfo(EnvUtils.java:758)
            at weblogic.application.naming.EnvUtils.findInfoByReferenceClass(EnvUtil
    s.java:691)
            at weblogic.application.naming.EjbReferenceResolver.resolveEjbRef(EjbRef
    erenceResolver.java:90)
            at weblogic.application.naming.EjbReferenceResolver.resolve(EjbReference
    Resolver.java:74)
            at weblogic.application.internal.flow.ReferenceResolutionFlow.resolveRef
    erences(ReferenceResolutionFlow.java:40)
            Truncated. see log file for complete stacktrace
    >
    #58048

    test

    #58049

    Valerie Avramenko
    Rebel Staff

    Hello Eresh!

    Thanks a lot for the error stack trace! Do you use 6.4.3 or 6.4.6 version of JRebel now?

    Could you please send your trace level jrebel.log files from the new version after reproducing the issue to support@zeroturnaround.com with the link to this forum topic? To generate it just add -Drebel.log=trace to your VM arguments, restart your server and reproduce the issue. The file should be in your .jrebelfolder.

    Please also specify what is your environment – what IDE, server (local or remote?), any additional software and its version do you use?

    Kind regards,
    Valerie

    #58055

    Thanks for the reply. You mean need to send jrebel.log to email support@zeroturnaround.com by providing link of this topic in the email?

    #58057

    Hi ,
    I have forwarded the trace log to your mailbox. Please have a look.
    we have jrebel licence.
    Yes, I also tried with 6.4.6 version as well and got the same error.
    Server : weblogic 12.2.1.1 (local from console)
    Environment : windows 7
    Java : jdk 8.
    Jrebel version : 6.4.6

    regards
    Eresh

    #58068

    HI Jrebel team,
    Any update?

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.