Unable to resolve 'app/ejb/Common.jar#SequenceInstrument'

I have developed a module with weblogic6.1 , but when I migrate it to weblogic
7 ,it alway appears errors as following.
I have build with weblogic 7 for many times , but nothing change , please help
me.
------error info ----
weblogic.management.ApplicationException: Prepare failed. Task Id = 7
Module Name: Common, Error: Exception while rollback of module : EJBModule(Common,status=NEW)
Common.jar; nested exception is:
     javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/Common.jar#SequenceInstrument'
Resolved: 'app/ejb' Unresolved:'Common.jar#SequenceInstrument' ; remaining name
'Common.jar#SequenceInstrument'
TargetException: weblogic.ejb20.UnDeploymentException: Common.jar; nested exception
is:
     javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/Common.jar#SequenceInstrument'
Resolved: 'app/ejb' Unresolved:'Common.jar#SequenceInstrument' ; remaining name
'Common.jar#SequenceInstrument'
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:661)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:552)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

Hello Sanjay,
This should work without any problems. Can you provide your manifest.mf file?
Meanwhile, refer to the following link for more documentation about WebLogic classloading
and how to specify a manifest.mf file to do what you're trying to achieve:
http://edocs.bea.com/wls/docs70/programming/classloading.html#1073491
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Sanjay <[email protected]> wrote:
Hi,
I have an .ear file which as an ejb.jar and dependent.jar file. Now
i set the classpath in MANIFEST.MF of ejb.jar and tried to deploy in
weblogic server7.0 but my ejb is not able to identity my dependent.jar
its throwing class not found error. I even tried setting up classpath
even @ my MANIFEST.MF of ear also. still not able to resolve.
So let me know does dependent.jar in ear is suppoted are not?

