OEM 12c Admin Server not up

When I go to Admin Server URL https://host:port/console it does not work, the Management service within OEM is showing as downl.
Please help

Similar Messages

WebLogic admin server not starting.

Hi all,
I have a problem with my WebLogic Admin server not starting. Following a VM reboot last week our admin servers are no longer starting. On this particular server we have 3 admin servers serving 3 separate environments.
Theserver seems to be getting stuck right at the very start. I have tried removing tmp, cache and ldap directories. Searched for and removed all .lok files. I have manually turned on full debug to try and flush some extra information through standard out but no luck. It is very peculiar. When we have exported the domain to another box and started the admin server it has come up successfully.
This is the output from the logs - this is literally as far as it get before it hangs and does nothing. As far as I know the next thing WebLogic is doing is checking the version. Has anyone any ideas what the problem could be? It is server wide as all 3 admin servers on the same box are suffering the same problem.
This is Weblogic 10.3.2 on a Solaris vm
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Development
CLASSPATH=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/lib/tools.jar:/apps/Oracle/Middleware64/utils/config/10.3/config-launch.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.jar:/apps/Oracle/Middleware64/modules/features/weblogic.server.modules_10.3.2.0.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/webservices.jar:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/apps/Oracle/Middleware64/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/apps/Oracle/Middleware64/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/xqrl.jar
PATH=/apps/Oracle/Middleware64/wlserver_10.3/server/bin:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/jre/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin:/usr/bin:/usr/sfw/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
Starting WLS with line:
/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/apps/Oracle/Middleware64/wlserver_10.3 -Dwls.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
<09-Jan-2013 18:32:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.1-21-133393-1.6.0_20-20100512-2127-solaris-sparcv9 from Oracle Corporation>

Just a wild guess (as you have restarted the physical servers), it could be related to the entropy of the machine.
What you can try to do is edit the java.security file in the $JAVA_HOME/jre/lib/security directory.
Find the entry securerandom.source and edit the value to file:/dev/./urandom (instead of file:/dev/urandom)

Weblogic server 12c managed server not starting

Hi All,
I am a newbie in weblogic. I downloaded the weblogic server 12c and installed in development mode in my Mac OSX 10.8. I am able to create the clusters and added the managed servers in it. I started the node manager attached to the machine where the managed servers are situated. Now the admin server is working, but when i try to start the managed server, it is showing TASK IN PROGRESS and not getting started. When i checked the logs, there were no logs added.
Please help me out.
Thanks in advance
Arjun

Arjun,
Please give more details how are you trying to starting the managed Server.
1. Are you starting from the Admin console?
If yes, what is the status message in the console? Do you see any errors in the admin server console?
Did you check if the Nodemanager is reachable from the admin console ?
2. Are you starting from the command prompt ?
For eg. startManagedWeblogic.cmd ManagedServer_name
Please explain.
Thanks,
Vijaya

Admin server not running

