How to start managed server on Weblogic 9.1 Admin console with jRockit

I configured a new 9.1 domain with jRockit as the JVM. Under Server Start, I used -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause in the Argument field. When I tried to start the server, I am getting the following error:
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Starting WebLogic server with command line: C:\bea\jrockit90_150_04\bin\java -Dweblogic.Name=jdevext -Dbea.home=C:\bea -Djava.security.policy=c:\bea\weblogic91\server\lib\weblogic.policy -Dweblogic.management.server=http://144.111.155.145:7001 -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\QuickTime\QTSystem\ -Djava.class.path=C:\bea\weblogic91\server\lib\weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;c:\bea\weblogic91\server\lib\wamapps\commons-logging.jar;c:\bea\weblogic91\server\lib\wamapps\log4j.jar;c:\bea\weblogic91\server\lib\wamapps\xalan.jar;c:\bea\weblogic91\server\lib\wamapps\xercesImpl.jar;c:\bea\weblogic91\server\lib\wamapps\xml-apis.jar -Dweblogic.system.BootIdentityFile=C:\bea\user_projects\domains\jdev\servers\jdevext\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false java -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause -verbose weblogic.Server >
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Working directory is "C:\bea\user_projects\domains\jdev">
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Server output log file is "C:\bea\user_projects\domains\jdev\servers\jdevext\logs\jdevext.out">
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-jrockit     to select the "jrockit" VM
-client     to select the "client" VM
-server     to select the "server" VM [synonym for the "jrockit" VM]
The default VM is jrockit.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
<May 24, 2006 11:16:57 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>

It looks like your command line is broken. You have:
java <lots of -Dprop=value> java <JRockit flags> weblogic.Server
That second "java" shouldn't be there.
-- Henrik