Similar Messages

  • Unable to resolve setting of dependent jar file in ear

    Hi,
    I have an .ear file which as an ejb.jar and dependent.jar file. Now i set the classpath in MANIFEST.MF of ejb.jar and tried to deploy in weblogic server7.0 but my ejb is not able to identity my dependent.jar its throwing class not found error. I even tried setting up classpath even @ my MANIFEST.MF of ear also. still not able to resolve.
    So let me know does dependent.jar in ear is suppoted are not?

    Hello Sanjay,
    This should work without any problems. Can you provide your manifest.mf file?
    Meanwhile, refer to the following link for more documentation about WebLogic classloading
    and how to specify a manifest.mf file to do what you're trying to achieve:
    http://edocs.bea.com/wls/docs70/programming/classloading.html#1073491
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    Sanjay <[email protected]> wrote:
    Hi,
    I have an .ear file which as an ejb.jar and dependent.jar file. Now
    i set the classpath in MANIFEST.MF of ejb.jar and tried to deploy in
    weblogic server7.0 but my ejb is not able to identity my dependent.jar
    its throwing class not found error. I even tried setting up classpath
    even @ my MANIFEST.MF of ear also. still not able to resolve.
    So let me know does dependent.jar in ear is suppoted are not?

  • Common JAR file between EJB and WAR inside an EAR

    Hi,
    I'm trying to deploy an EAR application outside the development environment and I have the following problem.
    My EAR has the following structure :
    application.ear
    |-- ejbs.jar
    |-- web.war
    Inside the WAR, in /WEB-INF/lib/, I have a set of JAR files that are used by the Web app and also, of course, by the EJB.
    During the deployment step, EJB module cannot be deployed because it miss some classes into the classpath.
    I think it is a common problem in J2EE development, so does someone has a solution for this problem ?
    Please note I'm using Macromedia JRun 4 SP1 on Windows XP.
    Regards,
    Damien.

    Ok,
    I have found a solution that seems elegant to me. I'm going to try and explain...
    My appli.jar EJB module and my appli.war Web module are using both two JAR, let's say common.jar and util.jar.
    The way to share those JAR between the two modules is to have the following structure for the EAR :
    appli.ear
      |-- appli.jar
      |-- appli.war
      |-- common.jar
      |-- util.jar
      |-- META-INF
           |-- application.xml
           |-- manifest.mfIn this structure :
    * the common.jar and the util.jar are not part of the WAR (/web-inf/lib)
    * the manifest.mf file has the following content :
    Manifest-Version: 1.0
    Created-By: My Application
    Class-Path: common.jar util.jarPlease note that space is used as separator for the classpath entry to allow independancy from OS.
    And you know what ? It works ! Well, on Macromedia JRun 4.0 SP1 and on Windows XP but I hope it works on other platforms.
    I hope it will help a lot of people because I spent a lot of time before to find a solution !
    Regards,
    Damien.

  • URL Portal error: Unable to resolve comp/env/ejb/URIManager/

    I am attempting to creat a URL portal using the Web Service Portlet Wizard.
    The Wizard seems to build the jsp fine, but I get the following error in the
    portlet when I try to bring it up:
    Error retrieving page at http://www.bloomberg.com/index.html Exception:
    Unable to resolve comp/env/ejb/URIManager/ Resolved: 'comp/env/ejb'
    Unresolved:'URIManager'
    I can't even find this path in my installation, nor any reference to
    URIManager. Am I missing a class somewhere? (Note: I have all this
    installed on my laptop for testing, and am not currently working off our
    main development server.)
    Thanks for your help.
    - JKL

    JKL,
    I have not used the Portlet Wizard, so I can't answer your question specifically.
    But I can help direct you on where to look.
    There should be an EJB deployment descriptor ejb-jar.xml in the ejb jar file that
    contains the following entry:
    <ejb-reference-description>
    <ejb-ref-name>ejb/URIManager</ejb-ref-name>
    <jndi-name>some class name</jndi-name>
    </ejb-reference-description>
    That is what to look for.
    PJL
    "JKL" <[email protected]> wrote:
    I am attempting to creat a URL portal using the Web Service Portlet Wizard.
    The Wizard seems to build the jsp fine, but I get the following error
    in the
    portlet when I try to bring it up:
    Error retrieving page at http://www.bloomberg.com/index.html Exception:
    Unable to resolve comp/env/ejb/URIManager/ Resolved: 'comp/env/ejb'
    Unresolved:'URIManager'
    I can't even find this path in my installation, nor any reference to
    URIManager. Am I missing a class somewhere? (Note: I have all this
    installed on my laptop for testing, and am not currently working off
    our
    main development server.)
    Thanks for your help.
    - JKL

  • Javax.naming.NameNotFoundException: Unable to resolve ejb-link.

    Env: JDK 1.3.1_08
    Weblogic: 7.0
    We are attempting to use EJB's (session) and have it all localized in a jar.
    The Business and Custom Logic is all compiled to WEB-INF/classes. All the jars including the EJB jar is under WEB-INF/lib.
    On Startup Weblogic throws the error message
    weblogic.management.ApplicationException: activate failed for application
    Module Name: application, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested exception:
    [javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean is not in the context. The context includes the following link bindings: {} Make sure the link reference is relative to the URI of the referencing module.]
    I have tried using the ../ notation before the Appejb.jar in the web.xml and what not, but that does not work either.
    I have sucesfully deployed the EJB jar through the weblogic console.
    Any Clues or suggestions will be most appreciated..
    thanks
    -a

    Create a ear application from the ejb jar and web application war.
    Copy ear application to the applications directory.
    In the ejb-link element in web.xml specify the relative path to the ejb jar.
    <ejb-link>../Appejb.jar</ejb-link>
    thanks,
    Deepak
    Akshay <[email protected]> wrote:
    Env: JDK 1.3.1_08
    Weblogic: 7.0
    We are attempting to use EJB's (session) and have it all localized in
    a jar.
    The Business and Custom Logic is all compiled to WEB-INF/classes. All
    the jars including the EJB jar is under WEB-INF/lib.
    On Startup Weblogic throws the error message
    weblogic.management.ApplicationException: activate failed for application
    Module Name: application, Error: weblogic.j2ee.DeploymentException: Could
    not setup environment - with nested exception:
    [javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean
    is not in the context. The context includes the following link bindings:
    {} Make sure the link reference is relative to the URI of the referencing
    module.]
    I have tried using the ../ notation before the Appejb.jar in the web.xml
    and what not, but that does not work either.
    I have sucesfully deployed the EJB jar through the weblogic console.
    Any Clues or suggestions will be most appreciated..
    thanks
    -a

  • Two web apps using the same EJB client jar

    I am currently deploying two web apps on a server. Both web apps use an EJB client
    jar (the same jar) to access EJB's and both apps work when tested independently.
    The problem arises when I log into app A and then log into app B. As soon as
    I do app A loses it's references to the EJBHomes, and other classes.
    It seems a classloader is unloading the first classes and instances loaded by
    the first app and then loading them from app B's client.jar.
    If I put the client.jar in the system classpath everything is fine, but that's
    just a hack.
    Is it not possible to deploy two web apps on a server using the same client.jar's
    in their own WEB-INF/lib's?

    Joe,
    As Pravin mentions, the checking of those boxes in Workbench triggers scheduled jobs within the EAC that kicks off the scripts at the appropriate time/day. But as you've noticed, there's not a ton of flexibility and you don't get cron or Windows Scheduler-type capabilities.
    If you need to do something special, you can manually kick off the report generation scripts from your control directory using the runcommand.bat (or sh) script or place the command into a cron/Windows Scheduler job:
    For example, to kick off the WeeklyReports job, you would do this:
    runcommand.sh WeeklyReports runSo, assuming you go down the route of creating multiple ReportGenerators and scripts, you would create a job to kick off the new script you've created at the appropriate time.
    Hope that helps,
    Patrick
    http://branchbird.com

  • Common jars for JWS and non-JWS Java Apps?

    Java Application 'A' is installed to file system - not JWS. App 'A' has some jars in common with Java Application 'B', which we would like to deploy using JWS. Do I have to:
    a) duplicate the common jars - once on the file system for App 'A' and once in the cache for App 'B'?
    b) keep the common jars only on the file system - but somehow make them visible to the JWS App 'B'?
    c) keep the common jars only in the JWS cache - but somehow make them visible to the non-JWS App 'A'?
    Please advise.
    Thanks in advance.
    -eman

    Regarding "Enabling Single Sign-On from SAP J2EE Engine/EP to Non-SAP Java Applications" by Tim Mullé, Stephan Boecker
    Could anyone who has this document say if "How to Enable Single Sign-on with Non-SAP Web Application" by Sudip Majumder (Tata Consultancy Services) is a direct replacement and contains all the same information?
    It is currently at: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0c78148-12de-2a10-27bf-960acc753aab
    (until SAP deletes it

  • Unable to deploy EJB: pipeline.jar from pipeline.jar:

    Hi
    While startng server i get this error. but from server console i see it is deployed
    properly.
    Why it is happeing ?
    Can anyone please gie insight into this ?
    Appreciate your time.
    Thanks,
    Nishant
    ####<Sep 8, 2003 9:34:18 AM EDT> <Info> <Data Synchronization> <kreme> <claimsportalserver>
    <main> <kernel identity> <> <00000
    0> <Application: portalApp; Data Repository of type Pipeline Data Repository created
    with persistence manager of type com.bea.
    p13n.appflow.pipeline.internal.PipelinePersistenceManager.>
    ####<Sep 8, 2003 9:34:18 AM EDT> <Error> <J2EE> <kreme> <claimsportalserver> <main>
    <kernel identity> <> <160001> <Error deplo
    ying application pipeline:
    Unable to deploy EJB: pipeline.jar from pipeline.jar:
    java.lang.AbstractMethodError
    at weblogic.jdbc.pool.ResultSet.getClob(ResultSet.java:957)
    at weblogic.jdbc.rmi.internal.ResultSetImpl.getClob(ResultSetImpl.java:1021)
    at weblogic.jdbc.rmi.SerialResultSet.getClob(SerialResultSet.java:1356)
    at com.bea.p13n.util.jdbc.GenericDatabase.getClob(GenericDatabase.java:457)
    at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:565)
    at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:495)
    at com.bea.p13n.management.data.repository.persistence.JdbcPersistenceManager.refresh(JdbcPersistenceManager.java:106)
    at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:186)
    at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
    at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:27
    1)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl.initialize(PipelineExecutorImpl.java:620)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl.<init>(PipelineExecutorImpl.java:124)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl_x8bn7v_Impl.<init>(PipelineExecutorImpl_x8bn7v_Impl.jav
    a:27)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.ejb20.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:128)
    at weblogic.ejb20.manager.StatelessManager.createBean(StatelessManager.java:265)
    at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:148)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
    at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:375)
    at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1507)
    at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1392)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:254)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:85)
    at weblogic.j2ee.Application.addComponent(Application.java:294)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
    at $Proxy44.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4114)

    Hi
    While startng server i get this error. but from server console i see it is deployed
    properly.
    Why it is happeing ?
    Can anyone please gie insight into this ?
    Appreciate your time.
    Thanks,
    Nishant
    ####<Sep 8, 2003 9:34:18 AM EDT> <Info> <Data Synchronization> <kreme> <claimsportalserver>
    <main> <kernel identity> <> <00000
    0> <Application: portalApp; Data Repository of type Pipeline Data Repository created
    with persistence manager of type com.bea.
    p13n.appflow.pipeline.internal.PipelinePersistenceManager.>
    ####<Sep 8, 2003 9:34:18 AM EDT> <Error> <J2EE> <kreme> <claimsportalserver> <main>
    <kernel identity> <> <160001> <Error deplo
    ying application pipeline:
    Unable to deploy EJB: pipeline.jar from pipeline.jar:
    java.lang.AbstractMethodError
    at weblogic.jdbc.pool.ResultSet.getClob(ResultSet.java:957)
    at weblogic.jdbc.rmi.internal.ResultSetImpl.getClob(ResultSetImpl.java:1021)
    at weblogic.jdbc.rmi.SerialResultSet.getClob(SerialResultSet.java:1356)
    at com.bea.p13n.util.jdbc.GenericDatabase.getClob(GenericDatabase.java:457)
    at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:565)
    at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:495)
    at com.bea.p13n.management.data.repository.persistence.JdbcPersistenceManager.refresh(JdbcPersistenceManager.java:106)
    at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:186)
    at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
    at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:27
    1)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl.initialize(PipelineExecutorImpl.java:620)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl.<init>(PipelineExecutorImpl.java:124)
    at com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl_x8bn7v_Impl.<init>(PipelineExecutorImpl_x8bn7v_Impl.jav
    a:27)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:232)
    at weblogic.ejb20.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:128)
    at weblogic.ejb20.manager.StatelessManager.createBean(StatelessManager.java:265)
    at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:148)
    at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
    at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:375)
    at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1507)
    at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1392)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:254)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:85)
    at weblogic.j2ee.Application.addComponent(Application.java:294)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:952)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
    at $Proxy44.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4114)

  • In iOS8 I receive an "Unable to Download Apps" for apps that are no longer in App Store and cannot delete it from iPhone 6, how do I resolve?

    I keep receiving an "Unable to Download Apps" error pop-up on my iPhone 6 for two apps. Neither app is in the App Store anymore. I held down the icon/badge for the app but when I click on the "x" to try to delete the app it will not let me because "" cannot be found. I tried to delete it from iTunes but the only selections I have next to the app are "Install" and "Will Install" but no remove. How do I get these banners to stop appearing and my phone to stop trying to download the two apps?? It is sucking my battery down.

    Go into iTunes, create a backup without Apps included, and then use that backup on your phone. Fixed the issue for me, and it didn't even seem to remove the apps like I thought it would. If it does remove the apps you can simply redownload them without too much trouble.

  • I am unable to get common.jar

    I have the following path but my basis consultant is on leave for a week
    common.jar (c:\usr\sap\<version>\JC00\j2ee\cluster\server0\bin\ext\com.sap.portal.common)
    Is there any other path from which I can get the common.jar file.
    May be from the portal is it possible to download this file .
    If yes please specify the path.
    10 to one who sends me the .jar at [email protected]
    Edited by: anzar naik on Jul 15, 2008 1:15 PM

    Hi,
    you will find the same in google. Its not related to sap. Its related to java. Most of the applications servers need this file.
    In MQ Server also you will find this jar.
    Thanks,
    RamuV

  • Unable to load the EJB module. DeploymentContext does not contain any EJB.

    I'm writing an enterprise application to familiarize myself with Glassfish 3.1.2 and EJB 3.1. I've created several local, stateless beans, and injected one into a JSF managed bean. The ejb and web modules compile fine, but when I launch the application with Glassfish I get the following startup error and the application does not deploy. I don't understand what it means, can someone ellaborate?
    SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer prepare method
    SEVERE: Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
    SEVERE: Exception while preparing the app
    SEVERE: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
    If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
    org.glassfish.deployment.common.DeploymentException: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
    If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
         at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:166)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
         at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
         at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
         at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
         at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
         at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
         at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
         at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
         at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
         at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
         at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
         at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
         at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
         at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
         at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
         at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
         at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
         at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
         at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
         at java.lang.Thread.run(Thread.java:722)

    My guess is that you deployed an ejb without bean in it. when you have an ejb module, be sure you have at least one bean present.
    Are you sure you have implementend some beans? Or did you do this only in the web module?
    Try adding an @Stateless bean doing nothing in you ejb module, redeploy and let me know if that works

  • Unable to invoke a EJB from a BPEL process

    I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
    This is what I see from the EM....
    Non Recoverable System Fault :
    javaInterface attribute for the binding is missing or the inteface class is not available.
    Below is a part of the stack trace from the soa server log…
    Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
    Missing class: com.abc.GreetingEJBBean
    Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
    elegateImpl
    Loader: sun.misc.Launcher$AppClassLoader@20929799
    Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Piece of xml from the composite.xml
    <reference name="GreetingService"
    ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
    <interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
    <binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
    javaInterface="com.abc.GreetingEJB"/>
    </reference>
    Looks like its not able to find the javaInterface mentioned above.
    I have a simple EJB with one business method and a very simple BPEL process.
    @Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
    @WebService
    public class GreetingEJBBean implements GreetingEJB {
    public GreetingEJBBean() {
    public String greetUser(String name){
    return ("Hello " + name);
    Any help would be greatly appreciated.

    I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
    At high level here's what I have noted so far:
    1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
    2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
    3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
    4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

  • No metadata found for metadata object "/oracle/apps/hcm/common/core/publicM

    Hi Folks -
    I am getting the below error when I try to run the HcmCompWorkbenchWorkarea.jspx in the Fusion COmpensation Module, locally from the JDeveloper Customization Role.
    I simply created a FUsion Customization APplication with a Customization,Model and View COntroller Projects without doing any customizations and was just trying to run the above page.
    I have never encountered this type of error before. Any help would be helpful.
    Thanks
    Srinivasa Sunchu
    Target URL -- http://127.0.0.1:7101/hcmCompensation/faces/HcmCompWorkbenchWorkarea
    [9544:5676:0523/110814:ERROR:gpu_info_collector_win.cc(98)] Can't retrieve a valid WinSAT assessment.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <ReferenceStoreHelper> <getReferencesMapEx> Incomplete connection reference object for connection:AtkRPSoapConn
    <May 23, 2013 11:08:19 AM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:51,427 during the configured idle timeout of 5 secs>
    PSR: Reading system property VOMaxFetchSize
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <IdentityStoreUtil> <getIdentityStoreFactory> Cannot initialize identity store, cause: javax.naming.NameNotFoundException: [LDAP: error code 32 - LDAP Error 32 : No Such Object]; remaining name 'cn=common, cn=products, cn=oraclecontext'.
    <May 23, 2013 11:08:39 AM PDT> <Error> <HTTP> <BEA-101017> <[ServletContext@1028995650[app:XXWFCAllocationAnalytics module:hcmCompensation path:/hcmCompensation spec-version:2.5 version:V2.0], request: weblogic.servlet.internal.ServletRequestImpl@425c22f8[
    GET /hcmCompensation/faces/HcmCompWorkbenchWorkarea?_afrLoop=10188581450556&_afrWindowMode=0&_afrWindowId=null HTTP/1.1
    Connection: keep-alive
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
    Referer: http://127.0.0.1:7101/hcmCompensation/faces/HcmCompWorkbenchWorkarea
    Accept-Encoding: gzip,deflate,sdch
    Accept-Language: en-US,en;q=0.8
    Cookie: JSESSIONID=W2yXRpbPSyQKgf59Vh8Kym62WBK7t34lH4yTvJzZ03swB1pLsm3b!-1548472823; ORA_FUSION_PREFS=v1.0~bG9jYWxlPWVufmRlZmF1bHRMYW5ndWFnZU1hcmtlcj10cnVl; ORA_FND_SESSION_HRDEV=DEFAULT_PILLAR:iWB1vrLNEeUh5Hk7IlYFujwb4JU13XEsl/YsTcvZn1XtTMc1dx574a56Roc0fPzh:1369332516423
    ]] Root cause of ServletException.
    oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25002. Error message parameters are {0=null, 1=oracle.apps.hcm.common.core.publicModel.DataControls}
         at oracle.jbo.mom.DefinitionManager.findDefObjectUsingMetadataObject(DefinitionManager.java:3056)
         at oracle.adf.model.binding.DCDataControlConfigDef.findDefObject(DCDataControlConfigDef.java:32)
         at oracle.adf.model.binding.DCDataControlDef.findDefObject(DCDataControlDef.java:377)
         at oracle.adf.model.binding.DCDataControlReference.<init>(DCDataControlReference.java:55)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadDataControlUsage(JUApplicationDefImpl.java:1137)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/oracle/apps/hcm/common/core/publicModel/DataControls.dcx"
         at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1336)
         at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:3248)
         at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1211)
         at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1157)
         at oracle.jbo.mom.DefinitionManager.findDefObjectUsingMetadataObject(DefinitionManager.java:3012)
         Truncated. see log file for complete stacktrace
    >
    <May 23, 2013 11:08:39 AM PDT> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'DefaultServer' has triggered at May 23, 2013 11:08:39 AM PDT. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    WatchData: DATE = May 23, 2013 11:08:39 AM PDT SERVER = DefaultServer MESSAGE = [ServletContext@1028995650[app:XXWFCAllocationAnalytics module:hcmCompensation path:/hcmCompensation spec-version:2.5 version:V2.0], request: weblogic.servlet.internal.ServletRequestImpl@425c22f8[
    GET /hcmCompensation/faces/HcmCompWorkbenchWorkarea?_afrLoop=10188581450556&_afrWindowMode=0&_afrWindowId=null HTTP/1.1
    Connection: keep-alive
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.93 Safari/537.36
    Referer: http://127.0.0.1:7101/hcmCompensation/faces/HcmCompWorkbenchWorkarea
    Accept-Encoding: gzip,deflate,sdch
    Accept-Language: en-US,en;q=0.8
    Cookie: JSESSIONID=W2yXRpbPSyQKgf59Vh8Kym62WBK7t34lH4yTvJzZ03swB1pLsm3b!-1548472823; ORA_FUSION_PREFS=v1.0~bG9jYWxlPWVufmRlZmF1bHRMYW5ndWFnZU1hcmtlcj10cnVl; ORA_FND_SESSION_HRDEV=DEFAULT_PILLAR:iWB1vrLNEeUh5Hk7IlYFujwb4JU13XEsl/YsTcvZn1XtTMc1dx574a56Roc0fPzh:1369332516423
    ]] Root cause of ServletException.
    oracle.jbo.NoDefException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-25002. Error message parameters are {0=null, 1=oracle.apps.hcm.common.core.publicModel.DataControls}
         at oracle.jbo.mom.DefinitionManager.findDefObjectUsingMetadataObject(DefinitionManager.java:3056)
         at oracle.adf.model.binding.DCDataControlConfigDef.findDefObject(DCDataControlConfigDef.java:32)
         at oracle.adf.model.binding.DCDataControlDef.findDefObject(DCDataControlDef.java:377)
         at oracle.adf.model.binding.DCDataControlReference.<init>(DCDataControlReference.java:55)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadDataControlUsage(JUApplicationDefImpl.java:1137)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadDataControls(JUApplicationDefImpl.java:1097)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadContainees(JUApplicationDefImpl.java:1051)
         at oracle.jbo.mom.ContainerDefImpl.loadFromXMLFile(ContainerDefImpl.java:373)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadFromXMLFile(JUApplicationDefImpl.java:705)
         at oracle.jbo.mom.DefinitionManager.loadProjectDefinition(DefinitionManager.java:1789)
         at oracle.jbo.mom.DefinitionManager.loadProjectDefinition(DefinitionManager.java:1881)
         at oracle.jbo.uicli.mom.JUMetaObjectManager.findCpx(JUMetaObjectManager.java:647)
         at oracle.jbo.uicli.mom.JUApplicationReference.resolve(JUApplicationReference.java:81)
         at oracle.jbo.uicli.mom.JUApplicationReference.getDef(JUApplicationReference.java:88)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.findBindingContainerIdByPath(JUApplicationDefImpl.java:374)
         at oracle.adf.model.BindingContext.findBindingContainerIdByPath(BindingContext.java:1769)
         at oracle.adf.model.BindingContext.findBindingContainerDefByPath(BindingContext.java:1715)
         at oracle.adf.model.BindingRequestHandler.isPageViewable(BindingRequestHandler.java:371)
         at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:260)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:203)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:128)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.apps.fnd.applcore.common.ApplSessionFilter.doFilter(ApplSessionFilter.java:652)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.wcps.client.PersonalizationFilter.doFilter(PersonalizationFilter.java:75)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.webcenter.content.integration.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:168)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:248)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/oracle/apps/hcm/common/core/publicModel/DataControls.dcx"
         at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1336)
         at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:3248)
         at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1211)
         at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1157)
         at oracle.jbo.mom.DefinitionManager.findDefObjectUsingMetadataObject(DefinitionManager.java:3012)
         at oracle.adf.model.binding.DCDataControlConfigDef.findDefObject(DCDataControlConfigDef.java:32)
         at oracle.adf.model.binding.DCDataControlDef.findDefObject(DCDataControlDef.java:377)
         at oracle.adf.model.binding.DCDataControlReference.<init>(DCDataControlReference.java:55)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadDataControlUsage(JUApplicationDefImpl.java:1137)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadDataControls(JUApplicationDefImpl.java:1097)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadContainees(JUApplicationDefImpl.java:1051)
         at oracle.jbo.mom.ContainerDefImpl.loadFromXMLFile(ContainerDefImpl.java:373)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.loadFromXMLFile(JUApplicationDefImpl.java:705)
         at oracle.jbo.mom.DefinitionManager.loadProjectDefinition(DefinitionManager.java:1789)
         at oracle.jbo.mom.DefinitionManager.loadProjectDefinition(DefinitionManager.java:1881)
         at oracle.jbo.uicli.mom.JUMetaObjectManager.findCpx(JUMetaObjectManager.java:647)
         at oracle.jbo.uicli.mom.JUApplicationReference.resolve(JUApplicationReference.java:81)
         at oracle.jbo.uicli.mom.JUApplicationReference.getDef(JUApplicationReference.java:88)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.findBindingContainerIdByPath(JUApplicationDefImpl.java:374)
         at oracle.adf.model.BindingContext.findBindingContainerIdByPath(BindingContext.java:1769)
         at oracle.adf.model.BindingContext.findBindingContainerDefByPath(BindingContext.java:1715)
         at oracle.adf.model.BindingRequestHandler.isPageViewable(BindingRequestHandler.java:371)
         at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:260)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:203)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:128)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.apps.fnd.applcore.common.ApplSessionFilter.doFilter(ApplSessionFilter.java:652)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.wcps.client.PersonalizationFilter.doFilter(PersonalizationFilter.java:75)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.webcenter.content.integration.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:168)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:248)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = SSUNCHU-WS01 TXID = CONTEXTID = e8f08bf4136e20a7:3e596c4f:13ed286c9b9:-8000-0000000000000295 TIMESTAMP = 1369332519262
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 30000
    >
    <May 23, 2013 11:08:45 AM PDT> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in c:\oracle\jdeveloper\system11.1.1.6.39.62.68\defaultdomain\servers\defaultserver\adr\diag\ofm\defaultdomain\defaultserver\incident\incdir_41 with a lockout minute period of 1.>

    Thanks, that did help and it was throwing similar errors for other jar files, which I added and now the page opens.
    But the issue that I am facing now is on this page there is a Manager Search, wherein I can proxy a manager.
    This Search popup is not returning any values. Previously if I reinstalled my system-jazn-data.xml file from my colleauge
    and rebooting my laptop worked. But now even that doe snot help.
    Srinivasa Sunchu

  • Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'

    Hi
    When executing import/export service through FSM we are getting below error on server console. Can someone please help us to resolve this.
    <Nov 22, 2012 10:25:14 PM IST> <Error> <oracle.j2ee.ws.common.jaxws.JAXWSMessages> <BEA-000000> <[MessageID: uuid:3eac9f32-ad81-4d96-b5b2-18cf0fd887c0[migRequestId=300100015300332][migObjectId=300100015300326][]] Could not send async request message to the JMS queue.
    java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.security.Security.runAs(Security.java:61)
    at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
    at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
    at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:365)
    at oracle.j2ee.ws.server.jaxws.JMSChannel.getConnection(JMSChannel.java:468)
    at oracle.j2ee.ws.server.jaxws.JMSChannel.sendMessage(JMSChannel.java:235)
    at oracle.j2ee.ws.server.jaxws.JMSChannel.sendRequest(JMSChannel.java:199)
    at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate$JMSMessageQueue.send(AsyncServiceRuntimeDelegate.java:170)
    at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate.pro
    Caused By: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    FYI:
    The "oracle.jrf.ws.async_template_11.1.1.jar" jar file required for JMS (oracle.j2ee.ws.server.async.) which is present in below directory path of weblogic standalone.
    Edited by: user12820425 on Dec 2, 2012 11:56 PM

    Are you using Standalone (or) Integrated WLS. It works only on Standalone WLS.
    Also for these issues, please put this in Cross Pillar Integration Forum. Contact Ning.Dong

  • Unable to resolve 'weblogic.messaging.dispatcher.S:null'

    We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
    Stack Trace:
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
    at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
    at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
    at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
    at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
    at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
    at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
    at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
    at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
    ... 8 more
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
    at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
    at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
    at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
    at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
    ... 9 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
    ... 14 more

    Hi,
    I would suggest you to go through these 2 links which you give all the details about UDD
    Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?page_id=1976
    Tips to solve UDQ issues
    - Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
    - Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
    - All the managed servers are in the same cluster.
    - If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
    - Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
    Hope this helps you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

Maybe you are looking for