Hello,
We are using wls 10.3.3 located in different unix machine. Using putty we work with the servers from the desktop computers. We want to monitor the JVM using Jrockit mission control from desktop. We have JRMC installed in the Windows XP desktop(JRockit Mission Control 3.1.0 (R27.6.3-40_o, 112101)). I tried to connect the JVM to JRMC using the steps in the below links.
http://weblogicserveradministration.blogspot.com/2010/10/monitoring-using-jrmc-remotely.html
http://multikoop.blogspot.com/2009/11/wls-monitoring-oracle-jrockit-jvm-with.html
And restarted the AdminServer after performing the steps, but we are not sure whether we have edited the JAVA_OPTIONS in the correct place. However the AdminServer did not start. It said the Java Virtual Machine cannot be started. Now we removed the edited settings in startWeblogic.sh file and made the file as before. And restarted the AdminServer, but the Adminserver did not start and showd below error message.
<Jul 2, 2011 5:44:59 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.config.JpsConfigurationException: /oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml (No such file or directory)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.initDefaultConfiguration(XmlConfigurationFactory.java:418)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getDefaultConfiguration(XmlConfigurationFactory.java:319)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:144)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.<init>(JpsContextFactoryImpl.java:113)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: java.io.FileNotFoundException: /oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
Truncated. see log file for complete stacktrace
>
<Jul 2, 2011 5:44:59 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 2, 2011 5:44:59 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 2, 2011 5:44:59 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
[5] Done ./startWebLogic.sh
Let me know where to change the JAVA_OPTIONS in the below startWeblogic.sh file
#!/bin/sh
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
# --- Start Functions ---
stopAll()
# We separate the stop commands into a function so we are able to use the trap command in Unix (calling a function) to stop these services
if [ "X${ALREADY_STOPPED}" != "X" ] ; then
exit
fi
# STOP DERBY (only if we started it)
if [ "${DERBY_FLAG}" = "true" ] ; then
echo "Stopping Derby server..."
${WL_HOME}/common/derby/bin/stopNetworkServer.sh >"${DOMAIN_HOME}/derbyShutdown.log" 2>&1
echo "Derby server stopped."
fi
ALREADY_STOPPED="true"
# --- End Functions ---
# This script is used to start WebLogic Server for this domain.
# To create your own start script for your domain, you can initialize the
# environment by calling @USERDOMAINHOME/setDomainEnv.
# setDomainEnv initializes or calls commEnv to initialize the following variables:
# BEA_HOME - The BEA home directory of your WebLogic installation.
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# PATH - JDK and WebLogic directories are added to system path.
# WEBLOGIC_CLASSPATH
# - Classpath needed to start WebLogic Server.
# PATCH_CLASSPATH - Classpath used for patches
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
# JAVA_VM - The java arg specifying the VM to run. (i.e.
# - server, -hotspot, etc.)
# USER_MEM_ARGS - The variable to override the standard memory arguments
# passed to java.
# PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
# DERBY_HOME - Derby home directory.
# DERBY_CLASSPATH
# - Classpath needed to start Derby.
# Other variables used in this script include:
# SERVER_NAME - Name of the weblogic server.
# JAVA_OPTIONS - Java command-line options for running the server. (These
# will be tagged on to the end of the JAVA_VM and
# MEM_ARGS)
# CLASS_CACHE - Enable class caching of system classpath.
# For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
# (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/overview.htm).
WLS_USER=admin
WLS_PW=devweblogic1
umask 037
# Call setDomainEnv here.
DOMAIN_HOME="/oracle/Middleware_1033/user_projects/domains/dev_domain"
. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
SAVE_CLASSPATH="${CLASSPATH}"
# Start Derby
DERBY_DEBUG_LEVEL="0"
if [ "${DERBY_FLAG}" = "true" ] ; then
${WL_HOME}/common/derby/bin/startNetworkServer.sh >"${DOMAIN_HOME}/derby.log" 2>&1
fi
JAVA_OPTIONS=""
SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
CLASSPATH="${SAVE_CLASSPATH}"
SAVE_CLASSPATH="${JAVA_OPTIONS}"
trap 'stopAll' 1 2 3 15
if [ "${PRODUCTION_MODE}" = "true" ] ; then
WLS_DISPLAY_MODE="Production"
else
WLS_DISPLAY_MODE="Development"
fi
if [ "${WLS_USER}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.username=${WLS_USER}"
fi
if [ "${WLS_PW}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.password=${WLS_PW}"
fi
if [ "${MEDREC_WEBLOGIC_CLASSPATH}" != "" ] ; then
if [ "${CLASSPATH}" != "" ] ; then
CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${MEDREC_WEBLOGIC_CLASSPATH}"
else
CLASSPATH="${MEDREC_WEBLOGIC_CLASSPATH}"
fi
fi
echo "."
echo "."
echo "JAVA Memory arguments: ${MEM_ARGS}"
echo "."
echo "WLS Start Mode=${WLS_DISPLAY_MODE}"
echo "."
echo "CLASSPATH=${CLASSPATH}"
echo "."
echo "PATH=${PATH}"
echo "."
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://hostname:port/console *"
echo "***************************************************"
# CLASS CACHING
if [ "${CLASS_CACHE}" = "true" ] ; then
echo "Class caching enabled..."
JAVA_OPTIONS="${JAVA_OPTIONS} -Dlaunch.main.class=${SERVER_CLASS} -Dlaunch.class.path="${CLASSPATH}" -Dlaunch.complete=weblogic.store.internal.LockManagerImpl -cp ${WL_HOME}/server/lib/pcl2.jar"
export JAVA_OPTIONS
SERVER_CLASS="com.oracle.classloader.launch.Launcher"
fi
# START WEBLOGIC
echo "starting weblogic with Java version:"
${JAVA_HOME}/bin/java ${JAVA_VM} -version
if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
echo "Starting WLS with line:"
echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
else
echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1
fi
stopAll
popd
# Exit this script only if we have been told to exit.
if [ "${doExitFlag}" = "true" ] ; then
exit
fi

Hi, where exactly in the file I need to change the settings : oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml . I might have changed the script startWeblogic.sh, but I undo the changes again, since then my admin server is not starting. Kindly help. I am not sure which script I need to change and in that script which location I have to edit?
I have used below link for help(under the section L.3.4 Other Causes), still I am not able to find anything useful from the link.
http://download.oracle.com/docs/cd/E21764_01/core.1111/e10043/aptrouble.htm#CIAFHHDD
We have the below error while stating the server with ./startWeblogic.sh command:
[root@sis-pslnx01 bin]# ./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/oracle/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/oracle/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/oracle/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/oracle/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/oracle/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/jasper/jasperreports-3.6.0.jar:/prosun/jasper/commons-digester-1.7.jar:/prosun/jasper/log4j-1.2.15.jar:/prosun/jasper/org.apache.commons.beanutils_1.6.jar:/prosun/jasper/org.apache.commons.collections_3.1.jar:/prosun/jasper/org.apache.commons.logging_1.0.4.jar:/prosun/jasper/iText-2.1.0.jar:/prosun/jasper/groovy-all-1.5.5.jar:/oracle/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/oracle/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/oracle/Middleware_1033/wlserver_10.3/server/bin:/oracle/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/oracle/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/oracle/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/oracle/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/oracle/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.username=admin -Dweblogic.management.password=devweblogic1 weblogic.Server
<Jul 5, 2011 7:14:14 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Jul 5, 2011 7:14:15 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Jul 5, 2011 7:14:17 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 5, 2011 7:14:17 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jul 5, 2011 7:14:18 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /oracle/Middleware_1033/user_projects/domains/dev_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
Jul 5, 2011 7:14:21 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: java.io.FileNotFoundException: /oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml (No such file or directory)
<Jul 5, 2011 7:14:21 PM IST> <Error> <Security> <BEA-090892> <The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.>
<Jul 5, 2011 7:14:21 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1394)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:273)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-01538: The default policy provider was not found.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:705)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-01514: The default context is missing in jps-config.xml.
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:665)
at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:650)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:271)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:265)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.config.JpsConfigurationException: /oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml (No such file or directory)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.initDefaultConfiguration(XmlConfigurationFactory.java:418)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getDefaultConfiguration(XmlConfigurationFactory.java:319)
at oracle.security.jps.internal.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:144)
at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.<init>(JpsContextFactoryImpl.java:113)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: java.io.FileNotFoundException: /oracle/Middleware_1033/user_projects/domains/dev_domain/./config/jps-config.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
Truncated. see log file for complete stacktrace
Edited by: yrk16 on Jul 5, 2011 7:02 AM

