Weblogic WLST for starting weblogic server

I have created a domain with a single server running Admin Server, SOA and BAM server in the same port.
I would like to start this Server from node manager.
I have started ii with the command nmStart(...), within WLST, I can connect to the ADmin server using connect() command.
But I cannot access the url.
If I start the AdminServer by using startWeblogic.sh then the URL works.
Has anybody tried it?

Hi,
Try this...
[Starting Admin and Managed Servers using Node Manager and WLST | http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html ]
Regards,
Neeraj Sehgal

Similar Messages

  • Why is it recommended to have a separate PeopleSoft ID for starting Application Server in PeopleSoft

    HI,
    Why is it recommended to have a separate PeopleSoft ID for starting Application Server in PeopleSoft

    Hello:
    You can put the JS function into the HTML Header section of the Page defintion.
    <script>
    function doDelete(id) {
    $x('P14_DEL_ID').value=id;
    doSubmit('DELETE');
    </script>Define a new page process whose process point is 'On Submit: After Computations and Validations'. For the Process Source specify
    Delete from <table> where key_column=:p14_del_id;Under Conditional Processing select 'Request=Expression 1'. For Expression 1 specify 'DELETE'
    Hope this helps.
    Varad

  • Urgent Help Required For Starting RMI server from servlet.

    I am currently working on rmi project.
    I want to send request to remote machine(Web host) where my application is from desktop client .For that we are using RMI.
    I am writing servlet and inside it i am binding object to registry for rmi server.
    which will be deployed on remote server.
    code ....
    Registry reg;
    reg=LocateRegistry.createRegistry(1099);
    Server server=new Server("server");//class whose remote object to be accessed
    //extends unicast remote object.Implement ServerInt interface which extends Remote.
    reg.bind("server",server);
    When i am trying to access this object i am getting following exception.
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalExcepti
    on: error unmarshalling return; nested exception is:
            java.lang.ClassNotFoundException: ServerModule.ServerInt]
    at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
    at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at RequstReplication.main(RequstReplication.java:27)
    Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested excep
    tion is:
    java.lang.ClassNotFoundException: ServerModule.ServerInt
    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
    ... 4 more
    Caused by: java.lang.ClassNotFoundException: ServerModule.ServerInt
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyInterfaces(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
    at java.rmi.server.RMIClassLoader$2.loadProxyClass(Unknown Source)
    at java.rmi.server.RMIClassLoader.loadProxyClass(Unknown Source)
    at sun.rmi.server.MarshalInputStream.resolveProxyClass(Unknown Source)
    at java.io.ObjectInputStream.readProxyDesc(Unknown Source)
    at java.io.ObjectInputStream.readClassDesc(Unknown Source)
    at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
    at java.io.ObjectInputStream.readObject0(Unknown Source)
    at java.io.ObjectInputStream.readObject(Unknown Source)
    ... 5 more
    I can access naming enumeration of registry and object bound to it.
    by following program.I shows corect objects.
    Context namingContext=new InitialContext();
    NamingEnumeration<NameClassPair> e=namingContext.list("rmi:");
    while(e.hasMore())
    System.out.println(e.next().getName());
    While when i start RMI server from simple java program i can access these objects from registry.
    I am not getting what is problem problem.Is there any other way to send request?
    Plese give quick response.

    I am currently working on rmi project.
    I want to send request to remote machine(Web host) where my application is from desktop client .For that we are using RMI.
    I am writing servlet and inside it i am binding object to registry for rmi server.
    which will be deployed on remote server.
    code ....
    Registry reg;
    reg=LocateRegistry.createRegistry(1099);
    Server server=new Server("server");//class whose remote object to be accessed
    //extends unicast remote object.Implement ServerInt interface which extends Remote.
    reg.bind("server",server);
    When i am trying to access this object i am getting following exception.
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalExcepti
    on: error unmarshalling return; nested exception is:
            java.lang.ClassNotFoundException: ServerModule.ServerInt]
    at com.sun.jndi.rmi.registry.RegistryContext.lookup(Unknown Source)
    at com.sun.jndi.toolkit.url.GenericURLContext.lookup(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at RequstReplication.main(RequstReplication.java:27)
    Caused by: java.rmi.UnmarshalException: error unmarshalling return; nested excep
    tion is:
    java.lang.ClassNotFoundException: ServerModule.ServerInt
    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
    ... 4 more
    Caused by: java.lang.ClassNotFoundException: ServerModule.ServerInt
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyInterfaces(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
    at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
    at java.rmi.server.RMIClassLoader$2.loadProxyClass(Unknown Source)
    at java.rmi.server.RMIClassLoader.loadProxyClass(Unknown Source)
    at sun.rmi.server.MarshalInputStream.resolveProxyClass(Unknown Source)
    at java.io.ObjectInputStream.readProxyDesc(Unknown Source)
    at java.io.ObjectInputStream.readClassDesc(Unknown Source)
    at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
    at java.io.ObjectInputStream.readObject0(Unknown Source)
    at java.io.ObjectInputStream.readObject(Unknown Source)
    ... 5 more
    I can access naming enumeration of registry and object bound to it.
    by following program.I shows corect objects.
    Context namingContext=new InitialContext();
    NamingEnumeration<NameClassPair> e=namingContext.list("rmi:");
    while(e.hasMore())
    System.out.println(e.next().getName());
    While when i start RMI server from simple java program i can access these objects from registry.
    I am not getting what is problem problem.Is there any other way to send request?
    Plese give quick response.

  • Weblogic Server does not show managed server started when I used the Windows service to start it.

    I created a windows service to start a managed server and the services was created successfully and stated.  WHen I go to the Weblogic Server Admn console, the server is still showing shutdown.  Whenm I try to start it, it returns with error that the the service is not able to start.  Has anyone ran into anything similar.  I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
    C

    Hi,
    For starting managed server as windows service there is no need of nodemanager .
    Please follow the steps given in the below doc:
    How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
    Thanks,
    Sharmela

  • Weblogic server console error.

    HI,
    I am working on weblogic server . I am having only one domain and same domain i am having one managed server and one admin server.
    I can start the managed server from command line but not from the weblogic console.It is showing in shutdown state.Please help what to do? Please suggest some key area to look for this error.I need to deploy application on managed server from console.

    Thanks for the replay..
    1> Is there any way to start any managed server from admin console without configuring node manager.
    2> For my case i have started managed server from command line.
    3>So should i have to configure node manager for starting managed server from console.

  • Chain warning exceptions on weblogic server console

    Hi,
    The below warnings are continuously observed on the weblogic server due to which OSM orders are not getting generated.
    We downloaded a patch available on Oracle Support [12319435] to eradicate this warning on the WLS 10.3.5, however, the issue still persists.
    Moreover, also changed the value of the 'Connection Creation Retry Frequency' to 60 seconds.
    Please help in troubleshooting this issue.
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.100.37.132:31,161 during the configured idle timeout of 5 secs>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.100.37.132:31,160 during the configured idle timeout of 5 secs>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000450> <Socket 44 internal data record unavailable (probable closure due idle timeout), event received -32>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.100.37.132:31,162 during the configured idle timeout of 5 secs>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000450> <Socket 50 internal data record unavailable (probable closure due idle timeout), event received 0>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.100.37.132:31,163 during the configured idle timeout of 5 secs>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000450> <Socket 45 internal data record unavailable (probable closure due idle timeout), event received 0>
    <Nov 6, 2012 11:39:55 AM GST> <Warning> <Socket> <BEA-000450> <Socket 46 internal data record unavailable (probable closure due idle timeout), event received 0>
    <Nov 6, 2012 11:40:40 AM GST> <Warning> <Socket> <BEA-000450> <Socket 47 internal data record unavailable (probable closure due idle timeout), event received 0>
    <Nov 6, 2012 11:40:50 AM GST> <Warning> <Socket> <BEA-000450> <Socket 49 internal data record unavailable (probable closure due idle timeout), event received 0>

    Thanks for the replay..
    1> Is there any way to start any managed server from admin console without configuring node manager.
    2> For my case i have started managed server from command line.
    3>So should i have to configure node manager for starting managed server from console.

  • Issue while enabling Access Control for a Coherence server node

    Hi
    Im trying to enable access control for a Coherence server node, using the default Keystore login method shipped with Coherence. When i start the server i get the error "java.security.AccessControlException: Unsufficient rights to perform the operation". Please see below for the sequence of steps I've followed to enable access control. I just need to be enable Authentication (not authorization) at this stage
    1. I have added the following entry in the Coherence Operational override file
    <security-config>
              <enabled system-property="tangosol.coherence.security">true</enabled>
              <login-module-name>Coherence</login-module-name>
              <access-controller>
                   <class-name>com.tangosol.net.security.DefaultController</class-name>
                   <init-params>
                        <init-param id="1">
                             <param-type>java.io.File</param-type>
                             <param-value>keystore.jks</param-value>
                        </init-param>
                        <init-param id="2">
                             <param-type>java.io.File</param-type>
                             <param-value>permissions.xml</param-value>
                        </init-param>
                   </init-params>
              </access-controller>
              <callback-handler>
                   <class-name>com.sun.security.auth.callback.TextCallbackHandler</class-name>
              </callback-handler>
         </security-config>
    2. The following is the entry in the Permissions.xml
    <?xml version='1.0'?>
    <permissions>
    <grant>
    <principal>
    <class>javax.security.auth.x500.X500Principal</class>
    <name>CN=admin,OU=Coherence,O=Oracle,C=US</name>
    </principal>
    <permission>
    <target>*</target>
    <action>all</action>
    </permission>
    </grant>
    </permissions>
    3. The following is the content of the Login configuration file "Coherence_Login.conf"
    Coherence {
    com.tangosol.security.KeystoreLogin required
    keyStorePath="keystore.jks";
    4. The following is the command line tag for starting the server
    java -server -showversion -Djava.security.auth.login.config=Coherence_Login.conf -Xms%memory% -Xmx%memory% -Dtangosol.coherence.cacheconfig=PROXY-cache-config.xml -Dtangosol.coherence.override=FOL-coherence-override.xml -Dcom.sun.management.jmxremote.port=6789 -Dcom.sun.management.jmxremote.authenticate=false -Dtangosol.coherence.security=true -cp "%coherence_home%\lib\coherence.jar" com.tangosol.net.DefaultCacheServer %1
    Following is the output on the Console when running the command. It asks for a username and password for the JKS store (If i provide the wrong password, it gives a different error, which shows that it is able to authenticate aganst the Keystore). After i put in the password, it throws the error as shown below "java.security.AccessControlException: Unsufficient rights to perform the operation"
    D:\Coherence\FOL_CacheServer>fol-cache-server
    java version "1.6.0_20"
    Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
    Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
    Username:admin
    Password:
    Exception in thread "main" java.security.AccessControlException: Unsufficient ri
    ghts to perform the operation
    at com.tangosol.net.security.DefaultController.checkPermission(DefaultCo
    ntroller.java:153)
    at com.tangosol.coherence.component.net.security.Standard.checkPermissio
    n(Standard.CDB:32)
    at com.tangosol.coherence.component.net.Security.checkPermission(Securit
    y.CDB:11)
    at com.tangosol.coherence.component.util.SafeCluster.ensureService(SafeC
    luster.CDB:6)
    at com.tangosol.coherence.component.net.management.Connector.startServic
    e(Connector.CDB:20)
    at com.tangosol.coherence.component.net.management.gateway.Remote.regist
    erLocalModel(Remote.CDB:10)
    at com.tangosol.coherence.component.net.management.gateway.Local.registe
    rLocalModel(Local.CDB:10)
    at com.tangosol.coherence.component.net.management.Gateway.register(Gate
    way.CDB:6)
    at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluste
    r(SafeCluster.CDB:46)
    at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.C
    DB:2)
    at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:998)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureServiceInterna
    l(DefaultConfigurableCacheFactory.java:923)
    at com.tangosol.net.DefaultConfigurableCacheFactory.ensureService(Defaul
    tConfigurableCacheFactory.java:892)
    at com.tangosol.net.DefaultCacheServer.startServices(DefaultCacheServer.
    java:81)
    at com.tangosol.net.DefaultCacheServer.intialStartServices(DefaultCacheS
    erver.java:250)
    at com.tangosol.net.DefaultCacheServer.startAndMonitor(DefaultCacheServe
    r.java:55)
    at com.tangosol.net.DefaultCacheServer.main(DefaultCacheServer.java:197)

    Did you create the weblogic domain with the Oracle Webcenter Spaces option selected? This should install the relevant libraries into the domain that you will need to deploy your application. My experience is based off WC 11.1.1.0. If you haven't, you can extend your domain by re-running the Domain Config Wizard again (WLS_HOME/common/bin/config.sh)
    Cappa

  • Script for Checking the Server Status

    Hi All,
         I just need the script for monitoring the server status through the WLST.My scenario:I have 2 server in Running State.If any one of the server get failed or in not RUNNING state then i use the script for starting that server automatically.I tried some of the script but it is not working properly .If any one have the sample script please share with me.
    Regards,
    Ove.

    Hi Syed,
    Replication state is very easy to see in 4.x and earlier. The last changenumber in the supplier changelog is visible (on the root DSE IIRC), and each consumer suffix has an operational attribute "copiedfrom" that tells you the name of the supplier, the database generation id, and the last change replayed from the supplier.
    So a script that compares the results of
    ldapsearch -h <supplier> -s base -b "" "objectclass=*" lastchangenumber
    and
    ldapsearch -h <consumer> -s base -b <base_suffix> "objectclass=*" copiedFrom
    will show you if a replica has fallen out of sync. It won't tell you more than how many changes behind the replica is, though, because pre-5.x changenumbers are sequential integers, not timestamps.
    However, the change that corresponds to the changenumber is clearly visible under the "cn=changelog" suffix. So if you look at the change itself you can see the timestamp on it.
    For more info on the status of replication, you should be able to query the agreements on the supplier. Those live under the "Netscape Machine Data Suffix", which you can also find on the supplier's root DSE:
    ldapsearch -h <supplier> -s base -b "" "objectclass=*" netscapemdsuffix
    And of course the error logs will usually tell you if replication is failing outright.
    I may be off on some of the attribute names, but if you do some investigating along these lines, you should be able to figure it out.

  • Starting managed server while admin server is down in 8.1

    Is there a way to bring the server up with script while admin server is down. I see it possible with 11g . How about 8.1?

    http://docs.oracle.com/cd/E13222_01/wls/docs81/cluster/setup.html and
    http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/overview.html
    "If Managed Server Independence is enabled, the Managed Server will start, even though it cannot connect to the Administration Server. "
    you can either do it with the startManagedWeblogic script, or by connecting to the Node Manager with WLST and starting the server.
    Only if MSI is on.
    http://www.wikiconsole.com/wiki/?p=1936

  • Start SQL Server in single user mode with parameter -m doesn't work well

    C:\Windows\system32>net start mssqlserver /m "Microsoft SQL Server Management St
    udio - Query"
    The SQL Server (MSSQLSERVER) service is starting.
    The SQL Server (MSSQLSERVER) service was started successfully.
    C:\Windows\system32>sqlcmd -S . -e
    1> go
    1> select @@servername;
    2> go
    select @@servername;
    myserver
    (1 rows affected)
    1>
    As you can see, I'm still able to connect with sqlcmd prompt to SQL Server. According production doc of SQL Server 2014, it should not be conncting by sqlcmd. it shall only be connected by SSMS.
    below the original doc on msdn:
    Start SQL Server in Single-User Mode
    Provide Feedback
    Under certain circumstances, you may have to start an instance of SQL Server
    in single-user mode by using the startup option -m. For
    example, you may want to change server configuration options or recover a
    damaged master database or other system database. Both actions require starting
    an instance of SQL Server in single-user mode.
    Starting SQL Server in single-user mode enables any member of the computer's
    local Administrators group to connect to the instance of SQL Server as a member
    of the sysadmin fixed server role. For more information, see Connect to
    SQL Server When System Administrators Are Locked
    Out.
    When you start an instance of SQL Server in single-user mode, note the
    following:
    Only one user can connect to the server.
    The CHECKPOINT process is not executed. By default, it is executed
    automatically at startup.
    Note
    Stop the SQL Server Agent service before connecting to an instance of SQL
    Server in single-user mode; otherwise, the SQL Server Agent service uses the
    connection, thereby blocking it.
    When you start an instance of SQL Server in single-user mode, SQL Server
    Management Studio can connect to SQL Server. Object Explorer in Management
    Studio might fail because it requires more than one connection for some
    operations. To manage SQL Server in single-user mode, execute Transact-SQL
    statements by connecting only through the Query Editor in Management Studio, or
    use the
    sqlcmd utility.
    When you use the -m option with sqlcmd or
    Management Studio, you can limit the connections to a specified client
    application. For example, -m"sqlcmd" limits connections to a
    single connection and that connection must identify itself as the
    sqlcmd client program. Use this option when you are starting
    SQL Server in single-user mode and an unknown client application is taking the
    only available connection. To connect through the Query Editor in Management
    Studio, use -m"Microsoft SQL Server Management Studio - Query".
    Shawn

    Hi Shawn Xiao,
    For starting SQL Server instance in single user mode, we can add –m; parameter in SQL Server Configuration Manager, also we can run CMD with ‘Run as administrator’ and input the following statement.
    NET START MSSQLSERVER /m
    I do a test in SQL Server 2014 Express version, after starting SQL with Single User Mode, SQL Server will only accept one connection. If you connect to SQL Server with a user account, the following error will occur.
    Login failed for user ‘domain\username’. Reason: Server is in single user mode. Only one administrator can connect at this time.
    However, in your situation, you can connect to SQL Server and run T-SQL statement successfully, it can be due to connection with the administrator account in your sqlcmd.
    For more information, you can review the following article.
    http://zarez.net/?p=117
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • WLST Failed in Oracle BPM Enterprise for Weblogic Server

    Hi,
    I am not getting any clue of resolving the following issue. We are using Oracle BPM Enterprise for Weblogic # 100141. Error details:-
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    t3://192.68.1.3:
    Connecting to t3://192.168.1.3: with userid weblogic ...
    This Exception occurred at Tue Jul 3 :56: IST .
    weblogic.utils.NestedError: Local host not known?!
         at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:9)
         at weblogic.rjvm.JVMID.localID(JVMID.java:8)
         at weblogic.protocol.LocalServerIdentity$SingletonMaker.<clinit>(LocalServerIdentity.java:3)
         at weblogic.protocol.LocalServerIdentity.getIdentity(LocalServerIdentity.java:)
         at weblogic.server.channels.ServerChannelImpl.createDefaultServerChannel(ServerChannelImpl.java:3)
         at weblogic.rjvm.t3.ProtocolHandlerT3$ChannelInitializer.<clinit>(ProtocolHandlerT3.java:3)
         at weblogic.rjvm.t3.ProtocolHandlerT3.getDefaultServerChannel(ProtocolHandlerT3.java:4)
         at weblogic.protocol.ServerChannelManager$SingletonMaker$.getOutboundServerChannel(ServerChannelManager.java:339)
         at weblogic.protocol.ServerChannelManager.findOutboundServerChannel(ServerChannelManager.java:43)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:3)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:94)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:5)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:88)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:53)
         at weblogic.jndi.WLInitialContextFactoryDelegate$.run(WLInitialContextFactoryDelegate.java:344)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
         at weblogic.jndi.Environment.getContext(Environment.java:35)
         at weblogic.jndi.Environment.getContext(Environment.java:85)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:88)
         at javax.naming.InitialContext.init(InitialContext.java:3)
         at javax.naming.InitialContext.<init>(InitialContext.java:9)
         at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:5)
         at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
         at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:35)
         at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:3)
         at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:6)
         at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:5)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
         at java.lang.reflect.Method.invoke(Method.java:59)
         at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:6)
         at org.python.core.PyMethod.__call__(PyMethod.java:96)
         at org.python.core.PyObject.__call__(PyObject.java:48)
         at org.python.core.PyObject.invoke(PyObject.java:6)
         at org.python.pycode._pyx4.connect$(<iostream>:6)
         at org.python.pycode._pyx4.call_function(<iostream>)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyTableCode.call(PyTableCode.java:44)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyFunction.__call__(PyFunction.java:9)
         at org.python.pycode._pyx6.initConfigToScriptRun$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:5)
         at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyTableCode.call(PyTableCode.java:56)
         at org.python.core.PyFunction.__call__(PyFunction.java:69)
         at org.python.pycode._pyx6.f$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:66)
         at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
         at org.python.core.PyTableCode.call(PyTableCode.java:8)
         at org.python.core.PyCode.call(PyCode.java:4)
         at org.python.core.Py.runCode(Py.java:35)
         at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:6)
         at weblogic.management.scripting.WLST.main(WLST.java:9)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
         at java.lang.reflect.Method.invoke(Method.java:59)
         at weblogic.WLST.main(WLST.java:9)
    Caused by: java.net.UnknownHostException: HOME-MITTAL: HOME-MITTAL
         at java.net.InetAddress.getLocalHost(InetAddress.java:353)
         at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:5)
         ... 6 more
    No server running at t3://192.168.1.3: or the user/password is wrong
    Exiting WebLogic Scripting Tool.
    Even I tried using hostname as "localhost" but still I am facing the same issue.
    Please suggest what is the resolution for the same.
    Thanks,
    Abhishek

    Hi,
    I was getting same excepction when tried to configure weblogic server (10.3.3 and 10gR3) through BPM Configuration Wizard, so I end up doing everything manually, like setting up JDBC data sources, JMS Server, JMS Modules and created DB (Directory & Engine).
    Now, I am stuck at the last step of deploying the EAR files generated using BPM Process Administrator, they EAR's are generated fine but while deploying them to Weblogic server (through BPM Process Administrator), getting following exception (for "01-eng-bpmengine.ear")
    <Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpmengine".
    fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: Invalid column type].
         at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
         at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
         at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
         at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1423)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy246.authenticateHumanParticipant(Unknown Source)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy243.connect(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
         at fuego.directory.provider.Factory.startSession(Factory.java:405)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
         at fuego.directory.Directory.startSession(Directory.java:268)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
         at fuego.ejbengine.Engine.start(Engine.java:122)
         at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.sql.SQLException: Invalid column type
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7975)
         at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
         at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8028)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:238)
         at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:324)
         at fuego.jdbc.FaultTolerantPreparedStatement.setString(FaultTolerantPreparedStatement.java:436)
         at fuego.directory.provider.jdbc.JDBCPersistenceManager.setStringAttribute(JDBCPersistenceManager.java:896)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1417)
         at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy246.authenticateHumanParticipant(Unknown Source)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
         at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
         at $Proxy243.connect(Unknown Source)
         at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
         at fuego.directory.provider.Factory.startSession(Factory.java:405)
         at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
         at fuego.directory.Directory.startSession(Directory.java:268)
         at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
         at fuego.ejbengine.Engine.start(Engine.java:122)
         at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    my assumption is JDBC Data Sources or the Directory/Engine database have some column name mismatch.
    Let me know if somebody has a solution for this, or if I am doing something wrong.
    NOTE: just found out that this happens only on Windows 2003 server, but not on OEL5 (Oracle Enterprise Linux 5).
    Thanks !!

  • Problem getting started weblogic server (for BI Publisher)

    Hello,
    I am trying to run services BI publisher
    But I can't because I have the following error:
    SVR_GRP =
    JAVA Memory arguments: -Xms256m -Xmx1024m
    WLS Start Mode=Production
    CLASSPATH=C:\BI11\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\BI11\Oracle_BI1\bifoundation\jdbc\jdk16\bijdbc.jar;;C:\BI11\patch_wls1035\profiles\defaul
    t\sys_manifest_classpath\weblogic_patch.jar;C:\BI11\JROCKI~1.2-4\lib\tools.jar;C:\BI11\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\BI11\WLSERV~1.3\server\lib\weblo
    gic.jar;C:\BI11\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\BI11\WLSERV~1.3\server\lib\webservices.jar;C:\BI11\modules\ORGAPA~1.1/lib/ant-all.jar;C
    :\BI11\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\BI11\wlserver_10.3\server\lib\weblogic.jar;C:\BI11\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\BI11\or
    acle_common\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\BI11\oracle_common\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\BI11\oracle_common\modules\oracle.odl_11.1.
    1\ojdl.jar;C:\BI11\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\BI11\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\BI11\ORACLE~1\modules\orac
    le.jrf_11.1.1\jrf.jar;C:\BI11\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\BI11\WLSERV~1.3\server\lib\xqrl.jar
    PATH=C:\BI11\patch_wls1035\profiles\default\native;C:\BI11\WLSERV~1.3\server\native\win\32;C:\BI11\WLSERV~1.3\server\bin;C:\BI11\modules\ORGAPA~1.1\bin;C:\BI11\
    JROCKI~1.2-4\jre\bin;C:\BI11\JROCKI~1.2-4\bin;C:\oracle11g\dbhome\bin;C:\;C:;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\VAIO;C:\Program Files\Ja
    va\jre6\bin;;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\E900\system\bin32;C:\E900\DEMO\bin32;C:\BI11\Oracle_BI1\products\Essbase\EssbaseServer\bin;
    C:\BI11\Oracle_BI1\bin;C:\BI11\Oracle_BI1\opmn\bin;C:\BI11\Oracle_BI1\opmn\lib;C:\BI11\Oracle_BI1\perl\bin;C:\BI11\WLSERV~1.3\server\native\win\32\oci920_8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32,
    compiled mode)
    Starting WLS with line:
    C:\BI11\JROCKI~1.2-4\bin\java -jrockit -Xms256m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\BI11\WLSERV~1.3\server\lib\weblogic.policy -D
    weblogic.ProductionModeEnabled=true -Doracle.home=C:\BI11\Oracle_BI1 -da -Dplatform.home=C:\BI11\WLSERV~1.3 -Dwls.home=C:\BI11\WLSERV~1.3\server -Dweblogic.hom
    e=C:\BI11\WLSERV~1.3\server -Dcommon.components.home=C:\BI11\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk
    14Logger -Ddomain.home=C:\BI11\USER_P~1\domains\BIFOUN~1 -Djrockit.optfile=C:\BI11\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config
    .dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\servers\AdminServer -Doracle.domain.config.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1 -Digf.a
    risidbeans.carmlloc=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\arisidprov
    ider -Doracle.security.jps.config=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\
    servers\AdminServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\BI11\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\BI11\ORACLE~1
    \modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=C:\BI11\Oracle_BI1
    -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -DHYPERION_HOME=C:\BI11\Oracle_BI1 -DEPM_ORACLE_IN
    STANCE=novalue -Dhyperion.home=C:\BI11\Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig -Depm.useApplicationContextId=fal
    se -Doracle.biee.search.bisearchproperties=C:\BI11\Oracle_BI1\bifoundation\jee\BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=
    true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.enc
    oding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BIS
    earchServiceConfiguration -Dxdo.server.config.dir=C:\BI11\user_projects\domains\bifoundation_domain\config\bipublisher -DXDO_FONT_DIR=C:\BI11\Oracle_BI1\common\
    fonts -Dem.oracle.home=C:\BI11\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dw
    lw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:\BI11\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    <Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable thi
    s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl
    e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true><Apr 10, 2012 3:07:12 PM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting We
    bLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32 from Oracle Corporation>
    <Apr 10, 2012 3:07:12 PM CEST> <Info> <Management> <BEA-141107> <Version: Weblogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Apr 10, 2012 3:07:14 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Apr 10, 2012 3:07:14 PM CEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Apr 10, 2012 3:07:15 PM CEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\BI11\user_projects\domains\bifoundation_domain\servers\AdminServer
    \logs\AdminServer.log is opened. All server side log events will be written to this file.>
    Apr 10, 2012 3:07:23 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd
    SEVERE: JPS-02592
    <Apr 10, 2012 3:07:23 PM CEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception sta
    ck trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Er
    ror message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseExcep
    tion: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
    <Apr 10, 2012 3:07:23 PM CEST> <Critical> <WebLogicServer> <BEA-000386> <Serversubsystem failed. Reason: weblogic.security.SecurityInitializationException: The
    loading of OPSS java security policy provider failed due to exception, see theexception stack trace or the server log file for root cause. If still see no obv
    ious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd f
    or service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.
    SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message:JPS-02592: Failed to push ldap config data to libOvd for service instance "idsto
    re.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "def
    ault", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    Truncated. see log file for complete stacktraceCaused By: oracle.security.jps.JpsException: JPS-02592: Failed to push ldap conf
    ig data to libOvd for service instance "idstore.ldap" in JPS context "default",cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Erro
    r) Start of root element expected.
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
    at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3099)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap"
    in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:341)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context
    "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
    at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
    at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:101)
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:432)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
    Truncated. see log file for complete stacktrace
    Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
    Truncated. see log file for complete stacktrace
    >
    <Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Apr 10, 2012 3:07:23 PM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    help me please
    Thanks.
    Edited by: 842284 on 10 avr. 2012 07:41

    Hi,
    Please navigate to the fmwconfig folder and check the adapters.os_xml file.
    $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    There are chances the adapters.os_xml file could be corrupted due to which the Weblogic server fails to start.
    Please verify if the adapters.os_xml file is valid.
    In case the file is corrupted, please perform the following steps :
    1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    2) Delete $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
    3) copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/
    4) Restart the server.
    Regards,
    Kal

  • Unable to start admin server service for weblogic (startWebLogic.sh) Linux

    I installed ECM 11g on Linux 64-bit , installed weblogic 12
    so when I try to start admin server service for weblogic (startWebLogic.sh) and following error its showing
    I found solution to give full access permeation for the user , but it's still same issue
    and i am triyng to start services from the users how installed the Weblogic and ECM
    bash-4.1$ '/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/startWebLogic.sh' .
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/ecm/Oracle/Middleware/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/ecm/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/lib/jvm/jdk1.6.0_33/lib/tools.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic_sp.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic.jar:/home/ecm/Oracle/Middleware/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/webservices.jar:/home/ecm/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/ecm/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/ecm/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/home/ecm/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/xqrl.jar:/home/ecm/Oracle/Middleware/Oracle_ECM1/ucm/idc/jlib/idcloader.jar:/home/ecm/Oracle/Middleware/Oracle_ECM1/ucm/idc/components/NativeOsUtils/classes-NativeOsUtils.jar
    PATH=/home/ecm/Oracle/Middleware/wlserver_12.1/server/bin:/home/ecm/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/usr/lib/jvm/jdk1.6.0_33/jre/bin:/usr/lib/jvm/jdk1.6.0_33/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/ecm/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_33"
    Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
    Starting WLS with line:
    /usr/lib/jvm/jdk1.6.0_33/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/ecm/Oracle/Middleware/wlserver_12.1/server/lib/weblogic.policy -Xverify:none -Djava.endorsed.dirs=/usr/lib/jvm/jdk1.6.0_33/jre/lib/endorsed:/home/ecm/Oracle/Middleware/wlserver_12.1/endorsed -da -Dplatform.home=/home/ecm/Oracle/Middleware/wlserver_12.1 -Dwls.home=/home/ecm/Oracle/Middleware/wlserver_12.1/server -Dweblogic.home=/home/ecm/Oracle/Middleware/wlserver_12.1/server -Dcommon.components.home=/home/ecm/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain -Djrockit.optfile=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/servers/AdminServer -Doracle.domain.config.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/carml -Digf.arisidstack.home=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/home/ecm/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dipm.oracle.home=/home/ecm/Oracle/Middleware/Oracle_ECM1 -Ducm.oracle.home=/home/ecm/Oracle/Middleware/Oracle_ECM1 -Dem.oracle.home=/home/ecm/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/ecm/Oracle/Middleware/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/ecm/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server
    <Sep 12, 2012 12:08:02 PM EEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Sep 12, 2012 12:08:03 PM EEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Sep 12, 2012 12:08:03 PM EEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.8-b03 from Sun Microsystems Inc..>
    <Sep 12, 2012 12:08:04 PM EEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 13340309 Thu Feb 16 18:30:21 IST 2012
    WebLogic Server Temporary Patch for 13019800 Mon Jan 16 16:53:54 IST 2012
    WebLogic Server Temporary Patch for BUG13391585 Thu Feb 02 10:18:36 IST 2012
    WebLogic Server Temporary Patch for 13516712 Mon Jan 30 15:09:33 IST 2012
    WebLogic Server Temporary Patch for BUG13641115 Tue Jan 31 11:19:13 IST 2012
    WebLogic Server Temporary Patch for BUG13603813 Wed Feb 15 19:34:13 IST 2012
    WebLogic Server Temporary Patch for 13424251 Mon Jan 30 14:32:34 IST 2012
    WebLogic Server Temporary Patch for 13361720 Mon Jan 30 15:24:05 IST 2012
    WebLogic Server Temporary Patch for BUG13421471 Wed Feb 01 11:24:18 IST 2012
    WebLogic Server Temporary Patch for BUG13657792 Thu Feb 23 12:57:33 IST 2012
    WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
    <Sep 12, 2012 12:08:06 PM EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log00009. Log messages will continue to be logged in /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log.>
    <Sep 12, 2012 12:08:06 PM EEST> <Notice> <Log Management> <BEA-170019> <The server log file /home/ecm/Oracle/Middleware/user_projects/domains/ecm_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    Sep 12, 2012 12:08:09 PM oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore
    WARNING: Opening of file based keystore failed.
    <Sep 12, 2012 12:08:09 PM EEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.>
    <Sep 12, 2012 12:08:09 PM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
    weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:148)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsRuntimeException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
         at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3097)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06514: Opening of file based keystore failed.
         at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:374)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:104)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:76)
         at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:66)
         at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)
         Truncated. see log file for complete stacktrace
    >
    <Sep 12, 2012 12:08:09 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
    <Sep 12, 2012 12:08:09 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
    <Sep 12, 2012 12:08:09 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
    bash-4.1$

    Looks to be a cert or keystore issue. How do you have that setup?

  • Problems Starting Weblogic  Server for Tutorials (Fresh install)...

    Hi guys, need a little help here.
    I'm trying to startup Weblogic Server for Java Control Tutorial application and I get all sorts of errors, mostly seeming to deal with JMS/JNDI network stuff. Here's the error dump I get:
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.4.2_05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
    Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
    Starting WLS with line:
    C:\bea\JDK142~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
    ,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:Com
    pileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da
    :com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls
    .home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.con
    figuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.managem
    ent.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ign
    oreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.log
    ErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=C:\bea\WEBL
    OG~1\server\lib\weblogic.policy weblogic.Server
    <Oct 30, 2005 2:33:31 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting Web
    Logic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Micro
    systems Inc.>
    <Oct 30, 2005 2:33:31 PM PST> <Info> <Configuration Management> <BEA-150016> <Th
    is server is being started as the administration server.>
    <Oct 30, 2005 2:33:31 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877>
    <Oct 30, 2005 2:33:32 PM PST> <Notice> <Management> <BEA-140005> <Loading domain
    configuration from configuration repository at C:\bea\WEBLOG~1\samples\domains\
    workshop\.\config.xml.>
    <Oct 30, 2005 2:33:33 PM PST> <Notice> <Log Management> <BEA-170019> <The server
    log file C:\bea\weblogic81\samples\domains\workshop\cgServer\cgServer.log is op
    ened. All server side log events will be written to this file.>
    <Oct 30, 2005 2:33:34 PM PST> <Notice> <Security> <BEA-090082> <Security initial
    izing using security realm myrealm.>
    <Oct 30, 2005 2:33:34 PM PST> <Notice> <WebLogicServer> <BEA-000327> <Starting W
    ebLogic Admin Server "cgServer" for domain "workshop">
    <Oct 30, 2005 2:33:38 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
    ishment of SQL-connection. Pointbase Server may not be running on localhost at p
    ort 9093.>
    <Oct 30, 2005 2:33:40 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
    ishment of SQL-connection. Pointbase Server may not be running on localhost at p
    ort 9093.>
    <Oct 30, 2005 2:33:42 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
    ishment of SQL-connection. Pointbase Server may not be running on localhost at p
    ort 9093.>
    <Oct 30, 2005 2:33:44 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
    ishment of SQL-connection. Pointbase Server may not be running on localhost at p
    ort 9093.>
    <Oct 30, 2005 2:33:46 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
    ishment of SQL-connection. Pointbase Server may not be running on localhost at p
    ort 9093.>
    <Oct 30, 2005 2:33:47 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgJM
    SPool-nonXA" deployment failed with the following error: 0:Could not create pool
    connection. The DBMS driver exception was: SQL-server rejected establishment of
    SQL-connection. Pointbase Server may not be running on localhost at port 9093..
    >
    <Oct 30, 2005 2:33:48 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgPool": SQL-server rejected establishment o
    f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Oct 30, 2005 2:33:50 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgPool": SQL-server rejected establishment o
    f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Oct 30, 2005 2:33:52 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgPool": SQL-server rejected establishment o
    f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Oct 30, 2005 2:33:54 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgPool": SQL-server rejected establishment o
    f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Oct 30, 2005 2:33:56 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "cgPool": SQL-server rejected establishment o
    f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgPo
    ol" deployment failed with the following error: 0:Could not create pool connecti
    on. The DBMS driver exception was: SQL-server rejected establishment of SQL-conn
    ection. Pointbase Server may not be running on localhost at port 9093..>
    <Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
    urce" deployment failed with the following error: DataSource(cgDataSource;cgSamp
    leDataSource) can't be created with non-existent Pool (connection or multi) (cgP
    ool).>
    <Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
    urce-nonXA" deployment failed with the following error: DataSource(cgDataSource-
    nonXA;weblogic.jdbc.jts.ebusinessPool) can't be created with non-existent Pool (
    connection or multi) (cgJMSPool-nonXA).>
    <Oct 30, 2005 2:33:57 PM PST> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer
    " store failed to open java.io.IOException: JMS JDBC store, connection pool = <c
    gJMSPool-nonXA>, prefix = <weblogic>: connection pool does not exist.
    java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
    = <weblogic>: connection pool does not exist
    at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
    8)
    at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:337)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:597)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:575)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:754)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:733)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:509)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    60)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    28)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
    oteMBeanServerImpl.java:988)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:946)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7691)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1304)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:347)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    <Oct 30, 2005 2:33:57 PM PST> <Error> <JMS> <BEA-040123> <Failed to start JMS Se
    rver "cgJMSServer" due to weblogic.jms.common.JMSException: JMS can not open sto
    re cgJMSStore.
    weblogic.jms.common.JMSException: JMS can not open store cgJMSStore
    at weblogic.jms.backend.BEStore.start(BEStore.java:163)
    at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
    at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:337)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:597)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:575)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:754)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:733)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:509)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    60)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    28)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
    oteMBeanServerImpl.java:988)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
    ServerImpl.java:946)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
    ServerMBean_Stub.java:7691)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
    s(SlaveDeployer.java:1304)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
    ava:347)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
    e(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-non
    XA>, prefix = <weblogic>: connection pool does not exist
    at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
    8)
    at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
    at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
    at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
    at weblogic.jms.backend.BEStore.open(BEStore.java:262)
    at weblogic.jms.backend.BEStore.start(BEStore.java:151)
    ... 29 more
    >
    <Oct 30, 2005 2:33:57 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
    c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
    ml is correct, and the JMS destination has been deployed.>
    <Oct 30, 2005 2:33:58 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
    . Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
    he JMS destination has been deployed.>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090170> <Loading the priv
    ate key stored under the alias DemoIdentity from the jks keystore file C:\bea\we
    blogic81\server\lib\DemoIdentity.jks.>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090171> <Loading the iden
    tity certificate stored under the alias DemoIdentity from the jks keystore file
    C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
    certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.j
    ks.>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
    certificates from the jks keystore file C:\bea\JDK142~1\jre\lib\security\cacerts
    .>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000331> <Started We
    bLogic Admin Server "cgServer" for domain "workshop" running in Development Mode
    >
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
    rted in RUNNING mode>
    <Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
    0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
    <Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
    0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "Li
    stenThread.Default" listening on port 7001, ip address *.*>
    <Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SS
    LListenThread.Default" listening on port 7002, ip address *.*>
    <Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. Connection failed after 2 attempts. The MDB will attempt to
    reconnect every 10 seconds. This log message will repeat every 600 seconds until
    the condition clears.>
    <Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
    c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
    ml is correct, and the JMS destination has been deployed.>
    <Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. Connection failed after 2 attempts. The MDB will attempt to reconnect every
    10 seconds. This log message will repeat every 600 seconds until the condition
    clears.>
    <Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
    . Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
    he JMS destination has been deployed.>
    <Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. Connection failed after 62 attempts. The MDB will attempt to reconnect ever
    y 10 seconds. This log message will repeat every 600 seconds until the condition
    clears.>
    <Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
    . Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
    he JMS destination has been deployed.>
    <Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. Connection failed after 63 attempts. The MDB will attempt to
    reconnect every 10 seconds. This log message will repeat every 600 seconds unti
    l the condition clears.>
    <Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
    c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
    ml is correct, and the JMS destination has been deployed.>
    <Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. Connection failed after 122 attempts. The MDB will attempt to reconnect eve
    ry 10 seconds. This log message will repeat every 600 seconds until the conditio
    n clears.>
    <Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
    eue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
    . Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
    he JMS destination has been deployed.>
    <Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. Connection failed after 123 attempts. The MDB will attempt t
    o reconnect every 10 seconds. This log message will repeat every 600 seconds unt
    il the condition clears.>
    <Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
    edit.request.topic. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
    c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
    ml is correct, and the JMS destination has been deployed.>
    THANK YOU for any help you can provide!

    These are errors/warning because of incorrect connection pool settings.Either the database parameters were not configured correctly or there were some issues with the configuration itself.
    Your server did start up correctly though.
    "<Server started in RUNNING mode>"

  • Cannot start weblogic server anymore after conf. jena for oracle database

    Hi,
    My weblogic server 10.3.4.0 installed in oracle developer days in oralce linux guest was able to start before using the oracle user account. Following the seman. tech. dev. guide, I set up jena adapter for oracle in my guest linux system. Since the oracle user doesn't have permission to copy folders into the autodeploy directory in weblogic server, so I login as root to copy the joseki.war folder into the autodeploy directory. However, after that, I am not able to start the weblogic server console anymore using the oracle user account. Any suggestions will be much appreciated. Thanks a lot in advance.
    Hong

    Pl do not post duplicates - cannot start weblogic server anymore in oracle user after config. in root

Maybe you are looking for

  • Excise cycle in case of cenvatable items

    Hi SAP gurus A po is raised for a cenvatable item.can some body please guide how the excise entry will appear and what stage.Kindly give the process wise T code . Points will be given. Thanks in advance. sk

  • Photoshop CS2 not opening files

    I have been having this problem for several weeks now. When ever I try to open any file in Photoshop CS2, it just spools the little rainbow circle and never opens the file. THankfully, I still have Photoshop CS on my computer so I can run things thro

  • Get FI Documet number from BKPF table using CO document number in COVP tabl

    Hi, In  datasource 0CO_OM_CCA_9 , we have written a code in CMOD to get the FI Document Number from CO document Number. The flow of code is: 1) From the CO document number, get reference document number  (REFBNfield) from, COVP table 2) Pass this REF

  • Vendor List for PO

    Hi Experts, when i am doing PO with xyz material. i am trying to search vendor. through radio button Vendors : By material .  so i go list of vendors but  vendor number and info record and plant. how can i get vendor number and NAME in that Hit list.

  • I don't understand how to upgrade to iOS 5 or 6 on my iPad?

    I don't understand how to upgrade to iOS 5 or 6 on my iPad?