Deployment problem in managed server environment

          I have a problem deploying a connector as a .rar-file. The file contains the two deployment
          descriptors and a .jar-file containing the connector classes. If I deploy the connector
          in a non-managed server (for instance the admin server), there is not a problem at
          all. But if I deploy the connector to a server that is managed I get an exception
          indicating that the resource manager could not find my javax.resource.spi.ManagedConnectionFactory
          implementation.
          If I put the .jar-file containing my connector implementation classes into the system
          classpath when booting the managed server, the problem is solved. The problem is
          that I don't want this .jar-file in the system classpath.
          Is this a known bug with any workarounds?
          Environment:
          Windows 2000
          WLS 6.1 SP 3
          JDK 1.3.1
          

          Hi Leif,
          I believe that there is a patch that resolves this problem. Could you please ask
          BEA Support for the 6.1 SP2 patch called CR078437_61sp2.jar. You would need to
          put this .jar on the front of your WLS classpath. This patch was created for 6.1
          SP2 but I believe should work for SP3 as well.
          Deb
          >As I wrote:
          >WLS 6.1 SP 3
          >
          >"Jim Gish" <[email protected]> wrote:
          >>What version (including service pack number) of Weblogic Server are
          >you
          >>using?
          >>
          >>"Leif Kristian Vadseth" <[email protected]> wrote in message
          >>news:[email protected]...
          >>>
          >>> I have a problem deploying a connector as a .rar-file. The file contains
          >>the two deployment
          >>> descriptors and a .jar-file containing the connector classes. If I
          >>deploy
          >>the connector
          >>> in a non-managed server (for instance the admin server), there is
          >not
          >>a
          >>problem at
          >>> all. But if I deploy the connector to a server that is managed I get
          >>an
          >>exception
          >>> indicating that the resource manager could not find my
          >>javax.resource.spi.ManagedConnectionFactory
          >>> implementation.
          >>>
          >>> If I put the .jar-file containing my connector implementation classes
          >>into
          >>the system
          >>> classpath when booting the managed server, the problem is solved.
          >The
          >>problem is
          >>> that I don't want this .jar-file in the system classpath.
          >>>
          >>> Is this a known bug with any workarounds?
          >>>
          >>> Environment:
          >>> Windows 2000
          >>> WLS 6.1 SP 3
          >>> JDK 1.3.1
          >>>
          >>
          >>
          >
          