URGENT: OES 10g Admin server not coming up

Hi All,
The environment has OES 10g CP5 setup with WebLogic Server. There were no changes made to the env recently and all of a sudden OES 10g server has stopped working.
We are seeing the below exception in logs. Appreciate any help.
INFO   | jvm 1    | 2012/12/20 03:07:36 | ARME is started now
INFO   | jvm 1    | 2012/12/20 03:07:37 | <Dec 20, 2012 3:07:37 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm asiadmin.>
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Error> <Security> <BEA-090060> <The AccessDecision class "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" returned an error: com.bea.security.providers.authorization.asi.InvocationException: ArmeNOTREADY Exception: Engine did not recieve initial policy.>
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Critical> <Security> <BEA-090404> <User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
INFO   | jvm 1    | 2012/12/20 03:07:38 | weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
INFO   | jvm 1    | 2012/12/20 03:07:38 |       at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
INFO   | jvm 1    | 2012/12/20 03:07:38 |       at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
INFO   | jvm 1    | 2012/12/20 03:07:38 |       at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
INFO   | jvm 1    | 2012/12/20 03:07:38 |       at weblogic.security.SecurityService.start(SecurityService.java:141)
INFO   | jvm 1    | 2012/12/20 03:07:38 |       at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
INFO   | jvm 1    | 2012/12/20 03:07:38 |       Truncated. see log file for complete stacktrace
INFO   | jvm 1    | 2012/12/20 03:07:38 | >
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
INFO   | jvm 1    | 2012/12/20 03:07:38 | <Dec 20, 2012 3:07:37 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
STATUS | wrapper | 2012/12/20 03:07:40 | <-- Wrapper Stopped
Following are the trials made without any success:
1. changed credentials in /opt/oracle/bea/wls10_3/ales32-admin/asiDomain/servers/asiAdminServer/security/boot.properties
2. Removed /opt/oracle/bea/wls10_3/ales32-admin/work/runtime/state.chk file and restarted
3. Renamed the ldap folder under /opt/oracle/bea/wls10_3/ales32-admin/asiDomain/servers/asiAdminServer/data/ldap
4. Changed password in boot.properties and ran asipassword.sh
          $ ./asipassword.sh admin /opt/oracle/bea/wls10_3/ales32-shared/keys/password.xml /opt/oracle/bea/wls10_3/ales32-shared/keys/password.key
          Enter password for alias: admin>
          Confirm password for alias: admin>
          Password saved.
          $
