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?

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)

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)

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.

Mail server not sending mail properly

I'm sure there is a quick fix to this that I'm not seeing but hopefully someone knows this better than I do.
We are in transition from a Plesk Mail system over to our OSX Server Mail Server. We are transitioning over our accounts by domain and not doing every domain at once which would be a hassle. We have transitioned over the primary domain and one virtual domain so far. We have two more virtual domains to go.
This third virtual domain has a lot of users and I just finish importing them all. I followed the write up on how to do this properly with doing it in WGM and then duplicating it in Postfix since virtual domains is broken. So I followed all those instructions but something weird is happening. We have not cut over our MX record yet for that virtual domain as we want to prepare our clients for when we do. But what is happening is if I send an e-mail from my account in the primary domain to a person in the virtual domain that we have not cut over yet, they won't get any mail from me. It's almost like the OSX server thinks it controls that virtual domain and delivers it to itself instead of passing it on. Yet I look in my virtual domain settings and I don't have that virtual domain setup or turned on. I just have the user accounts in.
There has to be a way for the OSX server not to take control of virtual accounts until I'm ready for it to. Anyone know how to fix this?
-Brian

So I thought this was fixed but I'm still hearing that users of the virtual domain that we haven't cut over yet are not getting their e-mail. It seems like our server is holding onto messages that need to be sent on to the old server for now until I change the MX record.
Here is the main.cf file output:
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
messagesizelimit = 10485760
myhostname = mail.xpmedia.com
mailbox_transport = cyrus
mailboxsizelimit = 0
virtual_transport = lmtp:unix:/var/imap/socket/lmtp
virtualmailboxdomains = hash:/etc/postfix/virtualdomainsxp
virtualaliasdomains = hash:/etc/postfix/virtual_domains
virtualaliasmaps = hash:/etc/postfix/virtual
mydomain = xpmedia.com
enableserveroptions = yes
inet_interfaces = all
relayhost =
mydestination = $myhostname,localhost.$mydomain,localhost,xpmedia.com
smtpdsasl_authenable = yes
smtpduse_pwserver = yes
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdpw_server_securityoptions = login,cram-md5,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
smtpdclientrestrictions = permit_mynetworks rejectrblclient zen.spamhaus.org permit
mapsrbldomains =
mynetworks = 98.173.129.235,127.0.0.0,127.0.0.1
localrecipientmaps =
luser_relay = postmaster
transportmaps=hash:/etc/postfix/transportmaps
Here is the Transport Maps file output:
xpmedia.com :
xpmissions.com :
xpwebchurch.com smtp:mail.xpmissions.com:587

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

Login to the OMS manahement server and start the server using
emctl start oms

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.

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

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

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.

How to upgrade the Admin Server to WLS 9.2.3 while Managed on 9.2.2

HI,
I have a WLS 9.2.2 domain with Admin and 2 Managed instances clustered. Admin and Managed Servers are on different machines.
I want to upgrade only the Admin Server to WLS 9.2 MP3 while all my Managed Servers are in WLS 9.2 MP2.
Can any one provide me the detailed steps on how to upgrade only the Admin server to WLS 9.2 MP3?
And I read in the Weblogic documentation that this supported. But could not find any detailed steps on how to upgrade only the Admin server to the Major version.
Thanks in Advance.

Hi
1. "And I read in the Weblogic documentation that this supported". Can you please provide the link or documenation that exactly says that this is Supported ???
2. As far as I know, one of the basic requirements for Weblogic Cluster with managed servers across different remote machines is, all the machines, Admin and Managed Servers machines should have Exact Same Version (including Service Pack) of WLS deployed. Right now I do not have this link on top of my head. But this is the only Supported and one basic requirement for Weblogic Cluster.
Since WLS uses all Shared Modules and each Shared module do have like Implementation and Specification Version. If you upgrade admin server domain, most probably config.xml file will be upgraded with all modules version as 10.0.2.3 (something like that). This means when you restart Managed Servers, they will get a new copy of config.xml file from admin server machine. So now on Managed Servers all these modules (10.0.2.3 etc) should exist on their local machines. This is just my thought.
Thanks
Ravi Jegga

EPM single Managed Server for all applicatoins vs EPM multiple managed servers

Hi Guys
There are two options of setting my managed serves in weblogic
1 - All application comes under single managed server.
2 - Every application have it's own managed server.
(Please correct me if there are other ways to other than this.)
What are the advantages and disadvantages of both?
Regards

Actually the purpose of these purely lies in your usage and env capacity ..
Suppose I have a test env where in I frequently suppose to restart the services , then I will better go for single managed option as I would not like wasting my time in stopping and starting of services .
Note this will have high RAM burden as you would be starting all the service even if you don't need that .
If you are constantly bringing services up and down you want the control of being able to choose what you are restarting. Lets say in your Test environment you want to change the deployment settings of JVM, change the Planning properties, change Essbase Server settings, you hose FDMEE and need to restart.... this list can easily go on ... you want to be able to restart the individual component rather than everything. You cannot accurately test patches in Test, because they don't simulate Prod - so you have to bank on having another pre-prod environment to do all of this in. You cannot tune accurately, because you have no control over the individual web apps.
As Dattatray said " 2. as there is only one window service, RAM and processor consumption will be less"
as JohnGoodwin said "I am not a fan of the single managed server unless it is for low resourced machine, e.g. laptop or POC, it is more trouble than it is worth."
The RAM usage is going to be lower, not higher.