Similar Messages

  • Portal Application deployment problem to Managed Web Server

    I'm trying to deploy an ADF application using JSR168 portlets to a Managed Web Server on WebCenter 11g and I'm getting the following error in the log file after running the portal.jsp (I get 'Portlet unavailable' on the browser page):
    oracle.adf.model.portlet.binding.PortletBindingException: The metadata for portlet binding TasksPortlet1_1 was not found in MDS.
    When I deploy the application from JDeveloper to the Managed Web Server I get the following error (The application does deploy successfully):
    Error during portlet export. Portlets will not be available in the target application. Context: input mds repository file path = C:\JDeveloper\mywork\Mindflow\mds. output mds repository file path = C:\JDeveloper\mywork\Mindflow\.mdsExport. input connections file path and name = /C:/JDeveloper/mywork/Mindflow/.adf/META-INF/connections.xml. export ID = /oracle/adf/portlet/export. producer/portlet IDs to export: [oracle/adf/portlet/MindFlowWsrpPortletProducer].
    However if I right-click on the portal.jsp page and select Run from JDeveloper and run it within the Integrated WLS it does run fine there.
    Is there something special that needs to be set for the Deployment on either the application or project? Or is there something that needs to be setup via the web-based Adminstrative Console (I have verified that the MindFlowWsrpPortletProducer is registered on the Admin console)?
    Thanks,
    Randy Skold

    Thanks for the reply ... here is the answer to your questions along with an update to some more information after trying something different
    Did you deploy the WebCenter Managed server from Jdeveloper
    I am deploying the application to the WebCenter Managed server from JDeveloper.
    What managed server did you deploy it to - a custom server that you created?
    Yes this is a custom Managed Server (called MindFlow). At the time of your response the only two servers up and running on WebCenter was the AdminServer and MindFlow.
    Did the deployment go through?
    Yes
    Are there any errors in the managed server log when you access the page?
    Yes these where the errors showing that it could not connect with the metadata via the repositories.
    Now for the update:
    I went ahead and started up the WLS_Portlet managed server that comes with WebCenter. When I did this I got the following error:
    WSM-04509: cannot initialize the connection to the data store
    I then deployed the Portlet Producer Application to the WLS_Portlet from JDeveloper. I then grabbed the url for the newly created portlet producer and updated the connection on the Portal application. After doing this and updating the portal.jspx file, I then deployed the Portal application to the MindFlow managed web server. I then brought up the portal.jspx page via a browser and was able to bring back results. The only issue now is that while doing this I got multiple MDS errors (including the initialize error above) and not sure if I can ignore these or not. One of the errors received was as follows:
    oracle.mds.exception.MDSException: MDS-01258: The value @MDS_CLASS for property class-name is invalid.

  • Error 401--Unauthorized when deployed on WL Managed server (10.3.3)

    Hi,
    I created & started a WL-Managed server on my window desktop machine. I deployed to this Managed server, an application which is running without problem on Admin Server. (The managed server is created in the same Domain as that of Admin Server)
    However, when I log on to the application on Managed server & enter the UID & PW I get the Error 401--Unauthorized page. The same security works perfectly well for Admin Server.
    Any clues what could be going wrong.
    Thanks in advance.
    Edited by: Prakash Chavan on Feb 28, 2011 4:57 PM

    Thanks Faisal,
    Here is the log after I add the 2 flags
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
    e changed to RUNNING>
    <Mar 1, 2011 8:59:30 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server star
    ted in RUNNING mode>
    Mar 1, 2011 9:13:27 AM oracle.jbo.uicli.mom.CpxUtils$Visitor logMainApplicationC
    px
    INFO: zip:C:/JDev11g/Middleware/user_projects/domains/base_domain/servers/Svr0/t
    mp/_WL_user/TestTrackApp_V2.0/77qs7f/war/WEB-INF/lib/_wl_cls_gen.jar!/view/DataB
    indings.cpx
    [JpsAuth] Check Permission
    PolicyContext: [TestTrackApp#V2.0]
    Resource/Target: [view.pageDefs.ttsPageDef]
    Action: [view]
    Permission Class: [oracle.adf.share.security.authorization.RegionP
    ermission]
    Result: [FAILED]
    For more information on this failure, please set -Djps.auth.debug.verb
    ose=true
    I have emailed you the requested log & the config files.
    Edited by: Prakash Chavan on Mar 1, 2011 9:35 AM

  • Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

    Hi Gurus,
    We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
    Issue:
    When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
    We have tried the following:
    1. We updated the HSS_COMPONENT_PROPERTY_VALUE table  and updated the PROPERTY_NAME "isCompact" to false.
    2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
    We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
    Thanks in advance.

    As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
    There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
    you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
    Hyperion Planning - Version 11.1.2.2.300 and later
    Information in this document applies to any platform.
    Goal
    The scenario:
    EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
    Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
    The administrator went ahead and redeployed the application servers individually into their own JVM.
    However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
    The aim:
    It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
    Solution
    Caution:
    Make sure that you take a backup of the following:
    - TheFoundation Services database schema backup
    - Take a backup of the following folders:
    \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    Disclaimer:
    This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
    Use at your own discretion.
    Procedure:
    1- Run the epmsys_registry to generate the Registry report
    2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
    i.e:
    Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
    3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                    Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
                    run the command:
                     epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                    Repeat this command for each ObjectID that has its applicationServerDeployment
                     property set to Configured
    4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
    5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
    Take note of the first ObjectID entry in the section header: for example
    WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
    Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Start a command prompt and set the working directory to
                     \Oracle\Middleware\user_projects\epmsystem1\bin
    - run the command:
                     epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    -Note the Parents ID in the output:
    For example:
    Parent 1
    NAME -  WORKSPACE_LWA
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    TYPE -  LOGICAL_WEB_APP
    Parent 2
    NAME -  HOST:BACHVMPS3TR
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    TYPE -  HOST
    - Note the single child ID:
    For Example:
    Child 1
    NAME -  WebLogic 10
    ID -  e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    TYPE -  APP_SERVER
    Now run the following command to remove the Link between Parent and child:
    epmsys_registry removelink #parentObjectID #childObjectID
    In this example that would translate to:
    To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
    And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
    #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
    epmsys_registry deletecomponent #parentObjectID
    In this example:
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
    - Delete also the Parent representing the WORKSPACE_LWA
    epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
    Note:So we have now deleted the WEBAPP and LWA for workspace.
    6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
    7- Start the Weblogic admin console and login
    Then go to the left panel and Expand Environment -> Server
    Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
    Activate Changes and Log off
    8- Stop the weblogic admin console server
    9- Go to the following location and delete the folder EPMServer0:
    \Oracle\Middleware\user_projects\domains\EPMSystem\servers
    Delete also EPMServer0 from the following location:
    \Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
    10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
    Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
    Run the following command: sc delete HyS9EPMServer_FOUNDATION1
    11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
    12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
    13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
    14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
    Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
    15- Start the services and test the workspace

  • Deploying application on managed server

    Hi All,
    I am using Weblogic 6.1sp1 on windows 2000.
    I have 2 servers
    server name type port
    myserver - admin server 7001
    vijay - managed server 19001
    when i start myserver & then vijay(managed server) It starts ok works fine.But
    if try to deploy application on managed server & then try to restart both my managed
    server just hangs by giving message.
    Starting WebLogic Server ....
    Connecting to http://localhost:7001...
    <Jan 24, 2002 12:18:04 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
    Server "vijay" for domain "mydomain">
    It doesn't throw any exceptions but it just hangs.
    so will u able to guide me on this.
    Thanx
    Vijay

    Vijay,
    are you using the node manager and starting the server from the admin console?
    The node manager starts this as a process and sometimes the process is not getting
    killed. try to kill the previously started process and it should work fine
    ANIL
    "vijay" <[email protected]> wrote:
    >
    Hi All,
    I am using Weblogic 6.1sp1 on windows 2000.
    I have 2 servers
    server name type port
    myserver - admin server 7001
    vijay - managed server 19001
    when i start myserver & then vijay(managed server) It starts ok works
    fine.But
    if try to deploy application on managed server & then try to restart
    both my managed
    server just hangs by giving message.
    Starting WebLogic Server ....
    Connecting to http://localhost:7001...
    <Jan 24, 2002 12:18:04 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
    Managed
    Server "vijay" for domain "mydomain">
    It doesn't throw any exceptions but it just hangs.
    so will u able to guide me on this.
    Thanx
    Vijay

  • EPM 11.1.2.x deployment to single managed server

    Hi Gurus,
    I have 2 questions:
    1) If we install some applications on single port number:9000(deploy to single managed server), after that if we deploy some applications to individual ports. is this installation work?
    2) for example we have installed and configured all applications to single managed server:9000. Now can we change this to individual port numbers??
    I mean can we configure all application to individual port numbers??
    Just asking with curiosity to know about this scenarios.
    Thanks,
    mady

    Hi Pablo,
    Hope you are doing good. In Starting of Carrer on Hyperion, JohnGoodwin and Your replies on the Forum was very helpful to me.  Nowadays,you are busy i think, and we are not getting more responses from you .
    Pablo wrote:
    If what you're trying to do is deploy everything to 9000, test that and then deploy everything to its own managed server, the answer is yes you can but you need to re-run the OHS configuration at the end everytime as it will need to update the mod_wl_ohs.conf file to update the ports/# of managed servers.
    Pablo
    In the response, Can we get any conflict between services if we do reconfigure to the Own managed server.?
    (why i am asking this question is, at the time of configuration to single managed server, we get EPM Server Service, then some more services only. But if we do reconfigure to the Own managed server, we will get more services in Services.msc)
    I didn't test this yet, just i got this doubt if we do like this what will happens. is it work or not?
    Thanks for your valuable time Pablo.
    Thanks,
    mady

  • Problems on managed server

    hi,
    im currently working on "sales quote demo" project for learning oracle Bpm 11g. I deployed SOATestDemoApp.ear on managed server(soa_server1) as an application by using weblogic console and when ii tried to invoke servlet by the folling URL,
    http://localhost:8001/integration/SOADemoCommunity/DemoCommunitySeedServlet, i didnt get any error message , but it progressing very long time.
    My question is When to start the managed server as because we deployed "SOATestDemoApp" on managed server and how we know that it can receive our request. Is it required to run the managed server while configure Jms and Database resource.
    please help me to understand the concept behind Admin and managed server.
    regards
    ashok.v

    hi,
    im currently working on "sales quote demo" project for learning oracle Bpm 11g. I deployed SOATestDemoApp.ear on managed server(soa_server1) as an application by using weblogic console and when ii tried to invoke servlet by the folling URL,
    http://localhost:8001/integration/SOADemoCommunity/DemoCommunitySeedServlet, i didnt get any error message , but it progressing very long time.
    My question is When to start the managed server as because we deployed "SOATestDemoApp" on managed server and how we know that it can receive our request. Is it required to run the managed server while configure Jms and Database resource.
    please help me to understand the concept behind Admin and managed server.
    regards
    ashok.v

  • Problem with Managed Server pointing to a different JDK

    Hi,
    My Adminserver is pointing to JDK 1.7 which is shown in the startup, but my managed servers are pointing to a different 1.6_43 . We are running into Java version mismatch problem while deploying our application built with jdk 1.7 onto these managed servers . How do i change the version of my managed server ?
    Thanks
    Sam

    Hi Sam,
    You generally only have to change it in two places.
    DOMAIN_HOME/bin/setDomainEnv.sh and MW_HOME/wlserver_12.1/common/bin/commEnv.sh
    See examples below.
    If you are on Linux you can quickly fix it. For example:
    cd /u01/app/oracle/product/fmw
    find . -type f -exec sed -i "s/\/u01\/app\/oracle\/product\/jdk1.6.0_39/\/u01\/app\/oracle\/product\/java_current/g" {} \;
    It is a good idea to make a softlink to your Java installation, then you will not have this problem in the future. If you are on Windows you can use a symlink.
    Linux example:
    ln -s /u01/app/oracle/product/jdk1.7.0_25 /u01/app/oracle/product/java_current
    Windows example:
    mklink /d D:\oracle\product\java_current D:\oracle\product\jrockit-jdk1.6.0_26-R28.1.4-4.0.1
    setDomainEnv.sh
    /u01/app/oracle/domains/eksudv/bin/setDomainEnv.sh
    if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
            JAVA_HOME="${BEA_JAVA_HOME}"
            export JAVA_HOME
    else
            if [ "${JAVA_VENDOR}" = "Sun" ] ; then
                    JAVA_HOME="${SUN_JAVA_HOME}"
                    export JAVA_HOME
            else
                    JAVA_VENDOR="Sun"
                    export JAVA_VENDOR
                    JAVA_HOME="/u01/app/oracle/product/java_current"
                    export JAVA_HOME
            fi
    fi
    commEnv.sh
    /u01/app/oracle/product/fmw/wlserver_12.1/common/bin/commEnv.sh
    # Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
    # and JAVA_VENDOR are pre-defined.
    if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
      # Set up JAVA HOME
      JAVA_HOME="/u01/app/oracle/product/java_current"
      # Set up JAVA VENDOR, possible values are
      #Oracle, HP, IBM, Sun ...
      JAVA_VENDOR=Sun
      # PRODUCTION_MODE, default to the development mode
      PRODUCTION_MODE=""
    fi
    Regards Peter
    http://theheat.dk

  • Problems starting managed server via nodemanager

    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !
    Falko Zurell - Webmaster
    Pixelpark AG
    Germany

    nodemanager must be using the old jvm (1.2.2 or whatever comes by
    default with 2.8). set up the environment or modify
    startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
    o.
    Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !

  • How to use jspx deployed in different managed server from bpm work space

    Hi,
    I have created and deployed my view project having all the jspx files and managed beans into a different managed server(created a new server,not into the soa server).
    I have created a bpm process and now I want to use the jspx page(deployed into the new managed server) in my bpm wrokspace.
    Can anyone help me how I can do it.
    thanks in advance.
    Regards,
    Tukuna

    Hi ,
    I tried with the below url and still i am not able to open the jspx page deployed into the admin server.
    http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/bp_designtf.htm#BDCFBJIE
    28.8.4 How To Deploy a Task Form to a non-SOA Oracle WebLogic Server
    Any help on this is appreciatable.
    Many thanks
    Tuku

  • Error while deploying to Production Managed Server

    My setup is one Domain, one AdminServer, one Managed Server all running in Production Mode.. The AdminServer:7001 and ManagedServer:7003 are on the same box.
    I can deploy my app and hit it via a web service on AdminServer:7001 but I can't hit is on the ManagedServer:7003.
    What happens is I tell the ODSI Admin Console to target the application to either ManagedServer or ManagedServer and AdminServer. Doing this put's the ManagedServer into an Admin STANDBY mode, lists the following error, and remains in an UNKNOWN state. I eventually have to shut the ManagedServer down and start it again.
    The server is running on the latest version of Oracle Mission Control 3.1.0 with the version of JRockit that's in there (1.6.0_11 R27.6.3).
    I mean, I'd rather not run the application on the AdminServer. Does anyone have any suggestions on what to look into to try to trouble shoot this issue??
    ####<Sep 16, 2009 10:02:46 AM EDT> <Error> <Deployer> <computername> <XYZ_ManagedServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1253109766565> <BEA-149231> <Unable to set the activation state to true for the application 'OraclePackage2_request_handlers'.
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
         at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
         at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:292)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:194)
         at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:66)
         at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >

    Hey ,Can you please help me?can you tell me how you resolved this issue.Our production is down due to
    java.lang.IllegalArgumentException: Session: null does not exist.
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:118)
         at com.bea.dsp.management.persistence.primitives.ServerPersistencePrimitives.getDataspaceRoot(ServerPersistencePrimitives.java:73)
         at com.bea.dsp.management.activation.ActivationService.dataSpaceAlreadyExists(ActivationService.java:342)
         at com.bea.dsp.management.activation.ActivationService.setRequestHandlerClassLoader(ActivationService.java:206)
         at com.bea.ld.server.bootstrap.RequestHandlerListener.postStart(RequestHandlerListener.java:46)
         Truncated. see log file for complete stacktrace.
    Its urgent plz

  • Problems starting Managed Server on WL6.0 Solaris

    Hi,
    I installed a WL6.0 on Solaris 8. Everythings works fine.
    I careated a Domain and an additional Server wich is located at a
    different machine. As is start this managed server on the other machine
    it complains with the following error message:
    <Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
    from user.>
    Enter password to boot WebLogic server:weblogic
    Starting WebLogic Server ....
    Connecting to http://sol23:7001...
    The WebLogic Server did not start up properly.
    Exception raised:
    weblogic.management.configuration.ConfigurationException: paros not
    found
    weblogic.management.configuration.ConfigurationException: paros not
    found
    at
    weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
    at weblogic.management.Admin.initialize(Admin.java:287)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    In the access-Log of the Admin-Server the following line appears
    my IP - - [30/Aug/2001:12:41:13 +0200] "GET
    /wl_management_internal2/Bootstrap HTTP/1.0" 404 0
    So my question: Where does this "wl_management_internal2" Application
    come from?
    Do I have to install some special things when I start an Admin-Server?
    thanks
    Falko Zurell . Webmaster
    Pixelpark AG . http://www.pixelpark.com
    Rotherstrasse 8 . 10245 Berlin . Germany
    phone: + 49 30 5058 - 1963 . fax: -1600

    Hi Falko,
    This is not a problem. when you want to add a new managed server to the
    admin server, you need to use weblogic console to create that server in the
    admin server first, then start the managed server with that name to connect
    to the admin server. That is like you have to let the admin server know
    there is such a server, then let it join to the Admin server. you can do
    that by using the admin console, from left panel, click on Servers -->
    "Create a new server" and name it to be "paros", specify the port and IP.
    and hit "create". then start the managed server.
    Thanks
    Yu
    "Falko Zurell" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I installed a WL6.0 on Solaris 8. Everythings works fine.
    I careated a Domain and an additional Server wich is located at a
    different machine. As is start this managed server on the other machine
    it complains with the following error message:
    <Aug 30, 2001 12:41:18 PM CEST> <Info> <Security> <Getting boot password
    from user.>
    Enter password to boot WebLogic server:weblogic
    Starting WebLogic Server ....
    Connecting to http://sol23:7001...
    The WebLogic Server did not start up properly.
    Exception raised:
    weblogic.management.configuration.ConfigurationException: paros not
    found
    weblogic.management.configuration.ConfigurationException: paros not
    found
    at
    weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
    at weblogic.management.Admin.initialize(Admin.java:287)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    >
    In the access-Log of the Admin-Server the following line appears
    my IP - - [30/Aug/2001:12:41:13 +0200] "GET
    /wl_management_internal2/Bootstrap HTTP/1.0" 404 0
    So my question: Where does this "wl_management_internal2" Application
    come from?
    Do I have to install some special things when I start an Admin-Server?
    thanks
    Falko Zurell . Webmaster
    Pixelpark AG . http://www.pixelpark.com
    Rotherstrasse 8 . 10245 Berlin . Germany
    phone: + 49 30 5058 - 1963 . fax: -1600

  • Problem starting managed server in Cluster

    Hi,
    I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
    The WebLogic Server encountered a critical failure
    Reason: Assertion violated
    Exception in thread "main" java.lang.NoClassDefFoundError
    at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
    at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
    at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
    at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
    at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
    at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
    at weblogic.Server.main(Server.java:67)
    Could you pl tell the reason of this error?
    Thanks in advance
    Hi,
    Can anybody help?
    Edited by: user10680571 on Dec 4, 2008 4:42 AM

    Thanks David.
    During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
    <04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    Thanks for your help.....

  • Document.passivate() giving problem in the server environment

    I am having two J2EE web applications accessing PDF forms using LiveCycle API. They both are invoking a short-lived process with RenderPDFForm service that takes form and formdata and renders a PDF form. The code where these applications communicate with Livecycle server is same for both the apps. The applications work fine in the local environment. But in the server environment, one of them work and the other fails with security certificate exception. These applications are deployed to the same server. The application that fails is failing during document.passivate() call. Here is the log message.
    com.adobe.idp.DocumentError: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path validation failed: java.security.cert.CertPathValidatorException: The certificate expired at Wed Jul 01 15:28:21 CDT 2009; internal cause is:
    java.security.cert.CertificateExpiredException: NotAfter: Wed Jul 01 15:28:21 CDT 2009
    at com.adobe.idp.Document.passivateInitData(Document.java:1562)
    at com.adobe.idp.Document.passivate(Document.java:1241)
    at com.adobe.idp.Document.passivate(Document.java:1185)
    at com.adobe.idp.DocumentManagerClient.passivate(DocumentManagerClient.java:236)
    at com.adobe.idp.dsc.provider.impl.base.RequestOutputStream.defaultPassivate(RequestOutputSt ream.java:40)
    at com.adobe.idp.DocumentRequestOutputStream.passivate(DocumentRequestOutputStream.java:56)
    at com.adobe.idp.Document.writeObject(Document.java:872)
    I know it looks like a security certificate exception. But the rest of the application work just fine. The application fails only during document.passivate().
    Any ideas ?
    Thanks,
    Jytohi

    I am having two J2EE web applications accessing PDF forms using LiveCycle API. They both are invoking a short-lived process with RenderPDFForm service that takes form and formdata and renders a PDF form. The code where these applications communicate with Livecycle server is same for both the apps. The applications work fine in the local environment. But in the server environment, one of them work and the other fails with security certificate exception. These applications are deployed to the same server. The application that fails is failing during document.passivate() call. Here is the log message.
    com.adobe.idp.DocumentError: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: PKIX path validation failed: java.security.cert.CertPathValidatorException: The certificate expired at Wed Jul 01 15:28:21 CDT 2009; internal cause is:
    java.security.cert.CertificateExpiredException: NotAfter: Wed Jul 01 15:28:21 CDT 2009
    at com.adobe.idp.Document.passivateInitData(Document.java:1562)
    at com.adobe.idp.Document.passivate(Document.java:1241)
    at com.adobe.idp.Document.passivate(Document.java:1185)
    at com.adobe.idp.DocumentManagerClient.passivate(DocumentManagerClient.java:236)
    at com.adobe.idp.dsc.provider.impl.base.RequestOutputStream.defaultPassivate(RequestOutputSt ream.java:40)
    at com.adobe.idp.DocumentRequestOutputStream.passivate(DocumentRequestOutputStream.java:56)
    at com.adobe.idp.Document.writeObject(Document.java:872)
    I know it looks like a security certificate exception. But the rest of the application work just fine. The application fails only during document.passivate().
    Any ideas ?
    Thanks,
    Jytohi

  • WLS 7.0 Active Directory authenticator - problems starting managed server (Solaris 8)

    Has anyone managed to setup a WLS 7.0 Active Directory authenticator and booted
    a managed server using the node manager? I can boot the server without the AD
    authenticator and I can also boot the server using a script and successfully authenticate
    through AD. My AD control flag is set to OPTIONAL and I have also setup a default
    authenticator to boot weblogic - the control flag here is set to SUFFICIENT. This
    configuration works fine with weblogic running on W2K, but not on Solaris (it
    looks like the control flag is being ignored). Errors as follows
    ####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01> <main>
    <kernel identity> <> <000000> <FileLo
    gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
    <kernel identity> <> <000415> <System
    has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
    <kernel identity> <> <000416> <Using e
    ffective file descriptor limit of: 1,024 open sockets/files.>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
    <kernel identity> <> <000418> <Allocat
    ing: 3 POSIX reader threads>
    ####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine> <server01>
    <main> <kernel identity> <> <0003
    64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
    Problem instantiating
    Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
    thrown by the getAttribute method of the Dynam
    icMBean for the attribute Credential>
    weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
    Authentication Providerjavax.management.RuntimeOper
    ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
    for the attribute Credential
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
    at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    ####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine> <server01>
    <main> <kernel identity> <> <000
    342> <Unable to initialize the server: Fatal initialization exception
    Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
    instantiating Authentication Providerjavax.management.
    RuntimeOperationsException: RuntimeException thrown by the getAttribute method
    of the DynamicMBean for the attribute Credential
    weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
    Authentication Providerjavax.management.RuntimeOper
    ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
    for the attribute Credential
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
    at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)

    Solved the problem. The 'domain root' directory specified in the remote start configuration,
    must contain a copy of the file 'SerializedSystemIni.dat' that was created along
    with the domain, in order to boot when an AD authenticator is configured. If an
    AD authenticator is not configured, no file is required. This was not a platform
    specific issue; on Win2K I had configured the 'domain root' remote start parameter
    to point to an existing domain root and not a new directory.
    "Andrew Walker" <[email protected]> wrote:
    >
    Has anyone managed to setup a WLS 7.0 Active Directory authenticator
    and booted
    a managed server using the node manager? I can boot the server without
    the AD
    authenticator and I can also boot the server using a script and successfully
    authenticate
    through AD. My AD control flag is set to OPTIONAL and I have also setup
    a default
    authenticator to boot weblogic - the control flag here is set to SUFFICIENT.
    This
    configuration works fine with weblogic running on W2K, but not on Solaris
    (it
    looks like the control flag is being ignored). Errors as follows
    ####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01>
    <main>
    <kernel identity> <> <000000> <FileLo
    gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
    <main>
    <kernel identity> <> <000415> <System
    has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
    <main>
    <kernel identity> <> <000416> <Using e
    ffective file descriptor limit of: 1,024 open sockets/files.>
    ####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
    <main>
    <kernel identity> <> <000418> <Allocat
    ing: 3 POSIX reader threads>
    ####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine>
    <server01>
    <main> <kernel identity> <> <0003
    64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
    Problem instantiating
    Authentication Providerjavax.management.RuntimeOperationsException:
    RuntimeException
    thrown by the getAttribute method of the Dynam
    icMBean for the attribute Credential>
    weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
    Authentication Providerjavax.management.RuntimeOper
    ationsException: RuntimeException thrown by the getAttribute method of
    the DynamicMBean
    for the attribute Credential
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
    at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    ####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine>
    <server01>
    <main> <kernel identity> <> <000
    342> <Unable to initialize the server: Fatal initialization exception
    Throwable: weblogic.security.service.SecurityServiceRuntimeException:
    Problem
    instantiating Authentication Providerjavax.management.
    RuntimeOperationsException: RuntimeException thrown by the getAttribute
    method
    of the DynamicMBean for the attribute Credential
    weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
    Authentication Providerjavax.management.RuntimeOper
    ationsException: RuntimeException thrown by the getAttribute method of
    the DynamicMBean
    for the attribute Credential
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
    at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
    at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
    at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
    at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)