Edited by: 898990 on 20-Dec-2012 04:35

We are seeing the below messages in secure_audit.log:
2012-12-20 04:30:22,369 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR Event Type = Authorization Audit Event V2 - Event Type =
Authorization Audit Event V2 -- <<Event Type = Authorization Audit Event V2 ><Subject: 2
Principal = class com.bea.security.principal.ALESDirectory("RootOrg!AdminDir")
Principal = class weblogic.security.principal.WLSUserImpl("admin")
<ONCE><<svr>><type=<svr>, application=, server=asiAdminServer, action=boot>>com.bea.security.providers.authorization.asi.InvocationException: ArmeNOTREADY Exception: Engine did not recieve initial policy
at com.bea.security.providers.authorization.asi.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:319)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Admin server not sending bootstrap servlet configuration to managed servers

I am having a bit of strange issue.
I have weblogic 8.1 SP5 domain in PROD.
14 managed servers in the domain
When i start the managed serverA, sometimes it starts, sometimes it doesnt.
By looking at admin server logs, i found the following.
When the managed ServerA doesnt start, the admin server has the following log snippet
<<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server ServerA.>
####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA>
####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
When the managed ServerA starts, the admin server has the following log snippet
Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server serverA.>
####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA.>
####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
####<Apr 14, 2009 2:38:21 AM EDT> <Info> <Configuration Management> <catlmsxp166.corp.cox.com> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> *<The bootstrap servlet has finished sending the configuration to serverA.>*
The difference is that admin server unable to send the bootstrap servlet configuration to managed servers, as highlighted above
Has anyone encountered this issue?
If so, is there is solution to this?
Right now i am doing the work around (Which is restart admin server and then start managed server, for every managed server that does not start)
But i cant do this all the time.
MY domain has 14 managed servers. All of them exhibit similar behaviour.
Some times they start, some times they dont.
Edited by: gvamsius on Apr 14, 2009 1:22 PM
Edited by: gvamsius on Apr 14, 2009 1:23 PM