Similar Messages

  • How to start Managed server in Weblogic 8.1

    Hi,
    I am Using Weblogic 8.1 server. I can able to start weblogic server by invkoing startWebLogic.sh. When I start managed server by invoking the shell startManagedWebLogic.sh it error out by following exception
    <BEA-000364> <Server failed during initialization. Exception:weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
    netscape.ldap.LDAPException: error result (49)
    weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
    netscape.ldap.LDAPException: error result (49)
    at weblogic.security.providers.authorization.DefaultAuthorizationUtils.getEngine(DefaultAuthorizationUtils.java:130)
    at weblogic.security.providers.authorization.DefaultRoleMapperProviderImpl.initialize(DefaultRoleMapperProviderImpl.java:104)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:242)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:957)
    at weblogic.security.service.RoleManager.initialize(RoleManager.java:152)
    at weblogic.security.service.RoleManager.<init>(RoleManager.java:98)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doRole(SecurityServiceManagerDelegateImpl.java:513)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:409)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:700)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:733)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:876)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:734)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    I refered some forum, they ask to update <EmbeddedLDAP > tag by setting Credential="" in config.xml file. Still I get the same exception.
    I have also tried in console, that too fails.
    Help me out to resolve this.
    thanks,
    Thiru.

    Hi,
    Thanks for your reply.
    My Admin server is running fine. The msi-config.xml, SerializedSystemIni.dat, boot.properties files are in the same directory. When I exceute the command
    startManagedWebLogic.sh <managed server name> it shows the same exception
    <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
    netscape.ldap.LDAPException: error result (49)
    weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
    netscape.ldap.LDAPException: error result (49)
    thanks,
    Thiru.

  • Can't start manager server on other machine from admin console

    hi, m fredzh
    i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
    the machines and servers list as follow:
    cluster1 192.168.1.100
    --machine1
    --server1 192.168.1.100
    --machine2
    -server2 192.168.1.101
    i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
    then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
    start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
    can anbody help me, thank you..
    ==============================================================================
    <Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    java.lang.AssertionError: java.lang.reflect.InvocationTargetException
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
    at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
    at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
    at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
    at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
    at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
    at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
    at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.reflect.InvocationTargetException
    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 weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
    at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
    at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
    at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
    at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
    at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
    at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
    at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
    at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
    at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
    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 weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
    at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
    at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
    at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
    at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
    at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
    at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
    at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
    at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Edited by: fredzh on 2010-10-12 下午6:54

    hi,Jay
    i followed the steps as follow:
    1、change prod mode to dev
    2、modified the config.xml entrys on the all two servers:
    <node-manager-password-encrypted>test</node-manager-password-encrypted>
    <credential-encrypted>test</credential-encrypted>
    <embedded-ldap>
    <name>cluster_domain</name>
    <credential-encrypted>test</credential-encrypted>
    </embedded-ldap>
    3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
    4、change the dev mode to prod mode on admin console, it failed throw error:
    "in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
    i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is the config.xml :
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
    <name>cluster_domain</name>
    <domain-version>10.3.2.0</domain-version>
    <security-configuration>
    <name>cluster_domain</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
    <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
    <sec:name>SystemPasswordValidator</sec:name>
    <pas:min-password-length>8</pas:min-password-length>
    <pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
    </sec:password-validator>
    </realm>
    <default-realm>myrealm</default-realm>
    <anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
    <credential-encrypted>test</credential-encrypted>
    <web-app-files-case-insensitive>false</web-app-files-case-insensitive>
    <compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>test</node-manager-password-encrypted>
    <principal-equals-case-insensitive>false</principal-equals-case-insensitive>
    <principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
    <downgrade-untrusted-principals>false</downgrade-untrusted-principals>
    <enforce-strict-url-pattern>true</enforce-strict-url-pattern>
    <cross-domain-security-enabled>false</cross-domain-security-enabled>
    </security-configuration>
    <jta>
    <security-interop-mode>default</security-interop-mode>
    </jta>
    <server>
    <name>AdminServer</name>
    <ssl>
    <hostname-verifier xsi:nil="true"></hostname-verifier>
    <hostname-verification-ignored>true</hostname-verification-ignored>
    <export-key-lifespan>500</export-key-lifespan>
    <client-certificate-enforced>false</client-certificate-enforced>
    <two-way-ssl-enabled>false</two-way-ssl-enabled>
    <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
    <inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
    <outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
    <allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
    <use-server-certs>false</use-server-certs>
    </ssl>
    <listen-port>7110</listen-port>
    <listen-address></listen-address>
    </server>
    <server>
    <name>server2</name>
    <machine>machine2</machine>
    <listen-port>7110</listen-port>
    <listen-address>192.168.1.101</listen-address>
    <server-start>
    <java-vendor>Sun</java-vendor>
    <java-home>/opt/jdk1.6.0_21</java-home>
    <bea-home>/root/Oracle/Middleware</bea-home>
    <root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
    <username>weblogic</username>
    <password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
    </server-start>
    </server>
    <embedded-ldap>
    <name>cluster_domain</name>
    <credential-encrypted>test</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.2.0</configuration-version>
    <machine xsi:type="unix-machineType">
    <name>machine2</name>
    <node-manager>
    <nm-type>SSL</nm-type>
    <listen-address>192.168.1.101</listen-address>
    <listen-port>5556</listen-port>
    <debug-enabled>false</debug-enabled>
    </node-manager>
    </machine>
    <admin-server-name>AdminServer</admin-server-name>
    </domain>
    Edited by: fredzh on 2010-10-13 下午7:57

  • How to start Managed server in weblogic10gr3....please help me out...

    hi...
    How to start Managed server in weblogic10gr3....please help me out...

    Hi
    You can start Managed server in admin console ->servers
    or you can start the managed servers in Independent mode(without admin server)
    by using the startManagedWebLogic.cmd/>startManagedWebLogic.sh (this requires weblogic authentication).
    Hope this helps
    thanks

  • Error starting managed server in weblogic

    am having this error wne starting managed server
    C:\mydomain\base_domain\bin>startManagedWebLogic.cmd madimad-b533821
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
    128m  -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
    :\PROGRA~1\Java\JDK16~1.0_2\lib\tools.jar;C:\mywls\wlserver\server\lib\weblogic_
    sp.jar;C:\mywls\wlserver\server\lib\weblogic.jar;C:\mywls\modules\features\weblo
    gic.server.modules_10.3.4.0.jar;C:\mywls\wlserver\server\lib\webservices.jar;C:\
    mywls\modules\ORGAPA~1.1/lib/ant-all.jar;C:\mywls\modules\NETSFA~1.0_1/lib/ant-c
    ontrib.jar;C:\oracle\Middleware\wlserver_10.3\sip\server\lib\weblogic_sip.jar;C:
    \Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\mywls\wlserver\co
    mmon\derby\lib\derbyclient.jar;C:\mywls\wlserver\server\lib\xqrl.jar
    PATH=;C:\mywls\wlserver\server\native\win\32;C:\mywls\wlserver\server\bin;C:\myw
    ls\modules\ORGAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_2\jre\bin;C:\PROGRA~1\Java\
    JDK16~1.0_2\bin;C:\Program Files\PC Connectivity Solution\;C:\product\11.2.0\dbh
    ome_1\bin;C:\product\11.2.0\dbhome_1;C:\forms;C:\DevSuiteHome_1\jlib;C:\Program
    Files\PHP;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Fil
    es\Common Files\Roxio Shared\DLLShared;C:\Program Files\Common Files\Roxio Share
    d\DLLShared;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared;C:\Program
    Files\Common Files\DivX Shared;c:\Program Files\Java\jdk1.6.0_21\bin;C:\Program
    Files\Common Files\Roxio Shared\10.0\DLLShared;C:\Program Files\Common Files\Rox
    io Shared\DLLShared;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared;C:
    \mywls;C:\mydomain\base_domain\bin;C:\Program Files\Java\jre6\bin\client;C:\Prog
    ram Files\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_21\jre\bin;C:\Program Fil
    es\Java\jdk1.6.0_21\bin;C:\Program Files\Java\jdk1.6.0_21;C:\Program Files\Java\
    jre6;C:\DevSuiteHome_1\forms;C:\DevSuiteHome_1\cgenf61\admin;C:\DevSuiteHome_1\f
    orms;C:\forms\sms_code.pll;C:\mywls\wlserver;C:\Java\jdk1.6.0_21;C:\mywls\wlserv
    er\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_21"
    Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
    Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client   -Xms256m -Xmx512m -XX:CompileThr
    eshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m -Dweblogic.Name=madimad-b533
    821 -Djava.security.policy=C:\mywls\wlserver\server\lib\weblogic.policy -Dweblog
    ic.security.SSL.trustedCAKeyStore="C:\mywls\wlserver\server\lib\cacerts"  -Xveri
    fy:none -ea:com.bea.wcp...   -da -Dplatform.home=C:\mywls\wlserver -Dwls.home=C:
    \mywls\wlserver\server -Dweblogic.home=C:\mywls\wlserver\server  -Dcommon.compon
    ents.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.
    logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\mydomai
    n\BASE_D~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1
    .1\jrocket_optfile.txt -Doracle.server.config.dir=C:\mydomain\BASE_D~1\config\FM
    WCON~1\servers\madimad-b533821 -Doracle.domain.config.dir=C:\mydomain\BASE_D~1\c
    onfig\FMWCON~1  -Digf.arisidbeans.carmlloc=C:\mydomain\BASE_D~1\config\FMWCON~1\
    carml  -Digf.arisidstack.home=C:\mydomain\BASE_D~1\config\FMWCON~1\arisidprovide
    r -Doracle.security.jps.config=C:\mydomain\BASE_D~1\config\fmwconfig\jps-config.
    xml -Doracle.deployed.app.dir=C:\mydomain\BASE_D~1\servers\madimad-b533821\tmp\_
    WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracl
    e\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\mo
    dules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.prot
    ocol  -Dweblogic.jdbc.remoteEnabled=false  -Dweblogic.management.discover=false
    -Dweblogic.management.server=http://madimad-b533821:7001  -Dwlw.iterativeDev=fal
    se -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false  weblogic.Server
    <24 Jan 2014 12:52:41 PM> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE
    Provider self-integrity check for better startup performance. To enable this che
    ck, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <24 Jan 2014 12:52:42 PM> <Info> <Security> <BEA-090906> <Changing the default R
    andom Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable thi
    s change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <24 Jan 2014 12:52:42 PM> <Notice> <WebLogicServer> <BEA-000395> <Following exte
    nsions directory contents added to the end of the classpath:
    C:\mydomain\base_domain\lib\sipactivator.jar>
    <24 Jan 2014 12:52:42 PM> <Info> <Server> <BEA-002647> <The service plugin, com.
    oracle.core.sip.activator, was added from C:\mydomain\base_domain\lib\sipactivat
    or.jar.>
    <24 Jan 2014 12:52:42 PM> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogi
    c Server with Java HotSpot(TM) Client VM Version 17.0-b17 from Sun Microsystems
    Inc.>
    <24 Jan 2014 12:52:45 PM> <Info> <Security> <BEA-090065> <Getting boot identity
    from user.>
    Enter username to boot WebLogic server:tshifhiwa
    Enter password to boot WebLogic server:
    <24 Jan 2014 12:52:57 PM> <Info> <Management> <BEA-141107> <Version: WebLogic Se
    rver 10.3.4.0  Fri Dec 17 20:47:33 PST 2010 1384255 >
    <24 Jan 2014 12:53:01 PM> <Error> <Management> <BEA-141252> <The domain version,
    10.3.5.0, is greater than the release version, 10.3.4.0, of this server.>
    <24 Jan 2014 12:53:01 PM> <Error> <Configuration Management> <BEA-150001> <An er
    ror occurred while connecting to the admin server to bootstrap through URL: http
    ://madimad-b533821:7001/bea_wls_management_internal2/Bootstrap, user: tshifhiwa
    weblogic.management.configuration.ConfigurationException: [Management:141252]The
    domain version, 10.3.5.0, is greater than the release version, 10.3.4.0, of thi
    s server.
            at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStr
    uct(BootStrapHelper.java:147)
            at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(Ru
    ntimeAccessImpl.java:432)
            at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
    imeAccessService.java:49)
            at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
    ager.java:461)
            at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
    icesManager.java:166)
            at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
            at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
            at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
            at weblogic.Server.main(Server.java:71)
    >
    <24 Jan 2014 12:53:01 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
    hanged to STARTING>
    <24 Jan 2014 12:53:01 PM> <Info> <WorkManager> <BEA-002900> <Initializing self-t
    uning thread pool>
    <24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320400> <The log file C
    :\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log will be
    rotated. Reopen the log file if tailing has stopped. This can happen on some pla
    tforms like Windows.>
    <24 Jan 2014 12:53:02 PM> <Notice> <LoggingService> <BEA-320401> <The log file h
    as been rotated to C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-
    b533821.log00007. Log messages will continue to be logged in C:\mydomain\base_do
    main\servers\madimad-b533821\logs\madimad-b533821.log.>
    <24 Jan 2014 12:53:02 PM> <Notice> <Log Management> <BEA-170019> <The server log
    file C:\mydomain\base_domain\servers\madimad-b533821\logs\madimad-b533821.log i
    s opened. All server side log events will be written to this file.>
    <24 Jan 2014 12:54:25 PM> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
    stem failed. Reason: java.lang.AssertionError: Assertion violated
    java.lang.AssertionError: Assertion violated
            at weblogic.utils.Debug.assertion(Debug.java:57)
            at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
    ce.java:2060)
            at weblogic.server.channels.ChannelService.getServerChannel(ChannelServi
    ce.java:1998)
            at weblogic.protocol.ServerChannelManager.findServerChannel(ServerChanne
    lManager.java:76)
            at weblogic.ldap.EmbeddedLDAP.findLdapURL(EmbeddedLDAP.java:1482)
            Truncated. see log file for complete stacktrace
    >
    <24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
    hanged to FAILED>
    <24 Jan 2014 12:54:26 PM> <Error> <WebLogicServer> <BEA-000383> <A critical serv
    ice failed. The server will shut itself down>
    <24 Jan 2014 12:54:26 PM> <Notice> <WebLogicServer> <BEA-000365> <Server state c
    hanged to FORCE_SHUTTING_DOWN>

    Hi,
    there are two thing in this issue.
    first
    It looks like the upgrade which you done is not happen correctly.
    Revert the back the upgrade and restart the the server again.
    Second
    rename the Ldap folder of you managed server and restart the server again.
    Regards,
    Kal

  • How to start managed server from admin server both running

    I have an admin server on one machine and created a managed server on different
    machine, I am not able to start managed server from either machine. When I used
    the admin server machine to start the managed server remotely I got this message
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server (running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
    ed during initialization. Exception:java.lang.SecurityException: Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Thanks.

    "fkeita" <[email protected]> wrote in message
    news:[email protected]...
    >
    I have an admin server on one machine and created a managed server ondifferent
    machine, I am not able to start managed server from either machine. When Iused
    the admin server machine to start the managed server remotely I got thismessage
    >
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
    >
    Try running netstat to see whether another process is actually running at
    the given address/port.
    Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
    the box to see whether the ips addreses are correct.
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server(running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
    ed during initialization. Exception:java.lang.SecurityException:Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >Seems to be some issue with security credentials.
    Try running the manageed server directly (as sort of admin) by not passing
    the admin server url and bringing it just like an admin server.
    See if this works. If it works, then soemthing wrong in the way the admin
    server is receiving the request/security credentials from managed server.
    Also make sure both managed and admin servers are on the same patch/service
    pack level.
    -Sabha

  • How to start managed server from admin server both running on separate machines

              I have an admin server on one machine and created a managed server on different
              machine, I am not able to start managed server from either machine. When I used
              the admin server machine to start the managed server remotely I got this message
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
              ogic Managed Server "managedserver3" for domain "admindomain">
              <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
              create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
              java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
              a
              ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
              to
              bind to any port such that it is not reachable from the console.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception>
              When I tried to connect managed server from its machine to admin server (running
              on separate machine ) I got this error
              Starting WebLogic Server...
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
              ed during initialization. Exception:java.lang.SecurityException: Authentication
              for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              The WebLogic Server did not start up properly.
              Exception raised:
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Reason: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Thanks.
              

              I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
              server, but it did not work, and got error messages. Error messages are posted
              on my first posting.
              "pankaj" <[email protected]> wrote:
              >Use the startManagedWeblogic.cmd / .sh script to start your
              >Managed/Clustered servers
              >
              >
              >"fkeita" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> I have an admin server on one machine and created a managed server
              >on
              >different
              >> machine, I am not able to start managed server from either machine.
              >When I
              >used
              >> the admin server machine to start the managed server remotely I got
              >this
              >message
              >>
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
              ><Starting WebL
              >> ogic Managed Server "managedserver3" for domain "admindomain">
              >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
              ><Unable to
              >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
              >port:
              >8002.
              >> java.net.BindException: Cannot assign requested address: JVM_Bind
              >Perhaps
              >the
              >> a
              >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
              >port
              >8002.>
              >>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
              >failed
              >> to
              >> bind to any port such that it is not reachable from the console.>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception>
              >>
              >> When I tried to connect managed server from its machine to admin server
              >(running
              >> on separate machine ) I got this error
              >>
              >> Starting WebLogic Server...
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
              ><Server fail
              >> ed during initialization. Exception:java.lang.SecurityException:
              >Authentication
              >> for user system denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >>
              >***************************************************************************
              >> The WebLogic Server did not start up properly.
              >> Exception raised:
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> Reason: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >>
              >> Thanks.
              >
              >
              

  • Getting error while starting manage server on weblogic 9.2 platform

    Hi
    I am getting following error while I try to start manage server
    java.lang.NullPointerException: at com.bea.console.handles.JMXHandle.(JMXHandle.java:73) at com.bea.console.actions.core.server.lifecycle.Lifecycle.noAccess(Lifecycle.java:771) at com.bea.console.actions.core.server.lifecycle.Lifecycle.start(Lifecycle.java:109) 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:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:869) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:63) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:167) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:49) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:57) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:86) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:221) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    The node manager is reachable, also the port it is listening is reachable.
    Please suggest me somethng
    Thanks and Regards
    Shilpa

    Hi
    I am getting following error while I try to start manage server
    java.lang.NullPointerException: at com.bea.console.handles.JMXHandle.(JMXHandle.java:73) at com.bea.console.actions.core.server.lifecycle.Lifecycle.noAccess(Lifecycle.java:771) at com.bea.console.actions.core.server.lifecycle.Lifecycle.start(Lifecycle.java:109) 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:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:869) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:63) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:167) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:49) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:57) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:86) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:221) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    The node manager is reachable, also the port it is listening is reachable.
    Please suggest me somethng
    Thanks and Regards
    Shilpa

  • MANAGED SERVER NOT COMMING UP  FROM ADMIN CONSOLE,

    Hi All,
    I can't start managed server from admin console.
    The status is showing FAILED_NOT_RESTARTABLE.
    below is the error it is showing in the node manager.
    But i can start managed server from the back-end successfully. If i start the nodemanager then managed server is not comming up.
    <May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed
    _server'>
    java.io.IOException: Server failed to start up. See server output log for more d
    etails.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
    rManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)
    May 24, 2011 4:12:22 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'my_managed_server'
    java.io.IOException: Server failed to start up. See server output log for more d
    etails.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
    rManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)
    Please help.
    Regards,
    nag.

    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain'>
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out00039">
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server error log also redirected to server log>
    <May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out'>
    <May 24, 2011 4:12:22 AM> <INFO> <weblogic_domain> <my_managed_server> <Server failed during startup so will not be restarted>
    <May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed_server'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    This is what i found in nodemanager log file
    Regards,
    Nag.

  • Error configuring and starting Managed Server in WebLogic 10.3

    Hi,
    I am able to configure and start the Managed Server on windows environment. I am trying to configure Managed Server on linux environment. I am configuring the Managed Server with custom keystore. When I configured the Managed Server I specified the keystore/trustsote information in the Keystores tab of the Admin Console for Managed Server settings. Specified Private Key Alias, Password in SSL tab.But when I am starting the Managed Server from command line, I see the process looking for demo trust files and failing.
    Here is the command I run to start the Managed Server:
    ./startManagedWebLogic.sh MyManagedServer1 https://localhost.localdomain:8443
    Below is the console output:
    <Mar 11, 2015 12:37:44 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
    <Mar 11, 2015 12:37:45 PM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:beaadmin
    Enter password to boot WebLogic server:
    <Mar 11, 2015 12:37:53 PM PDT> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks.>
    <Mar 11, 2015 12:37:53 PM PDT> <Error> <Security> <BEA-090132> <Could not open the keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks for read access. Exception: java.io.FileNotFoundException: /opt/wlserver_10.3/server/lib/DemoTrust.jks (No such file or directory)>
    <Mar 11, 2015 12:37:53 PM PDT> <Warning> <Security> <BEA-090164> <Failed to load trusted certificates from keystore /opt/wlserver_10.3/server/lib/DemoTrust.jks of type jks>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jre1.6.0_45/lib/security/cacerts.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    <Mar 11, 2015 12:37:53 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
    <Mar 11, 2015 12:37:55 PM PDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at https://localhost.localdomain:8443.>
    <Mar 11, 2015 12:37:55 PM PDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Mar 11, 2015 12:37:55 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Mar 11, 2015 12:37:55 PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320400> <The log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log00015. Log messages will continue to be logged in /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log.>
    <Mar 11, 2015 12:37:55 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log is opened. All server side log events will be written to this file.>
    <Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090837]The configured keystore location for the PKI Credential Mapper is either null or empty.>
    <Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090815]The password provided for the keystore configured for the PKICredential Mapper was null.>
    <Mar 11, 2015 12:37:57 PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 11, 2015 12:37:57 PM PDT> <Critical> <Security> <BEA-090403> <Authentication for user beaadmin denied>
    <Mar 11, 2015 12:37:57 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
    weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
            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: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User beaadmin weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
            at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
            at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            Truncated. see log file for complete stacktrace
    >
    <Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Mar 11, 2015 12:37:57 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Why is it looking for demotrust.jks file to start the Managed Server. We don't use the demo trust and cannot copy to the location it is referring to. I followed the solution provided at the below link:
    http://serverfault.com/questions/106499/custom-trust-and-custom-identity-keystore-in-weblogic-10-3
    There are 2 options given in the link. To update the boot.properties of the Admin Server and appending JAVA_OPTIONS to DomainEnv file. Both of these caused the failure of Admin Server. I couldn't bring up the server after these changes.I also came across posts talking about boot.properties for Managed Server. I don't see the security folder that has boot.properties for my Managed Server (verified it on both windows and linux boxes).
    Thanks in advance.
    -nn.

    Hi Faisal,
    Here is the config.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd"
            xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security"
            xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <name>JCRMDomain</name>
        <domain-version>10.3.4.0</domain-version>
        <security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml">
            <name>JCRMDomain</name>
            <realm>
                <sec:authentication-provider xsi:type="wls:default-authenticatorType">
                    <sec:control-flag>SUFFICIENT</sec:control-flag>
                </sec:authentication-provider>
                <sec:authentication-provider xmlns:ext="http://xmlns.oracle.com/weblogic/security/extension" xsi:type="ext:jcrm-authenticatorType">
                    <sec:name>JcrmAuthenticator</sec:name>
                    <sec:control-flag>SUFFICIENT</sec:control-flag>
                </sec:authentication-provider>
                <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
                <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
                <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
                <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
                <sec:credential-mapper xsi:type="wls:pki-credential-mapperType">
                    <sec:name>PKICredentialMapper</sec:name>
                </sec:credential-mapper>
                <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
                <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
                <sec:user-lockout-manager>
                    <sec:lockout-threshold>3</sec:lockout-threshold>
                    <sec:lockout-duration>15</sec:lockout-duration>
                    <sec:lockout-reset-duration>99999</sec:lockout-reset-duration>
                </sec:user-lockout-manager>
                <sec:deploy-role-ignored>false</sec:deploy-role-ignored>
                <sec:deploy-policy-ignored>false</sec:deploy-policy-ignored>
                <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
                <sec:security-dd-model>DDOnly</sec:security-dd-model>
                <sec:combined-role-mapping-enabled>true</sec:combined-role-mapping-enabled>
                <sec:name>myrealm</sec:name>
                <sec:delegate-m-bean-authorization>false</sec:delegate-m-bean-authorization>
                <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator"
                                        xsi:type="pas:system-password-validatorType">
                    <sec:name>JCRMPasswordValidator</sec:name>
                    <pas:max-password-length>31</pas:max-password-length>
                    <pas:min-password-length>15</pas:min-password-length>
                    <pas:min-numeric-characters>2</pas:min-numeric-characters>
                    <pas:min-lowercase-characters>2</pas:min-lowercase-characters>
                    <pas:min-uppercase-characters>2</pas:min-uppercase-characters>
                    <pas:min-non-alphanumeric-characters>2</pas:min-non-alphanumeric-characters>
                </sec:password-validator>
                <sec:deployable-provider-synchronization-enabled>false</sec:deployable-provider-synchronization-enabled>
            </realm>
            <default-realm>myrealm</default-realm>
            <credential-encrypted>{AES}cpwhv2peqwl0Z8Ma1Jk7KlmC6d1gtCAqxnzrmR5ssybHpM9AUzbBRJ7rE7m4/7U16IHgsTMkcOr/5/abZJ4NeuHR45jdDK1EjFmnUuPssISmGkan3EIpCKHmPPIynVxh</credential-encrypted>
            <node-manager-username>wdUXiuwL5A</node-manager-username>
            <node-manager-password-encrypted>{AES}UDiZjaLOrm0y+/I9noQVURudpzmRKMBOQR2B8ofNIt8=</node-manager-password-encrypted>
        </security-configuration>
        <server>
            <name>AdminServer</name>
            <max-http-message-size>10000000</max-http-message-size>
            <ssl>
                <name>AdminServer</name>
                <enabled>true</enabled>
                <hostname-verifier xsi:nil="true"></hostname-verifier>
                <hostname-verification-ignored>true</hostname-verification-ignored>
                <client-certificate-enforced>false</client-certificate-enforced>
                <listen-port>8443</listen-port>
                <two-way-ssl-enabled>true</two-way-ssl-enabled>
                <server-private-key-alias>localhost.localdomain</server-private-key-alias>
                <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
                <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
                <allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
                <use-server-certs>true</use-server-certs>
                <jsse-enabled>true</jsse-enabled>
            </ssl>
            <listen-port-enabled>false</listen-port-enabled>
            <web-server>
                <keep-alive-secs>60</keep-alive-secs>
                <https-keep-alive-secs>60</https-keep-alive-secs>
            </web-server>
            <listen-address/>
            <java-compiler>javac</java-compiler>
            <tunneling-enabled>true</tunneling-enabled>
            <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
            <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
            <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
            <key-stores>CustomIdentityAndCustomTrust</key-stores>
            <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
            <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
            <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
            <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
            <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
            <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
        <overload-protection>
          <panic-action>system-exit</panic-action>
          <failure-action>force-shutdown</failure-action>
          <server-failure-trigger>
            <max-stuck-thread-time>600</max-stuck-thread-time>
            <stuck-thread-count>3</stuck-thread-count>
          </server-failure-trigger>
        </overload-protection>
        </server>
        <server>
          <name>MyManagedServer1</name>
          <ssl>
            <enabled>true</enabled>
            <listen-port>8445</listen-port>
            <server-private-key-alias>localhost.localdomain</server-private-key-alias>
            <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
          </ssl>
          <machine xsi:nil="true"></machine>
          <listen-port>8444</listen-port>
          <listen-port-enabled>true</listen-port-enabled>
          <cluster xsi:nil="true"></cluster>
          <web-server>
            <web-server-log>
              <number-of-files-limited>false</number-of-files-limited>
            </web-server-log>
          </web-server>
          <listen-address></listen-address>
          <key-stores>CustomIdentityAndCustomTrust</key-stores>
          <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
          <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
          <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
          <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
          <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
          <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
          <data-source>
            <rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
          </data-source>
        </server>
        <production-mode-enabled>false</production-mode-enabled>
        <embedded-ldap>
            <name>JCRMDomain</name>
            <credential-encrypted>{AES}LNAnq4qCQQmy9rCOMN+uIZVPq1bVvPrwQqqtOScZrnYmwESt9aruHNVy4IjqMWz7</credential-encrypted>
        </embedded-ldap>
        <administration-port-enabled>true</administration-port-enabled>
        <configuration-version>10.3.4.0</configuration-version>
        <admin-server-name>AdminServer</admin-server-name>
    </domain>
    It has 'CustomIdentityAndCustomTrust' for both Admin Server as well as managed Server in it.
    Thanks,
    nn

  • Failed to start managed server in weblogic server 9.2.1

    Before I'm using WebLogic 9.2.0 and the managed server can startup without any issue. Now, my environment is upgraded to WebLogic 9.2.1 and I'm experiencing a couple of problems. The major problem is that I cannot start my managed server anymore even if the node manager and admin servers are running. Error logged are as follows:
    <May 22, 2007 2:52:31 PM GMT+08:00> <Critical> <WebLogicServer> <BEA-000386> <Se
    rver subsystem failed. Reason: javax.management.RuntimeErrorException: Error thr
    own by the invoke method of the Dynamic MBean
    javax.management.RuntimeErrorException: Error thrown by the invoke method of the
    Dynamic MBean
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:195)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
    at javax.management.remote.rmi.RMIConnectionImpl_920_WLStub.invoke(Unkno
    wn Source)
    at weblogic.management.remote.common.RMIConnectionWrapper$15.run(ClientP
    roviderBase.java:606)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    Truncated. see log file for complete stacktrace
    java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.jndi.intern
    al.ServerNamingNode_920_WLStub
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(W
    LInitialContextFactoryDelegate.java:587)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInit
    ialContextFactoryDelegate.java:559)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:474)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:372)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    Truncated. see log file for complete stacktrace
    java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_920_WL
    Stub
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:168)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(W
    LInitialContextFactoryDelegate.java:583)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInit
    ialContextFactoryDelegate.java:559)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:474)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:372)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    67)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(C
    lientProviderBase.java:125) at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(
    ClientProviderBase.java:79)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnec
    torFactory.java:326)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto
    ry.java:247)
    at weblogic.management.mbeanservers.domainruntime.internal.MBeanServerCo
    nnectionManager.connectToManagedServer(MBeanServerConnectionManager.java:276)
    at weblogic.management.mbeanservers.domainruntime.internal.MBeanServerCo
    nnectionManager.notifyNewMBeanServer(MBeanServerConnectionManager.java:383)
    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:585)
    at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean
    .java:411)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
    l.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
    BeanServerInterceptor.java:815)
    at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
    nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:149)
    at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterce
    ptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:149)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(
    SecurityInterceptor.java:426)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor$10.run(AuthenticatedSubjectInterceptor.java:377)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor.invoke(AuthenticatedSubjectInterceptor.java:375)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanSer
    ver.java:310)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
    onImpl.java:1408)
    at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
    nImpl.java:81)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
    (RMIConnectionImpl.java:1245)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
    MIConnectionImpl.java:1348)
    at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
    l.java:782)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown S
    ource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:434)
    at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:5
    7)
    at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicSer
    verRef.java:965)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    I experienced similar (identical?) problem after upgrading WLS 9.2 with MP2.
    In my case simple setting the following fields from the tab 'Server Start': Java Home and Classpath resolved problem.
    Greetings
    GT

  • How to start managed server from console?

    Hi,
    After several unsuccesful attempts to start a managed server from admin console,
    which starts fine by script and stops by console, can somebody please mail me
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute or not. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

    The ServerStart element should look like below (WLS6.1sp1+). Using absolute
    path is definitely OK. Please provide us more info if you still have this
    problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
    especially config and <mgr'ed server name>_error.log
    <ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
    ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
    blogic.jar"
    Name="Server-1005280911753"
    OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
    005280991998.log"
    RootDirectory="d:\bea\load1"
    SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
    "Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
    >
    Hi,
    After several unsuccesful attempts to start a managed server from adminconsole,
    which starts fine by script and stops by console, can somebody please mailme
    what to enter in the "remote start" tab!
    The documentation is very uncertain if the path have to be absolute ornot. It
    seems to be a problem with the classpath.
    thanks in advance
    Kai

  • How to start managed server automatically with admin server.

    Hello all, I have an admin server anda managed server configured in a machine. I want to start the managed server as soon as I run the script to start the admin server and node manager in the unix pc.
    The admin and managed server are added to the same machine and the machine is connected with the node manager.
    Please let me know what else need to be configured or make change in the script.

    hello user12003735..
    sorry for not mentioning the wlst tool path.
    You can start the wlst(WEBLOGIC SCRIPTING TOOL) in two ways and run your jython scripts.
    PROCEDURE 1) Directly invoking wlst :
    You will find the wlst.cmd(wlst.sh in case of UNIX enviroments) in $WL_HOME/common/bin. From command line do this
    wlst <JYTHON SCRIPT>
    ./wlst.sh <JYTHON SCRIPT> [UNIX]
    PROCEDURE 2) From Command Line :
    There is a jar file in $WL_HOME/server/lib named weblogic.jar. It conatins a class file named WLST.cmd in the package weblogic[Try jd-gui.exe java decompiler to look inside the jarfile. to get it google it]. This jar file actually makes the wlst tool running. If you try to look inside wlst.cmd or wlst.sh you will find that the scripts are internally adding this jar file in CLASSPATH and calling it:
    eval '"${JAVA_HOME}/bin/java"' ${JVM_ARGS} weblogic.WLST '"$@"' [wlst.sh]
    "%JAVA_HOME%\bin\java" %JVM_ARGS% weblogic.WLST %* [wslt.cmd]
    So you can do exactly what the scripts doing from command line. do this :
    {A} $WL_HOME/server/bin/setWLSEnv.sh [or setWLSEnv.cmd] <---------------------------------------- SETS THE CLASSPATH
    You will see a lot of jar files added to your classpath and this step is exactly same when you run the wlst from the scripts in PROCEDURE 1.
    java weblogic.WLST <JYTHON SCRIPT>
    One thing you can also use the weblogic jar file to monitor any weblogic server[You have to first set the env with setWLSEnv.cmd or .sh]:
    java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> GETSTATE <SERVERNAME> [GETTING THE STATE]
    java weblogic.Admin -url t3://<IP>:<PORT> -username <USERNAME> -password <PASSWORD> FORCESHUTDOWN <SERVERNAME> [FORCIBLY SHUTTING DOWN SERVERS]
    You can do many other things with weblogic.jar not just the previous two. Refer to oracle manuals.

  • Manage Server Health Goes Blank in Admin Console

    Hello Team,
    I am continously facing issue with OSB manage server. It is running fine but health is blank in Admin Console.
    Due to which it is not responding to any user request.
    Kindly guide me to troubleshoot this issue.

    Hi,
    It is due to the problem with the JMX communication between and Admin and your OSB managed servers. Did you observed any messages related to it?
    Is it a SSL communication, then try to make sure that certificates are valid.
    As a general practice, make sure you have listen address configured for your servers. If left it blank(default), then it would be listening on the all the available host and communication would get messy in these situations.
    If still facing problem, i would suggest you enable the below debugs and raise a support case
    1. Apply the below three debug logs from console(for admin as well as Managed Server)
       weblogic->management->JMXCore
       weblogic->management->JMXDomain
       weblogic->management->JMXRuntime
    2. Restart all the servers
    If the issue, occurs, provide the debug along with the thread dump(take 5 thread dump at an interval of 5seconds) for the Managed Server(which is unknown state) and for the admin server.
    Regards
    Rosario

  • Not able to start Managed server using nohup command and failed to authenticate weblogic user

    Hi,
    I stopped weblogic Admin server, managed server and opmnctl. and restarted Admin server successfully but I'm able to start managed start without nohup command. if I use nohup command then it's not able to get authenticate and faild to start managed server. I created boot.property file with weblogic user name and password still not working. is there anyother way to suppy login credentials for managed server?
    how can I supply login credentials in below command?
    nohup ./startManagedWebLogic.sh bi_server1 t3://machine:7001 > bis1_startup.log &
    Appreciate you for your help
    Thanks
    Jay.

    /app/obiee_11g/Oracle_BI1/jdk/bin/java -server -Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics -Dweblogic.Name=bi_server1 -Djava.security.policy=/app/obiee_11g/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/app/obiee_11g/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/app/obiee_11g/wlserver_10.3 -Dwls.home=/app/obiee_11g/wlserver_10.3/server -Dweblogic.home=/app/obiee_11g/wlserver_10.3/server -Dcommon.components.home=/app/obiee_11g/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/app/obiee_11g/user_projects/domains/bifoundation_domain -Djrockit.optfile=/app/obiee_11g/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/servers/bi_server1 -Doracle.domain.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/carml -Digf.arisidstack.home=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/app/obiee_11g/oracle_common/modules/oracle.ossoiap_11.1.1,/app/obiee_11g/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -DHYPERION_HOME=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_INSTANCE=novalue -Dhyperion.home=/app/obiee_11g/Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Depm.useApplicationContextId=false -Doracle.biee.search.bisearchproperties=/app/obiee_11g/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.encoding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BISearchServiceConfiguration -Dxdo.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/bipublisher -DXDO_FONT_DIR=/app/obiee_11g/Oracle_BI1/common/fonts -Drtd.instanceName=RTD_bi_server1 -Dem.oracle.home=/app/obiee_11g/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=01scqabi01.natusmed.natus.com:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/obiee_11g/patch_wls1035/profiles/default/sysext_manifest_classpath weblogic.Server
    <Nov 17, 2013 12:24:00 AM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Nov 17, 2013 12:24:00 AM PST> <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>
    <Nov 17, 2013 12:24:01 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
    <Nov 17, 2013 12:24:07 AM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:Error: Failed to get value from Standard Input
    Enter password to boot WebLogic server:
    <Nov 17, 2013 12:24:07 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Nov 17, 2013 12:24:09 AM PST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user starting the managed server. The reason for the error is .>
    <Nov 17, 2013 12:24:09 AM PST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://01scqabi01.natusmed.natus.com:7001.>
    <Nov 17, 2013 12:24:09 AM PST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Nov 17, 2013 12:24:09 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 17, 2013 12:24:09 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Nov 17, 2013 12:24:09 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1.log is opened. All server side log events will be written to this file.>
    <Nov 17, 2013 12:24:19 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Nov 17, 2013 12:24:20 AM PST> <Critical> <Security> <BEA-090403> <Authentication for user denied>
    <Nov 17, 2013 12:24:20 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
    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: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Nov 17, 2013 12:24:20 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Maybe you are looking for