Maybe you are looking for

  • Unable to create Listener in Repository

    I am doing a base install of CG 5.4 onto a Windows 7 box.  The install goes fine and I shutdown/startup CQ5.  Upon CQ5 server startup, I see the following stacktrace: 09.04.2012 15:58:45 *ERROR* RepositoryStartupServlet: RepositoryStartupServlet init

  • Goods Receipt wrt Outbound delivery and Restrict GR wrt PO!

    Hi, In a scenario of intercompany, i need a functionality! GR should be done only wrt Outbound Delivery but not wrt Purchase order for intercompany document type. Pl. help!

  • How to create a response file for Acrobat 9 Pro?

    I with to collect data from a PDF form made with LiveCycle Designer. The instruction say- After a user submits a form, open the returned form. In the Add Completed Form To Responses File dialog box, select one of the following: I am totally baffled a

  • Gamers Club Unlocked Renewal Question

    Hi Matt, I've been a Gamers Club Unlocked Member since the program started in September of 2011, as well as a pretty consistent Premier Silver( which has now become Elite P'us) member. My Gamer's Club Unlocked membership expires on the 14th of next m

  • Extractor: Check on Accuracy and Completeness

    Our customer asks if we can implement a check on accuracy and completeness of the extractors (from R/3 to BW). Isn't there already a build-in check (CRC or CHECKSUM) that does this automatically. So in general: How is it determined that data from R/3