Honestly I've never seen a similar problem.
Could you show us the "standard out" when you start the servers?
Could you to show us the standard out when you start the servers?

IPM Group Admin Server not Working, Its giving Error

IPM Group Admin Server giving this error, Bu the Process are running
OGS Server Error
Error
Error in communicating with IPMGroupAdministration Server.
It may be down or not yet up. Please make sure that the IPMGroupAdministration Server is up and running, then refresh the page.
45.
IPMOGSServer
Program started - No mgt msgs received
12556
0
0
11/3/2010 2:13:56 PM
Not applicable
9.
CMFOGSServer
Program started - No mgt msgs received
7184
0
0
11/1/2010 10:09:00 PM
Not applicable
Please Help

Are you using ACS? If so, verify you have the correct privileges to access the application with your group settings.

NetApp plugin for OEM 12c - DB is not on NFS mounted storage. DB Storage Perf Report empty

Hi, I have installed NetApp Plugin for OEM 12c (12.1.0.3.1) for a Netapp vFiler used for SMO. "Database Storage Utilization" and "Consolidation Database Storage Performance" empty. "Database is not on NFS mounted storage. Hence, no views available." - a. We are using ASM lun created on NFS. Does this means it will not appear in the plugin report ? - b. If point a. is true, is there a way to make the data appear ? I had already verified the BELOW. Only for point 4, I observed MGMT$DB_DATAFILES."OS_STORAGE_ENTITY" is NA (even though the ASM disk is actually on a NFS mount) : 1. Database discovery is done in EM12c . 2. Go to the database “HOST” target in EM 12c and click on the host target on which database resides. From host target drop down, click on “Host-> StorageDetails”. It will launch the “Storage Details” page. Please refer attached screenshot. There is a table displayed on bottom of screen and click on “File Systems” tab and check that your discovered database storage mount point is shown there. (Please note that whenever you define new mount point on host, this list should reflect the change.), otherwise, Database Performance views will not work. This mount point discovery is updated periodically. (It might be possible that DB views are not working because this discovery might not have finished) 3. Please click on NetApp Storage Target type and go to “Target HomePage drop down ->All Metrics”. Please click on “Volume List” metric and confirm if the volume is listed there on which database resides. 4. If all above steps holds good, please execute the below query on EM 12c repository and send the result: SELECT V2.TARGET_NAME, V1.FILESYSTEM, SUBSTR(V1.FILESYSTEM,INSTR(V1.FILESYSTEM,':')+6, (CASE WHEN (INSTR(V1.FILESYSTEM,'/',1,3) > 0) THEN INSTR(V1.FILESYSTEM,'/',1,3) - INSTR(V1.FILESYSTEM,'/',1,2) - 1 ELSE 100 END)) "VOLUMENAME" FROM MGMT$STORAGE_REPORT_NFS V1, MGMT$DB_DATAFILES V2 WHERE V1.MOUNTPOINT = V2.OS_STORAGE_ENTITY and V2.TARGET_NAME=''

Hi Aik, Change in SQLs will not work. There is lot of code for data discovery.We need to have discovery mechanism integrated in our plug-in for ASM LUNS.ASM LUN based database discovery has been planned to support in future release of plug-ins. Can you please share following details about OEM plug-in usage:1. Company Name2. ONTAP OS (cDOT / 7-mode which version)3. Nature of Databases (Only ASM or NFS based)4. Are your currently using this plug-in for NFS databases? If yes, how it helps to simplify your database administration. We will share your feedback to Product Management for support of ASM. Regards,Sachin Maheshwari

Cloned OMS - WebLogic Admin Server not available....

