Are workmanagers visible in the jndi tree viewer?

Hi, I'm trying to setup a workmanager, and I'm having a few problems, but I'm just wondering if I'm falling at the first hurdle. I've tried creating workmanagers at the global and application level, but looking in the admin console for my server they never show up in the jndi tree viewer. Should I expect to see my workmanager there? If I look in the deployment then I do see that the workmanager exists, alongside default.
Thanks.

If you create a workmanager at the application level, you'll see the work manager in the console under Deployments -> your app -> Monitoring ->Workload.
If you create a workmanager at the domain / server level and reference it within your app's deployment descriptors ( wl-dispatch-policy ), you can look under Servers ->your app's targeted server -> Deployments -> your app -> Monitoring -> Workload. In this case, you'll see all the workmanagers targeted to that server, but you can confirm your app's usage of the correct wm by submitting a request to your app and seeing an increase in the completed requests column of the display.
A work manager configured at the domain / server level doesn't have a JNDI name attribute that you enter. You just use the same workmanager name in your deployment descriptor <wl-dispatch-policy>someWM</wl-dispatch-policy>.
The handling of stuck threads seems to be a trouble point for application defined workmanagers, so we've decided to stick with individual server level work managers for each app.

Similar Messages

  • Localhome doesnot appear on the jndi tree on weblogic 8.1 after deployment

    I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
    I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
    "The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
    what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
    my descriptors are as follows:
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <display-name>MeldePersonDatabaseEJB</display-name>
    <enterprise-beans>
    <session>
    <display-name>MeldePersonDatabaseFacadeBean</display-name>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
    <local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
    <ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    --------------------

    I believe the console only supports testing of remote ejbs.
    I didn't see anything obviously wrong with your app. I'm guessing that
    it's working fine. I'd just write a Servlet that hits the local ejb.
    That should prove whether it's working or not.
    -- Rob
    Murteza Salemi wrote:
    I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
    I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
    "The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
    what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
    my descriptors are as follows:
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <display-name>MeldePersonDatabaseEJB</display-name>
    <enterprise-beans>
    <session>
    <display-name>MeldePersonDatabaseFacadeBean</display-name>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
    <local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
    <ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

  • Loading the JNDI Tree in a Cluster

    Is there any special processing that occurs with a Startup class when it
              has been
              started via the cluster level properties file?
              We've got a class that loads the JNDI tree for various configuration for
              our application.
              It's written that so that it will rebind() entries in the tree, so two
              copies could work together
              in the cluster, but I'd like to prevent the double work. (One copy
              bind()s an element, then the other rebind()s the same value.
              Are Startups "cluster" aware, and is there any magic to simplify this
              for me (or do I do the
              work of creating a semaphore-like setup in my class to detect two copies
              running.)
              Thanks in Advance,
              Brian Homrich
              Chicago, Illinois
              

    In the startup class on Environment object if you don't set
              replicatebindings to false, in a cluster all locally bound objects will be
              replicated. The default it true. So, jndi will try replicate every
              bind/rebind etc.
              Rebind will remove old copy and bind the new copy. But I have to understand
              more what you are trying to do, before I can be of any help.
              - Prasad
              Brian Homrich wrote:
              > Is there any special processing that occurs with a Startup class when it
              > has been
              > started via the cluster level properties file?
              >
              > We've got a class that loads the JNDI tree for various configuration for
              > our application.
              > It's written that so that it will rebind() entries in the tree, so two
              > copies could work together
              > in the cluster, but I'd like to prevent the double work. (One copy
              > bind()s an element, then the other rebind()s the same value.
              >
              > Are Startups "cluster" aware, and is there any magic to simplify this
              > for me (or do I do the
              > work of creating a semaphore-like setup in my class to detect two copies
              > running.)
              >
              > Thanks in Advance,
              >
              > Brian Homrich
              > Chicago, Illinois
              

  • EJB not published in the JNDI tree

    I am trying to deploy a simple ear file containing one ejb on to WL 9.2. The app is deploying without any problems, but the EJB is not published in the JNDI tree. When I look at the EJB's configuration through the admin console, it does indicated that the JNDI name is set to "ejb/HelloWorld". However, when I look at the JNDI tree there is no HelloWorld node under ejb. Below is my weblogic-ejb-jar.xml file that defines the JNDI name:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar
      xmlns="http://www.bea.com/ns/weblogic/90"
      xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
                          http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
      <weblogic-enterprise-bean>
        <ejb-name>HelloWorld</ejb-name>
        <stateless-session-descriptor>
          <pool>
            <max-beans-in-free-pool>1000</max-beans-in-free-pool>
            <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
          </pool>
        </stateless-session-descriptor>
        <transaction-descriptor>
          <trans-timeout-seconds>0</trans-timeout-seconds>
        </transaction-descriptor>
        <enable-call-by-reference>false</enable-call-by-reference>
        <jndi-name>ejb/HelloWorld</jndi-name>
      </weblogic-enterprise-bean>
    </weblogic-ejb-jar>Can anyone help me understand why the JNDI name is not being published?
    Thanks.

    Hi all,
    It seems that I have the same problem with WL 10. Has any of you solved this yet?
    I'm trying to switch my application from perfectly working JBoss 4.2 environment to WL 10 and no luck so far, because of this weird problem.
    What I have noticed so far is:
    - Some of my sessions beans are deployed ok
    - "Big" session beans are silently ignored in deployment. This is unbelievable because these beans are SILENTLY ignored. And, my session beans are not that big. Under 700 LOC all of them.
    - These EJBs don't appear in admin console's JNDI-browser
    - These EJBs don't appear in ear-content details in "Deployments" section.
    - These EJBs don't get their stubs generated in server/cache/EJBCompilerCache
    - One big is ignored, but when splitting it in e.g. three smaller ones, all of these three session beans are deployed successfully
    I'm using EJB3 session beans with no XML-descriptors.
    So what is going on here??!
    Looking forward to hear some answers. At least from BEA developers or other insiders.
    Thanks.
    Edited by villeingman at 06/13/2007 12:42 AM

  • MRS - Resources and demands are not visible in the Planning Board

    Hi Friends - I am working on the the MRSS 610. We have installed it on the our ECC 6.0 as an add-on. We have configured the system as per the configuration guide.
    But when I am accessing Manageru2019s Planning Board -  /MRSS/PLBOMGR , using the Organization unit, I am getting Notification saying that the resources assigned to the Organization unit are not available in the MRS.
    "Resource 00000000010000000000000000000000 not yet created in the WFM Core"
    The details of the Error message
    "Resource 00000000010000000000000000000000 not yet created in the WFM Core
    Message no. /MRSS/SGE034
    Diagnosis
    Resource 00000000010000000000000000000000 has not yet been created in MRS.
    System Response
    No assignments have been created for resource 00000000010000000000000000000000, even though, according to the organizational model, this resource is to be taken into consideration in the planning board.
    Procedure
    Contact technical support.
    Procedure for System Administration
    Create the resource in question in MRS."
    I have run the Report
    /MRSS/HCM_RPTWFMIF : Transfers the HR data (availability times, qualifications and the resources itself) into the MRS Basis
    But even after that I am not getting the resources in the planning board.
    Also I am not able to view the Demands from PM/CS orders.
    I have created PM Orders and
    Assigned Work centres to the operations and
    assigned the Resources to the Operations.
    The HR assignment to the work center is also done.
    I have tried T Code   /MRSS/PLBOSRV - Enter the MRS planning board using a specified order
    to pull the order demand. But it is not working
    Its giving following message
    1004280 is not a valid demand
    Message no. /MRSS/SGU139
    Diagnosis
    The order does not exist in MRS.
    This may be because:
    The order number has an invalid format.
    The order does not exist.
    The order is not relevant for planning and has therefore not been transferred to MRS.
    The order has been deleted from MRS.
    Pls help me on this.
    Thanks in advance and warm regards
    Purnendu

    Hi Anil/Saurabh - Thanks a lot for your replies.
    I have checked the MRS configuration as per your suggestion.
    It looks fine as per the configuration guide. I have done the PM/CS integration for Orders as demand.
    But the Demands are not visible on the Planning Board.
    I have checked in the debugging mode what is causing the problem - It looks like
    "The Database Table: /mrss/d_dem_h  needs entry"
    But there are no entries in this table.
    I could not find any Customizing transactions or Application transactions for maintaining this table. This is an Application Table for Master and Transaction Data and its Display and Maintenance allowed with Restriction.
    I could not also find any transaction for transferring Demand from ECC(R/3) to MRS.
    How do I maintain entries in this table?
    How do I transfer Demand from ECC to MRS?
    Saurabh - I have also been not able to transfer HR Resources from ECC to MRS.
    We don't have WFM Core installed in our instance. But MRS should work fine without WFM. MRS Basis should take care of it.
    To transfer Employee resources i have run the Program " /MRSS/HCM_RPTWFMIF". But when I execute the transaction with the selection parameters system shows that it is processing (Clock at the bottom Status bar) but it does not shows any result or status.
    So I am not sure whether it is executing the program properly.
    Pls help me resolve these issues.
    Thanks and warm regards
    Purnendu

  • Binding huge object to the jndi tree.

    Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. This same thing is working with about 4MB object in Sun One but takes about 45 Mins to 1 Hour to finish the serialization etc for jndi .Kindly provide some guidance.Thanks in advance.

    True. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
    Obviously the values that I inserted affected all the applications, like the url of our SOA server.

  • Could not lookup PortalManagerHome in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager

    Hi
    I am just a starter on WLPortal.
    I have created a barebone Application from scratch. I have synchronized it properly
    from EBCC to WLP. But When I am trying to access the home page of my application,
    I am getting from stack trace -
    <Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup PortalManagerHome
    in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
    javax.naming.NameNotFoundException: Unable to resolve comp/env/ejb/PortalManager
    Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:802)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:173)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:36)
    at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at com.bea.p13n.util.JndiHelper.lookupNarrow(JndiHelper.java:96)
    at com.bea.portal.appflow.PortalAppflowHelper.<clinit>(PortalAppflowHelper.java:64)
    at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.init(PortalWebflowServlet.java:78)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:700)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:643)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:588)
    at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:368)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Nov 6, 2002 5:37:59 PM IST> <Error> <HTTP> <[WebAppServletContext(19695286,FirstWebApp,/FirstWebApp)]
    Servlet failed with Exception
    java.lang.NullPointerException:
    at com.bea.portal.appflow.PortalAppflowHelper.createPortalManager(PortalAppflowHelper.java:82)
    at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:187)
    at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:99)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    When I decompiled the class PortalAppflowHelper, I found a static block in it,
    which was as under-
    static
    debug = Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
    try
    if(debug.ON)
    debug.out("Looking up PortalManagerHome using EJB reference java:comp/env/ejb/PortalManager");
    portalManagerHome = (PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
    com.bea.portal.manager.ejb.PortalManagerHome.class);
    if(debug.ON)
    debug.out("Successfully retrieved PortalManagerHome " + portalManagerHome);
    catch(Exception e)
    PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
    e);
    I have checked the PortalManager's JNDI name on WLConsole. Its ${APPNAME}.BEA_portal.PortalManager.
    Should I change it?
    When I tried to change it, I started getting other weird errors.
    Thanks
    Neeraj Hans

    Neeraj -
    The Portal framework code (including PortalAppflowHelper) uses ejb
    references to find the PortalManager (and other EJBs) from servlets and
    taglibs; that is what is signified by the java:comp/env/... name.
    Since you built your webapp from scratch (instead of using the portal
    wizard), you will need to make sure the you have the appropriate
    <ejb-ref> entries in your web.xml, and the corresponding
    <ejb-reference-description> entries in your weblogic.xml. By default,
    you will need at least mappings for:
    - ejb/PortalManager
    - ejb/UserManager
    - ejb/GroupManager
    - ejb/PipelineExecutor
    - ejb/EventService
    See either the resulting webapp from using the portal wizard or
    BEA_HOME/weblogic700/samples/portal/sampleportalDomain/beaApps/sampleportal/sampleportal/WEB-INF
    for example syntax.
    Greg
    Neeraj Hans wrote:
    Hi
    I am just a starter on WLPortal.
    I have created a barebone Application from scratch. I have
    synchronized it properly
    from EBCC to WLP. But When I am trying to access the home page of my
    application,
    I am getting from stack trace -
    <Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup
    PortalManagerHome
    in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
    javax.naming.NameNotFoundException: Unable to resolve
    comp/env/ejb/PortalManager
    Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
    at <stack trace lines snipped>
    When I decompiled the class PortalAppflowHelper, I found a static
    block in it,
    which was as under-
    static
    debug =
    Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
    try
    if(debug.ON)
    debug.out("Looking up PortalManagerHome using EJB
    reference java:comp/env/ejb/PortalManager");
    portalManagerHome =
    (PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
    com.bea.portal.manager.ejb.PortalManagerHome.class);
    if(debug.ON)
    debug.out("Successfully retrieved PortalManagerHome "
    + portalManagerHome);
    catch(Exception e)
    PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
    e);
    I have checked the PortalManager's JNDI name on WLConsole. Its
    ${APPNAME}.BEA_portal.PortalManager.
    Should I change it?
    When I tried to change it, I started getting other weird errors.
    Thanks
    Neeraj Hans

  • Images are not visible in the iPhone.

    When I open iTunes there are number of images found in the iPhone, but the images are not visible in the iPhone actually.

    I using local deployment. I deploy my application directly from NWDS to a Mobile Client running also locally in my machine. Maybe I'm wrong, but I think that Mobile Client look for resources in NWDS workspace.
    This is the dpi file located in the Mobile Client inbox folder when I perform the deployment.
    <?xml version="1.0" encoding="UTF-8"?>
    <deployment>
    <device>
    <repository>
    <mcd name="IrviaDemoApp" namespace="" version="1">
    <action type="install"/>
    <location type="local">
    <source path="C:\Documents and Settings\oloranube\workspace.sr5.jdi\LocalDevelopment\DCs\company.es\irvia_demo_app\_comp\MOBILE-INF\MCD.xml" property="mcd" type="file"/>
    <component name="hpcds.es~irvia_demo_app">
    <applications>
    <application deploy="true" name="IrviaDemoApp"/>
    </applications>
    <source path="C:\Documents and Settings\oloranube\workspace.sr5.jdi\LocalDevelopment\DCs\company.es\irvia_demo_app\_comp\bin" property="bin" type="dir"/>
    <source path="C:\Documents and Settings\oloranube\workspace.sr5.jdi\LocalDevelopment\DCs\company.es\irvia_demo_app\_comp\gen_wdp" property="gen_wdp" type="dir"/>
    <source path="C:\Documents and Settings\oloranube\workspace.sr5.jdi\LocalDevelopment\DCs\company.es\irvia_demo_app\_comp\src\mimes" property="mimes" type="dir"/>
    <source path="C:\Documents and Settings\oloranube\workspace.sr5.jdi\LocalDevelopment\DCs\company.es\irvia_demo_app\_comp\gen_wdp\application-j2ee-engine.xml" property="j2ee_xml" type="file"/>
    </component>
    </location>
    </mcd>
    </repository>
    </device>
    </deployment>
    There is a <source> entry for the mimes directory, where "Component images" are located.
    PD: Sorry about my poor english. I hope you to understand me.

  • Goods are not visible on the Web Shop main page (RUMP UP)

    Hi colleagues.
    Help please anybody :)
    There was the problem with the goods in Web Shop.
    Goods are not visible on the page Web Shop.
    Below you can see actions performed by us and Prerequisites:
    1. Repository was unachieved from Standard archive - WEC20_MDMCATALOG_CONS
    2. Taxonomy, Hierarchy and Lookup table data were transferred from CRM via MDMGX
    3. Manually created root node in Product Catalogs table in MDM
    4. Put technical code (ID) of created node to Product Catalog module in WCEM configuration - field Catalog ID.
    5. Fill another necessary fields in Product Catalog module in WCEM.
    6. Manually add test record in MDM and linked to node in Product Catalog table, elements from Main Taxonomy and other required fields.
    7. In preview mode of WCEM configuration not possible see any records from MDM (but product catalog elements showed correctly)
    More information about settings in MDM, CRM,WCB and configuration steps can see in attachment files
    Best regardn,
    Andrey

    Hi Denis
    Leading zeroes it's no my case, because the products (materials) replicated from CRM to MDM.
    Replication from CRM to MDM via MDMGX and Initial Load R3AC1 is successfull.
    But on the WebChannel web shop page this products are not visible.
    I have suggested that the problem in authirizations of technical user, which uses RFC Destinations from SAP NW AS Java (Web Channel) to MDM.
    According Security Guide for SAP Web Channel 2.0 (paragr. 8.3.2 see please screenshot), user of WEC_MDM_DEFAULT destination must assign the role WEBCHANNEL_CATALOG_DISPLAY_ROLE.
    But this role does not exist in the system (SAP MDM, SAP NW).
    Please give me advice about this.

  • The ipad music app does not allow me to play certain tracks that i have synced via my itunes. The tracks are clearly visibly in the music app but when tap on them to play they wont play. help and advice will be much appreciated

    The ipad music app does not allow me to play certain tracks that i have synced via my itunes. The tracks are clearly visibly in the music app but when tap on them to play they wont play. what do i do?

    Agree about the disaster part. I haven't found a fix within iTunes.
    I gave up and switched to downcast 2 days ago. Even though it was a hassle to re-subscribe to all my podcasts, im so much happier.
    To make switching easier, I found that in iTunes you can "get info" on the podcast and copy the RSS address to the clipboard. Put all of these in a message note. When iCloud syncs the note to your phone, you can copy and paste the urls into downcast one at a time to subscribe.
    Downcast has crashed on me occassionally when I'm subscribing to feeds, but so far it has recovered gracefully each time and no data was lost.

  • TS1292 There are two numbers that are not visible in the middle of the code What can I do?

    There are two digits that are not visible in the middle of the itune code. How can I still access this card?

    Click here and request assistance, supplying as much of the code as you can.
    (74408)

  • Adding entries to the JNDI tree

    Is it possible to add entries to the JNDI path of the OC4J server? I know you can add it via web.xml, but I´m looking into doing that manually through the admin console?
    Thanks,
    Mario

    True. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
    Obviously the values that I inserted affected all the applications, like the url of our SOA server.

  • AS7.0b:JMS: can I browse the JNDI tree with the admin tool?[cid:792813]

    Is there a way to browse the JNDI Tree thru the Admin Tool.
    1) I have deployed a Topic Destination with the name jms/AuditTopic,
    jms/MonitorTopic
    2) I have deployed a MDB with the name AuditAgent which is tied to
    jms/AuditTopic
    when the server is deploying the AuditAgent MDB it throws the following
    error:
    INFO: JMS5002: Binding [< JMS Destination: jms/MonitorTopic,
    javax.jms.Topic, No properties >]
    SEVERE: JMS5027: Exception in creating JMS destination administered object
    [jms/MonitorTopic]: [[A4017]: Destination name is not specified.]
    SEVERE: JMS5031: Exception in creating JMS destination administered object
    javax.jms.JMSException: [A4017]: Destination name is not specified.
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.createDestinationObject(JMSAdminImpl.java:193)
    at com.iplanet.ias.jms.IASJmsConfig.createDestination(UnknownSource)
    at com.iplanet.ias.jms.IASJmsUtil.installJMSResources(UnknownSource)
    at com.sun.enterprise.resource.ResourceInstaller.installJMSResources(UnknownSource)
    at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(UnknownSource)
    at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
    INFO: JMS5002: Binding [< JMS Destination: jms/AuditTopic, javax.jms.Topic,
    No properties >]
    SEVERE: JMS5027: Exception in creating JMS destination administered object
    [jms/AuditTopic]: [[A4017]: Destination name is not specified.]
    SEVERE: JMS5031: Exception in creating JMS destination administered object
    javax.jms.JMSException: [A4017]: Destination name is not specified.
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.createDestinationObject(JMSAdminImpl.java:193)
    at com.iplanet.ias.jms.IASJmsConfig.createDestination(UnknownSource)
    at com.iplanet.ias.jms.IASJmsUtil.installJMSResources(UnknownSource)
    at com.sun.enterprise.resource.ResourceInstaller.installJMSResources(UnknownSource)
    at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(UnknownSource)
    at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
    INFO: JMS5002: Binding [< JMS Connection Factory:
    jms/TopicConnectionFactory, javax.jms.TopicConnectionFactory, No properties>]
    FINE: ++++ Entered SecClientRequestInterceptor::send_request()
    SEVERE: NAM5005: JMS Destination object not found: jms/AuditTopic
    SEVERE: javax.naming.NameNotFoundException
    javax.naming.NameNotFoundException: AuditTopic not found
    at com.sun.enterprise.naming.TransientContext.doLookup(Unknown Source)
    at com.sun.enterprise.naming.TransientContext.lookup(Unknown Source)
    at com.sun.enterprise.naming.TransientContext.lookup(Unknown Source)
    at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(Unknown Source)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.lookup(Unknown Source)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
    at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
    at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
    SEVERE: EJB5016: Exception creating BaseContainer :
    [javax.naming.InvalidNameException: JMS Destination object not
    found:`jms/AuditTopic`]
    FINE: EJB5016: Exception creating BaseContainer : [{0}]
    javax.naming.InvalidNameException: JMS Destination object not
    found:`jms/AuditTopic`
    at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
    at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
    at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
    SEVERE: EJB5090: Exception in creating EJB container
    [javax.naming.InvalidNameException: JMS Destination object not
    found:`jms/AuditTopic`]
    WARNING: LOADER5004: UnExpected error occured while creating ejb container
    javax.naming.InvalidNameException: JMS Destination object not
    found:`jms/AuditTopic`
    at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.setupEnvironment(Unknown Source)
    at com.sun.ejb.containers.BaseContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(Unknown Source)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Unknown Source)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
    at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
    at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
    FINE:
    org.omg.CORBA.OBJ_ADAPTER: NoContext: outside of an invocation context.
    vmcid: 0x0 minor code: 0 completed: No
    at com.sun.corba.ee.internal.POA.DelegateImpl.poa(Unknown Source)
    at org.omg.PortableServer.Servant._poa(Servant.java:99)
    at com.rai.common.inbound._InboundManagerBean_EJBObjectImpl_Tie.deactivate(Unknown Source)
    at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.cleanUpTie(Unknown Source)
    at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.unexportObject(Unknown Source)
    at javax.rmi.CORBA.Util.unexportObject(Util.java:159)
    at com.sun.enterprise.iiop.POAProtocolMgr.destroyReference(Unknown Source)
    at com.sun.ejb.containers.StatelessSessionContainer.undeploy(Unknown Source)
    at com.iplanet.ias.server.AbstractLoader.unloadEjbs(Unknown Source)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(Unknown Source)
    at com.iplanet.ias.server.ApplicationLoader.load(Unknown Source)
    at com.iplanet.ias.server.AbstractManager.load(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.loadDeployedApplications(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onStartup(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPostInit(Unknown Source)
    3)Some extra error and warnings follow:
    FINE: No SAS context element found in service context list
    WARNING:
    java.io.IOException: Invalid indirection to offset 2940
    at com.sun.corba.se.internal.io.IIOPInputStream.throwExceptionType(Native Method)
    at com.sun.corba.se.internal.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:274)
    at com.sun.corba.se.internal.io.ValueHandlerImpl.readValueInternal(ValueHandlerImpl.java:247)
    at com.sun.corba.se.internal.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:209)
    at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(Unknown Source)
    at com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(Unknown Source)
    at com.sun.corba.ee.internal.corba.AnyImpl.read_value(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(Unknown Source)
    at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Unknown Source)
    at javax.rmi.CORBA.Util.readAny(Util.java:90)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
    FINE:
    org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Invalid
    indirection to offset 2940 vmcid: SUN minor code: 211 completed: Maybe
    at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(Unknown Source)
    at com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(Unknown Source)
    at com.sun.corba.ee.internal.corba.AnyImpl.read_value(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(Unknown Source)
    at com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(Unknown Source)
    at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Unknown Source)
    at javax.rmi.CORBA.Util.readAny(Util.java:90)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(Unknown Source)
    at com.sun.corba.ee.internal.iiop.ORB.process(Unknown Source)
    at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(Unknown Source)
    at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
    FINE: ++++ Entered SecClientRequestInterceptor::receive_exception
    SEVERE: RSR5049:Error publishing JDBC connection Pool Resource
    javax.naming.CommunicationException: java.rmi.MarshalException: CORBA
    MARSHAL 1398079699 Maybe; nested exception is:
    org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 211 completed:
    Maybe
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(Unknown Source)
    at javax.naming.InitialContext.rebind(InitialContext.java:367)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResource(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJDBCConnectionPoolResources(Unknown Source)
    at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.run(Unknown Source)
    at com.sun.enterprise.server.J2EEServer.main(Unknown Source)
    at com.iplanet.ias.server.ApplicationServer.onInitialization(Unknown Source)
    at com.iplanet.ias.server.J2EERunner.confPreInit(Unknown Source)
    FINE: ++++ Entered SecClientRequestInterceptor::send_request()
    FINE: Security context is null (nothing to add to service context)
    FINE: No SAS context element found in service context list

    Hi Rohit,
    Thanks for your response..
    Below is the BLAdminTopic configuration.Please let me know if you need any further info.
    Topic:BLAdminTopic
    Type:Distributed Topic
    JNDI:jms/BLAdminTopic
    Sub Deployment :N/A
    Target:N/A
    BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
    BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
    Regards,
    Jyotiranjan

  • Why the host ports are also seen in the spanning-tree output ?

    Why the host ports are also seen in the spanning-tree output ?
    Switch1#show spann
    VLAN0001
      Spanning tree enabled protocol ieee
      Root ID    Priority    32769
                 Address     0000.0CA2.138B
                 This bridge is the root
                 Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    32769  (priority 32768 sys-id-ext 1)
                 Address     0000.0CA2.138B
                 Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  20
    Interface        Role Sts Cost      Prio.Nbr Type
    Fa0/1            Desg FWD 19        128.1    P2p
    Fa0/2            Desg FWD 19        128.2    P2p
    Fa0/15           Desg FWD 19        128.15   P2p
    interface FastEthernet0/15
    description PC0 Interface
    switchport mode access
    spanning-tree portfast
    interface FastEthernet0/16
    I read somewhere that all the ports of a switch will participate in STP by default. Is there any way to remove the STP operation on host ports ?
    Regards,
    Chandu       

    All ports participate in Spanning Tree by default.
    Spanning tree is there to block redundant L2 paths in order to prevent loops. All ports are capable of causing a loop so you would not want to turn spanning tree off, in fact I don't think you can switch it off on a per port basis. You can switch it off on a per vlan basis.
    You are already using portfast which allows host ports to transition into a forwarding state without going through the listening and learning states of STP. If you switch off STP on a port, you risk the chance of a L2 loop.
    https://supportforums.cisco.com/docs/DOC-5180

  • Stack dump while trying to view the JNDI Tree on a managed server.

    Hi,
    We are running WLI 9.2.3.
    I have a problem when trying to view the managed servers JNDI Tree via the Admin console. The admin servers JNDI tree appears to be fine, but trying to view the 1st managed servers JNDI Tree via the admin console keeps producing a stack dump.
    Does anyone know why this would be? Is it a security issue, judging by the classes below:
    ####<Jul 14, 2010 1:31:29 PM BST> <Warning> <RMI> <sofatd2b> <tgri02_rsk_ms11> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel
    <> <> <1279110689890> <BEA-080004> <An error was thrown by rmi server: weblogic.jndi.internal.RootNamingNode.listBindings(Ljava.lang.String;Ljava.util.Hashtable;)java.lang.StackOverflowError.
    java.lang.StackOverflowError
    at $Proxy5.isAccessAllowed(Unknown Source)
    at com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed(AccessDecisionServiceImpl.java:105)
    at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
    at $Proxy11.isAccessAllowed(Unknown Source)
    at com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed(AuthorizationServiceImpl.java:81)
    at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
    at $Proxy13.isAccessAllowed(Unknown Source)
    at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:461)
    at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:524)
    at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:414)
    at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:394)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:169)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)

    Hi,
    if it works in Chrome then this Problem is related to IE.
    Maybe the URL is to long? IE can "only" handle 2048 Characters.
    Regards
    -Seb.

Maybe you are looking for

  • Error message when trying to share to Facebook from PE10

    I am getting an error message when trying to share video to Facebook.  Has anyone else gotten this message?  It doesn't seem to want to go away.

  • Packaging a PDF with Files and Hyperlinks

    Hello, Google keeps coming up empty when I search for the solution ad I can't seem to find anything in these forums either, but hopefully one of you will be able to help me out. I want to provide a client with a zip archive containing the PDF I'm wor

  • 9iAS server how to use servlet

    While using 9ias there are two types of running the application one through cgi and another through servlet. The default examples are in cgi. while i am running through cgi everything is fine whereas if i use servlet i am unable to run or proceed and

  • F4 Valuehelp with own dataelement in ALV

    Hi out there, i createt own dataelement with own domain. in domain there are fixed values. Now i designed an itab for alv grid. (abap oo methods). Unfortunately the F4 Help does not appear. How to config the corresponding fieldcat?   CLEAR ls_fieldca

  • Deploying a JAX-WS web service in Weblogic 10

    I created a web service starting from a WSDL, using the wsdlc and jwsc Ant tasks to build and package my web service, and the deploy Ant task for deployment. These steps used to work fine! However now I'm getting the following error during deployment