BizTalk Admin Console not responding when loading configuration

Hi All,
I have a BizTalk 2013 R2 test environment which has separate BizTalk and SQL servers.
Due to something went wrong with the BizTalk server so I built another BizTalk
server and joined the same BizTalk group and I also moved the master secret
server to the new BizTalk server. I removed the old BizTalk server from the
group and shut the old server down.
But when I am using the new server to load the configuration for any receive or send ports,
the MMC gave me the "this snap-in is not responding" alert and if I canceled the alerts a couple of times, the configuration info can be loaded.
The admin console is fast when not loading configuration though.
Does anybody have any ideas what could be wrong?
Thanks,
David
David

This issue could be because of many reasons. Work on the below pointers.
1) I would suggest you to start with performing BizTalk Repair to avoid any registry issues, because in most of the cases Admin console related issues are solved by BizTalk repair only.
2) Check if SQL Server and MSDTC service is running properly.
As a Last option collect DebugDiag logs and try to analyze the same.
https://www.microsoft.com/en-us/download/details.aspx?id=42933
Check the below articles as well.
http://blogs.msdn.com/b/biztalknotes/archive/2014/02/20/biztalk-server-admin-console-fails-to-launch.aspx
http://support.microsoft.com/en-us/kb/2449532
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

Name server not updated in development configuration after change of SLD

Hi Guys
Hope you can help me with this one.
We have moved our SLD from one server to another.
After this we changed the name server in NWDI and in NWDS.
In NWDS i removed the development configuration and reimported it, but when I do this, a popup box shows the details of the development configuration and the name server is still the old SLD server. This means that when I start the NWDS I get an error saying that the name server host is unreachable.
Where do I change this?
I found out that the name server is setup in the .confdef file under .dtc\0 in the field called name-server-url. If I change this manually in the file, it works. But if I remove the development configuration and reimport it again, I am taken back to the old name server again.
It seems as if something has to be changed in NWDI, but I can't figure out what.
Can anybody help?
Cheers,
Jacob Vennervald

Hi Jacob,
I would proceed as follows: 
- login to your new SLD 
- go to the technical systems in the landscape area of the SLD 
- in the filter drop down select AS JAVA 
- check if your NWDI has reported to this SLD in the last 12 or 24 hours, you can check this on the "last update" column 
- if your system has reported to this sld the last few hours this is good if not go to the step "change J2ee to new sld" i will descirbe later. 
- remember the name of the system here. it is like sid on dbhostname. 
- got to sld administration (link on top) choose content maintenace in administration 
- in the subset filter select "All with instances" as class set SAP AS JAVA Cluster 
- you should find your system there. click on it. 
- in the new screen find a link in the middle top <nr> associated instances -> click it 
- in the next screen you will see the relationship of the technical system to the rest of the sld data. 
- there should be a topic called "hosted application server" 
- the should be an entry like: system landscape directory: sld on sid on server -> click it 
- here you will see the data for this hosted system. You can find the cim/url definig the SLD you will find the roles. Landscape and name server should assigend and so on here you can chage the SLD url. 
You can although proceed as follows. This as well requieres you nwdi to report and use this sld in j2ee see below if not. 
- on sld startscreen choose landscapes in the landscapes part of sld 
- select landscape type nwdi systems 
- if there is no landscape you can create one 
- in the landscape ypu can assinge systems. The sld should be availabel to choose. 
- once in the landscape you can view the system and you can change the CIM Server url and the roles there aswell its just another view on the content. 
 
you can although check: 
- open name reservation from develpoment part of start screen 
- here you should find a button about enabling or disabling the sld for nwdi usege. this should be of course enabled... 
 
"change J2ee to new sld" Ok and here what to do or to check if you are not sure if your NWDI uses/reports to the new sld. 
- Go to the nwdi server an open Visual admin i asume you are running a 7.0 Di if not let me knoe i can although tell you for CE. 
- ok in VA. select on of your server nodes->services->SLD data supplier. 
- an overview page will show up. 
- select the http settings tab in the lower middle. 
- https settings will tell the j2ee where to report to. Verify the data and change if needed. use the lightinigbolt button on top to transfer data to the sld. have a little patiance if your data is not shown immediately in your sld,. it may take 1-2 minutes until it is shown in the gui. 
- switch to cim client generation tab. those paraemters will tell your j2ee from what sld to read data from. It is important to understand that you may report to one sld but to read from antioher. depending on your sld landscape. The CIm CLient should use the same Sld as your NWDI uses in CMS setting. 
- if all is setup. do a cim client test. 
 
Allright. This is all I know on how the NWDI is integrated in SLD. Hope you can resolve your problem wiht this steps.
 
Have a good time 
Jan

Admin server not sending bootstrap servlet configuration to managed servers

Similar Messages

Maybe you are looking for