Greetings,
We are working our way through an active active R4 OMS setup, and we just successfully cloned oms1 to oms2 via cloud control, and executed the post install steps. We now need to access each of the OMSs WebLogic Admin Server Console to confirm LDAP settings, and the oms2 WebLogic Admin Server Console is unavailable. The oms2 clone has the same WebLogic Admin Server details as oms1 (see below).
Is that by design, i.e. only one WebLogic Admin Server Console with two load balanced OMSs?
Which files do we need to edit on oms2 to get oms2's WebLogic Admin Server on-line?
oms1:
/u01/app/oracle/product/middleware_r4/oms/bin/emctl status oms -details
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Admin Server is RUNNING
oms2:
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Thank you,

The WLS admin server only exists on the first OMS host. Usually an SLB is used for load balancing.
For information on HA (High Availability) solutions, see:
http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_intro.htm#EMADV9611
Regards,
- Loc

Admin-serv not starting Solaris 8

Hello,
I have installed Sun One Application Server 7 in Solaris 8 and I get the following error when I try to start the admin-serv:
CORE1116: Sun ONE Application Server 7.0.0_01
INFO: CORE3016: daemon is running as super-user
INFO: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_01] from [Sun Microsystems Inc.]
INFO: ADM0002:System MBean initialized:[ias:type=controller]
INFO: ADM0002:System MBean initialized:[ias:type=configurator]
INFO: ADM0001:MBeanServer initialized successfully
INFO: ADM0005:Timestamp files for configuration created for:[admin-server]
INFO: ADM0005:Timestamp files for configuration created for:[server1]
INFO: ADM0102: Starting a thread for tracking manual changes
WARNING:
com.iplanet.ias.cis.connection.ConnectException: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5990:TCPBlockingChannel.JNI_ConnectNative: PR_Connect() failed
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:187)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:102)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:118)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:131)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:142)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:76)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:80)
at com.sun.corba.ee.internal.corba.InitialNamingClient.locateObject(InitialNamingClient.java:905)
at com.sun.corba.ee.internal.corba.InitialNamingClient.getIORUsingHostInfo(InitialNamingClient.java:724)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveCorbaloc(InitialNamingClient.java:700)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveUsingORBInitRef(InitialNamingClient.java:668)
at com.sun.corba.ee.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1237)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1129)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.java:3006)
at com.sun.enterprise.naming.SerialContextProviderImpl.initSerialContextProvider(SerialContextProviderImpl.java:47)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:363)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1415)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:212)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5990:TCPBlockingChannel.JNI_ConnectNative: PR_Connect() failed
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.connectNative(Native Method)
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.doConnect(TCPBlockingChannel.java:171)
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.<init>(TCPBlockingChannel.java:54)
at com.iplanet.ias.cis.channel.tcp.TCPChannelFactory.createChannel(TCPChannelFactory.java:97)
at com.iplanet.ias.cis.channel.ChannelManager.createChannel(ChannelManager.java:58)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:162)
... 18 more
WARNING:
com.iplanet.ias.cis.connection.ConnectException: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5990:TCPBlockingChannel.JNI_ConnectNative: PR_Connect() failed
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:187)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:102)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:118)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:131)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:142)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:76)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:80)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:694)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:630)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1155)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:823)
at com.sun.corba.ee.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1245)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1129)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.java:3006)
at com.sun.enterprise.naming.SerialContextProviderImpl.initSerialContextProvider(SerialContextProviderImpl.java:47)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:363)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1415)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:212)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5990:TCPBlockingChannel.JNI_ConnectNative: PR_Connect() failed
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.connectNative(Native Method)
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.doConnect(TCPBlockingChannel.java:171)
at com.iplanet.ias.cis.channel.tcp.TCPBlockingChannel.<init>(TCPBlockingChannel.java:54)
at com.iplanet.ias.cis.channel.tcp.TCPChannelFactory.createChannel(TCPChannelFactory.java:97)
at com.iplanet.ias.cis.channel.ChannelManager.createChannel(ChannelManager.java:58)
at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:162)
... 18 more
SEVERE: NAM5002: Exception in SerialContextProviderImpl InsertSerialContextProvider().
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:203)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:76)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:80)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:694)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:630)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1155)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:823)
at com.sun.corba.ee.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1245)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1129)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.java:3006)
at com.sun.enterprise.naming.SerialContextProviderImpl.initSerialContextProvider(SerialContextProviderImpl.java:47)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:363)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1415)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:212)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
SEVERE: CORE5082: Exception running j2ee services: [java.rmi.RemoteException]
SEVERE: CORE5091: Error executing J2EE server ...
java.lang.RuntimeException
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:564)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1415)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:212)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: java.rmi.RemoteException
at com.sun.enterprise.naming.SerialContextProviderImpl.initSerialContextProvider(SerialContextProviderImpl.java:61)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:363)
... 3 more
SEVERE: CORE5093: Error executing J2EE server
SEVERE: CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1433)
at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:212)
at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
Caused by: java.lang.RuntimeException
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:564)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:1415)
... 2 more
Caused by: java.rmi.RemoteException
at com.sun.enterprise.naming.SerialContextProviderImpl.initSerialContextProvider(SerialContextProviderImpl.java:61)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:363)
... 3 more
SEVERE: CORE3186: Failed to set configuration
Can anyone help me?
Everything looked to go well in the instalation process so I have no idea of what could be happening. I also post the install.log content, I hope this helps:
INFO - Start core server configuration.
INFO - Domain successfully created
INFO - Server instance successfully created
INFO - End core server configuration.

Forget this post.

What about the admin server not working?

Hello,
I noticed that, even when the admin server is down, the LDAP server nicely serves search, create or modify clients requests. At least the extended operation persistent search works as well.
My question is what does stop working in the DS if the admin server is down?
- Likely the Server console.
- SNMP monitoring?
- Replication?
- SSL authentication?
- What else?
My concern is of course Linux ES 3.0 support.
Thanks for all your answers.

The admin server is just a http server used for administration with the console. Most admin functions can also be done from the command line, so it's really GUI administration that you are losing.

OEM 12c Agent does not show down status.

Hi, I'm testing EM 12c. I added host target to oem and then kill agent process on host.
When open agent page (Setup-Agent-Testingagent) see error.
Communication between the Oracle Management Service host to the Agent host is unavailable. Any functions or displayed information requiring this communication link will be unavailable. For example: deleting/configuring targets, uploading metric data, or displaying Agent home page information such as Agent to Management Service Response Time (ms).
But status agent and host show up in EM.
I try resync agent, But nothing has changed it.
./emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Agent is Not Running
Other target (hosts,agent) show status correctly.
Thanks for help.

EM is showing Host is up makes sense. If I remember correct the OMS pings the host if the agent is down. This will succeed so the host will show up.
Why the agent is showing up does not make sense to me. The agent sends a signal every (default) 120 seconds. If no signal is received by the OMS the OMS sends a reverse ping to the agent. If this does not succeed the agent and its monitored targets should get the state “Agent Unreachable”.
Eric

Admin Server not starting.

Hi,
I'm trying to start weblogic admin sever through script.
The server is not coming up. I'm gettign the following error
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[com.bea.wli.init.WLIDBCreateException: javax.naming.NameNotFoundException: Unable to resolve 'cgDataSource' Resolved ; remaining name 'cgDataSource']
I tried commenting the 'cgDataSource' line in config.xml and tried that didn't work out.
Please suggest me how can i get rid of this error & start up the server.
Thank you in advance.

You can modify the setting in the config file for the startup class.
The reason why the weblogic server is failing to start is that you might have marked 'Failure is Fatal' for the startup class. This prevents the server to start if the startup class fails to load.
The reason why startup class is failing to load could be that it is trying to lookup a datasource from JNDI before the server has initialized the JDBC services. You can configure the startup class to load only after the JDBC services are initialised.
The below startup class configuration should be used for if you want the startup class to load after JDBC initialisation and after application deployment
<startup-class>
<name><startup class Name></name>
<target><Server to target></target>
<deployment-order>1</deployment-order>
<class-name><Actual Name of the startup class></class-name>
</startup-class>
The below startup class configuration should be used for if you want the startup class to load after JDBC initialisation and before application deployment
<startup-class>
<name><startup class Name></name>
<target><Server to target></target>
<deployment-order>1</deployment-order>
<class-name><Actual Name of the startup class></class-name>
<load-before-app-activation>true</load-before-app-activation>
</startup-class>

Weblogic Admin Server not starting after Virtual Server move

Hi, we've migrated a VMware virtual server, and our Weblogic Admin (and managed IRM server) no longer start. The associated log files don't get updated and only the following info is present in the Command window, which I can only see if I use the /k switch, otherwise the windows shut immediately.
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar
;C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sys_manifest_classpath\weblog
ic_patch.jar;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sys_manifest_cla
sspath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sys_m
anifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\JDK160~1\lib\tools.jar;C
:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~3\WLSER
V~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~3\modules\features\weblogic.serve
r.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\webservices.jar;
C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~3\modules
\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\common
s-cli-1.1.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa
-infra-mgmt.jar;C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:
\Oracle\MIDDLE~3\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~3\
WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~3
\patch_oepe1033\profiles\default\native;C:\Oracle\MIDDLE~3\patch_ocp353\profiles
\default\native;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\native\win\32;C:\Oracle\MID
DLE~3\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1\bin;C:\Oracle\
MIDDLE~3\JDK160~1\jre\bin;C:\Oracle\MIDDLE~3\JDK160~1\bin;C:\oraclexe\app\oracle
\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wb
em;C:\Program Files\Java\jdk1.6.0_20\bin;C:\Program Files\Apache Software Founda
tion\Apache2.2\modules;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\native\win\32\oci920
_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~3\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThre
shold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -
Djava.security.policy=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic.policy
-Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~3\WLSERV~1.3 -Dwls.home=C:\O
racle\MIDDLE~3\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~3\WLSERV~1.3\s
erver -Ddomain.home=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1 -Dcommon.compo
nents.home=C:\Oracle\MIDDLE~3\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons
.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Or
acle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.do
main.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1 -Do
racle.server.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWC
ON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~3\USER_P~
1\domains\IRM_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=
oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~3\USER_P~1\
domains\IRM_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~
3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateT
ypesDirectory=C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracl
e\MIDDLE~3\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEna
bled=false -Dirm.oracle.home=C:\Oracle\MiddlewareNew\Oracle_ECM1 -Dem.oracle.ho
me=C:\Oracle\MiddlewareNew\oracle_common -Djava.awt.headless=true -Dweblogic.man
agement.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToC
onsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sy
sext_manifest_classpath;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sysex
t_manifest_classpath;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sysext_man
ifest_classpath weblogic.Server
Is there another log file I could look at to get more info? None of the domain log files are updated.
Thanks

Thanks for the reply, this looks fine (I think)..the below is the output
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator.SEALEDINFO-PROD>cd C:\Oracle\MiddlewareNew\user_projects\
domains\irm_domain\bin
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain\bin>setdomainenv.cmd
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java weblogic.version
WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401
Use 'weblogic.version -verbose' to get subsystem information
Use 'weblogic.utils.Versions' to get version information for all modules
C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>

Shutdown(block='false') only works via Admin Server, not managed servers

Hello,
We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
connect(user, pwd, http://localhost:7001)
shutdown('myserver1', 'Server', block='false')
shutdown('myserver3', 'Server', block='false')
shutdown('myserver5', 'Server', block='false')
shutdown('myserver7', 'Server', block='false')
shutdown('myserver9', 'Server', block='false')
All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
connect(user, pwd, url='t3://localhost:8001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:9001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:10001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:11001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:12001')
shutdown(block='false')
disconnect()
NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
Best regards,
Michael

Hi Mike,
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
or
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Regards,
Kal

OEM 12c Admin Server not up

Similar Messages

Maybe you are looking for