WLS 10.3.1 Managed Server + WLS 10.3.3 AdminServer
I have installed WLS 10.3.3 on Solaris. I have installed WLS 10.3.1 on Windows. I have created a domain in 10.3.3 version. I would like to create a managed server on 10.3.1 installation.
Is this possible?+
When I tried I got the following error:
*<May 26, 2010 4:39:06 PM IST> <Error> <Management> <BEA-141252> <The domain version, 10.3.3.0, is greater than the release version, 10.3.1.0, of this server.>*
<May 26, 2010 4:39:06 PM IST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through URL: http://10.1.51.155:9999/bea_wls_management_internal2/Bootstrap, user: admin
weblogic.management.configuration.ConfigurationException: [Management:141252]The domain version, 10.3.3.0, is greater than the release version, 10.3.1.0, of this server.
at weblogic.management.provider.internal.BootStrapHelper.getBootStrapStruct(BootStrapHelper.java:147)
at weblogic.management.provider.internal.RuntimeAccessImpl.initialize(RuntimeAccessImpl.java:432)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:49)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
Edited by: user12009192 on May 26, 2010 5:14 PM
I think your domain and managed server must be same version....
Similar Messages
-
WLS 10.3.5 Managed server is not starting in Windows 7
Hello there,
I had installed SOA suite 11 and weblogic server 10.3.5. setDomainEnv is setting environment variables like below.
Path
C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\Oracle\Middleware\jdeveloper\ant\bin;C:\Oracle\Middleware\jdk160_24\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Program Files\Java\jre7\bin;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
Classpath
C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\sip\server\lib\weblogic_sip.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;.;C:\Oracle\Middleware\jdk160_24\lib;C:\Oracle\Middleware\jdeveloper\ant\lib;
Now i have given this command in user_domains/../bin folder
startManagedWebLogic.cmd soa_managed_server01 http://suchalam-ws:7002
But the managed server is shutting down. below is the trace from windows7 command prompt.
this server is being started in managed server independence mode in the absence of
the admin server.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Aug 30, 2012 1:13:28 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\Oracle\Middleware\user_projects\domains\sudheers_domain\servers\soa_manage
d_server01\logs\soa_managed_server01.log will be rotated. Reopen the log file if
tailing has stopped. This can happen on some platforms like Windows.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\Oracle\Middleware\user_projects\domains\sudheers_domai
n\servers\soa_managed_server01\logs\soa_managed_server01.log00011. Log messages
will continue to be logged in C:\Oracle\Middleware\user_projects\domains\sudheer
s_domain\servers\soa_managed_server01\logs\soa_managed_server01.log.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\Oracle\Middleware\user_projects\domains\sudheers_domain\servers\soa
managedserver01\logs\soa_managed_server01.log is opened. All server side log e
vents will be written to this file.>
Aug 30, 2012 1:13:30 AM oracle.security.jps.internal.common.util.XmlSchemaValida
tionUtil$StrictErrorHandler warning
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation valu
e = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have e
ven number of URI's. Location: line 2 column 272.
<Aug 30, 2012 1:13:39 AM IST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Aug 30, 2012 1:13:51 AM IST> <Warning> <JTA> <BEA-110503> <The migrator(the Adm
inServer for manual JTA migration policy, or the Singleton Master for automatic
JTA migration policy) is not available. Will skip JTA TRS failback because isStr
ictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS
of soa_managed_server01 has been migrated to backup server and the backup server
is accessing the TLOG of soa_managed_server01. More safety can be achieved by s
etting isStrictOwnershipCheck to [true].>
<Aug 30, 2012 1:13:52 AM IST> <Warning> <Management> <BEA-141277> <The JMX MBean
PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was cre
ated without the hooks for the WLS security infrastructure. The Platform MBeanSe
rver will NOT be used and Platform MBeans will NOT be available via the WLS Runt
ime or Domain Runtime MBeanServers. This can occur if you have defined Platform
MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or
JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system
properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBean
ServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be a
vailable via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to fa
lse.>
<Aug 30, 2012 1:14:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Aug 30, 2012 1:14:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Aug 30, 2012 1:14:04 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initial
ize the application 'wsm-pm' due to error weblogic.management.DeploymentExceptio
n: [J2EE:160149]Error while processing library references. Unresolved applicatio
n library references, defined in weblogic-application.xml: [Extension-Name: orac
le.wsm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1
.1, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing lib
rary references. Unresolved application library references, defined in weblogic-
application.xml: [Extension-Name: oracle.wsm.seedpolicies, Specification-Version
: 11.1.1, Implementation-Version: 11.1.1, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(
CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.jav
a:58)
Truncated. see log file for complete stacktrace
>
<Aug 30, 2012 1:14:04 AM IST> <Notice> <SipServer.Resource> <BEA-332401> <Initia
lizing SipServer Resource with configuration com.bea.wcp.sip.management.descript
or.beans.SipServerBeanImpl>
<Aug 30, 2012 1:14:08 AM IST> <Notice> <WLSS.Engine> <BEA-330071> <WebLogic Sip
Server "soa_managed_server01" patch version: WebLogic Server 10.3.5.0 Fri Apr 1
20:20:06 PDT 2011 1398638
Javax Server Pages Client Capable 1.2 Tue Jul 13 02:43:41 EDT 2010
Expression Language 2.1 for JSP 1.0 Sun Jul 18 23:17:34 PDT 2010
Javax Enterprise Servlets Client Capable 1.0 Thu Aug 2 12:41:25 EDT 2007
Eclipse Java Development Tools 3.5.2 Thu Sep 2 09:47:11 EDT 2010
WebLogic java compiler utils package Client Capable 1.2 Thu Feb 11 03:38:50 EST
2010
WebLogic WebApp Container Public API Client Capable 1.4 Fri Oct 1 20:01:15 PDT 2
010
Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011
Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu F
eb 3 16:30:47 EST 2011
ANTLR Java based compiler generator Client 2.7 Mon Jun 11 12:19:48 EDT 2007
WebLogic Descriptors for J2EE 1.5 Wed May 5 14:32:58 EDT 2010
WebLogic Descriptors for J2EE 1.5 Binding Bundle
WebLogic Specific Descriptors 1.3 Tue Sep 14 18:48:42 PDT 2010
WebLogic Specific Descriptors 1.3 Binding Bundle
WebLogic Datasource 1.9 Tue Oct 26 13:50:26 PDT 2010
WebLogic Datasource 1.9 Binding Bundle
WebLogic Beangen Client Capable 1.7 Wed Feb 24 16:02:48 PST 2010
WebLogic Beangen 1.7 Binding Bundle
WLDF Accessor Client Capable 1.5 Fri Sep 3 17:10:52 EDT 2010
WLDF Accessor 1.5 Binding Bundle
WebLogic Management Core Interfaces Client Capable 2.8 Thu Mar 3 12:10:10 EST 20
11
WebLogic Management Core Interfaces 2.8 Binding Bundle
WebLogic EJBGen Client Capable 1.1 Thu Jun 3 13:17:07 EDT 2010
Apache Byte Code Engineering Library (BCEL) extracted from 5.2.zip from http://j
akarta.apache.org/site/downloads/downloads_bcel.cgi with packages renamed from o
rg.apache.bcel to com.bea.core.repackaged.apache.bcel Client 5.2 Tue May 15 09:5
2:37 EDT 2007
Apache commons collections package 3.2 Tue Mar 20 15:48:25 MDT 2007
Apache commons lang package 2.1 Tue Mar 20 15:48:30 MDT 2007
Apache commons pool package 1.3 Tue Mar 20 15:48:36 MDT 2007
Apache commons io 1.4 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache commons fileupload 1.2.1 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache DOM implementation 1.0 Tue Mar 20 15:36:46 MDT 2007
Apache Logging Support 1.0 Tue Mar 20 15:36:50 MDT 2007
Apache OpenJPA classes 1.2 Thu Jul 22 05:16:07 EDT 2010
XMLBeans - Apache SVN rev 962560 2.1 Thu Jul 15 09:52:54 EDT 2010
BEA Logging Runtime Support Client Capable 1.8 Mon Jun 7 12:07:02 PDT 2010
BEA Common Security Open SAML 1.0 Fri May 14 20:18:10 PDT 2010
BEA OpenSAML 2.0 1.0 Wed Mar 24 13:18:27 PDT 2010
bea-harvester-api2.0 Client Capable 2.3 Mon Feb 15 14:41:06 EST 2010
bea-harvester-jmx2.0 Client Capable 2.3 Wed Feb 3 11:54:03 PST 2010
bea-harvester-utils Client Capable 1.4 Mon Feb 15 14:41:06 EST 2010
bea-mbean-typing-util 1.4 Wed Feb 24 19:15:33 EST 2010
Javolution 3.7.19 3.7 Tue Aug 28 17:32:21 PDT 2007
Joda-time 1.2.1 1.2 Tue Aug 28 17:32:27 PDT 2007
BEA STAX Build Time Support 1.5 Tue May 4 07:32:25 PDT 2010
BEA STAX Runtime Time Support Client Capable 1.7 Wed Aug 4 19:40:47 EDT 2010
BEA Generic Annotations Client Capable 1.3 Sat Jul 11 00:30:54 EDT 2009
BEA Kodo 1.4 Mon Feb 7 16:22:04 PST 2011
BEA Kodo Integration Client Capable 1.6 Sun Nov 22 16:29:06 PST 2009
BEA Kodo Integration 1.6 Binding Bundle
BEA Kodo Integration Tools 1.4 Thu Feb 3 16:07:53 EST 2011
XML Beans Marshalling (package renamed com.bea) SVN 962560 2.3 Thu Mar 3 12:10:1
0 EST 2011
WebLogic Utils Client Capable 1.9 Thu Mar 3 12:10:10 EST 2011
Aspect 5.3 Fri Jun 4 14:55:18 PDT 2010
BEA Apache Commons Logging Repackaged 1.2 Mon Jun 11 12:47:12 EDT 2007
Spring Framework 1.1 Thu Dec 3 12:21:08 EST 2009
Pitchfork 1.3 Thu Jun 3 13:17:07 EDT 2010
${description} 1.2 Fri Jun 25 16:25:26 EDT 2010
CSS i18n 1.0 Fri Oct 8 10:32:52 EDT 2010
CSS xacml 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML2 Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Interfaces 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security API 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security JDK Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 Management JavaBeans 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
XACML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Environment 1.0 Fri Oct 8 10:32:52 EDT 2010
RSA certj 3.1 Wed May 5 15:11:55 PDT 2010
Netscape LDAP JDK 1.2 Mon Jun 7 15:56:47 EDT 2010
Commons Networking Utilty classes 1.0 Wed Feb 6 15:01:03 PST 2008
WebLogic SAAJ 1.6 Wed Jun 16 22:02:31 EDT 2010
WebLogic STAX Client Capable 1.9 Thu Feb 10 18:00:52 PST 2011
jaxb-impl.jar taken from Glassfish JAXB 2.1.9 1.0 Fri Aug 20 14:37:07 EDT 2010
jaxb-impl.jar taken from Glassfish JAXB 2.1.12 1.0 Thu May 6 16:10:04 PDT 2010
resolver.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:24 EST 2009
Fastinfoset.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:27 EST 2009
jaxws-rt.jar taken from Glassfish JAXWS 2.1.5 1.2 Mon Feb 28 17:53:01 PST 2011
Java.net implementation of MimePull.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu
Dec 3 11:46:33 EST 2009
Codehaus STaX Interfaces 3.0.1 1.0 Mon Mar 8 20:49:50 PST 2010
Woodstox STaX Parser 4.0.5 1.0 Thu Dec 3 11:35:43 EST 2009
jaxws-tools.jar taken from Glassfish JAXWS 2.1.5 1.1 Fri Sep 24 17:55:05 PDT 201
0
Java.net Stax Extensions 1.0 Tue Jun 3 07:12:06 PDT 2008
Java.net xml stream buffer 1.0 Tue Mar 17 05:24:12 PDT 2009
Jakarta ORO 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Enterprise Activation 1.1 Tue Apr 8 09:31:17 PDT 2008
Javax Annotation 1.0 Fri Dec 25 09:02:47 PST 2009
Javax Interceptor 1.0 Tue Mar 20 15:37:16 MDT 2007
Javax Enterprise Beans 3.0 Mon Jun 11 12:21:01 EDT 2007
Java Data Objects 2.0 Mon Jun 11 12:20:56 EDT 2007
Java Enterprise Deployment APIs 1.2 Tue Mar 20 15:37:28 MDT 2007
Java Enterprise Messaging 1.1 Mon Jun 11 12:21:11 EDT 2007
Java Web Services 2.0 Tue Mar 20 15:37:37 MDT 2007
Javax Enterprise Mail 1.1 Mon Jul 6 10:41:09 MDT 2009
Java Enterprise Management APIs 1.0 Tue Mar 20 15:37:49 MDT 2007
Java Persistence Client Capable 1.0 Tue Oct 7 12:18:34 PDT 2008
Java Connector 1.5 Mon Jun 11 12:22:07 EDT 2007
Java Authorization Contract for Containers 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Transaction APIs Client Capable 1.0 Thu Aug 2 12:42:14 EDT 2007
JAXB 2.1 Mon Jun 11 12:22:53 EDT 2007
Java XML Registry 1.0 Wed Feb 6 15:01:03 PST 2008
Java XML Soap Extensions 1.3 Mon Jun 11 12:22:59 EDT 2007
Java Stream XML Extensions 1.1 Mon Jun 11 12:23:05 EDT 2007
JAX-WS APIs 2.1 Mon Jun 11 12:23:16 EDT 2007
Java API for XML-based RPC 1.2 Mon Jun 11 12:23:10 EDT 2007
Monfox Dynamic SNMP Agent 1.1 Fri Mar 19 05:46:27 MDT 2010
Serp bytecode manipulation framework 1.14.3 Fri Jun 11 12:06:08 PDT 2010
WebLogic Apache Classes Client Capable 1.2 Thu Feb 18 22:06:19 PST 2010
WebLogic BeanInfo Caching and Discovery Client Capable 2.4 Sat Oct 25 20:46:29 P
DT 2008
WebLogic Descriptor Client Capable 1.9 Tue Jul 20 16:03:09 EDT 2010
Repackaged ASM-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-commons-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-tree-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-util-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Oracle JFR 1.0 Thu Feb 18 19:06:33 PST 2010
WebLogic Diagnostics Core Interfaces Client Capable 2.5 Thu Jun 3 05:20:41 PDT 2
010
WebLogic Diagnostics Logging Client Capable 1.2 Fri Dec 12 11:37:59 MST 2008
WebLogic Diagnostics Query Module Client Capable 1.2 Tue Oct 27 02:48:36 PDT 200
9
WebLogic Diagnostics Instrumentor Tool 1.7 Tue May 18 03:51:46 PDT 2010
WebLogic Diagnostics Instrumentor Config Tool 1.7 Tue Jun 29 16:41:19 EDT 2010
WebLogic Diagnostics JRockit Flight Recorder Interfaces Client Capable 1.1 Fri O
ct 29 16:32:05 EDT 2010
Diagnostics Notifications Module Client Capable 1.4 Sun Nov 22 16:03:32 PST 2009
BEA Logging Runtime Support Client Capable 1.5 Thu Apr 29 20:43:42 EDT 2010
WebLogic i18n Runtime Support Client Capable 1.8 Fri Sep 10 08:12:34 EDT 2010
WebLogic i18n Build Support Client Capable 1.5 Fri Feb 19 15:03:15 EST 2010
WebLogic I18N tools Client Capable 1.3 Sun Nov 22 16:03:32 PST 2009
WebLogic Management JMX Interfaces 1.4 Thu Aug 12 11:16:22 PDT 2010
WebLogic Security Provider Generation Tool 1.5 Wed Oct 14 16:39:28 MDT 2009
WebLogic Security Provider Generation Tool Client Capable 1.5 Wed Oct 14 16:39:2
8 MDT 2009
WebLogic Messaging Kernel Client Capable 1.8 Mon Aug 23 21:42:11 EDT 2010
WebLogic Resource Pool Client Capable 1.7 Mon Sep 27 12:00:08 EDT 2010
WebLogic Socket Muxer API Client Capable 1.2 Thu Apr 1 21:16:27 EDT 2010
WebLogic RMI Client Capable 1.10 Tue Mar 22 16:56:32 PDT 2011
Common Security WebLogic Server Integration Support 1.0 Fri Oct 8 10:32:52 EDT
2010
Server Lifecycle Interfaces Client Capable 1.4 Fri Feb 19 15:03:15 EST 2010
WebLogic Store Client Capable 1.7 Fri Dec 17 16:52:31 EST 2010
WebLogic STORE GXA Client Capable 1.6 Mon Aug 23 21:16:10 EDT 2010
WebLogic Store Admin Tool Client Capable 1.2 Thu Jan 21 10:24:18 PST 2010
WebLogic JDBC Store Client Capable 1.3 Mon May 17 10:46:33 PDT 2010
WebLogic JTA implementation Client Capable 2.7 Fri Sep 17 12:19:45 PDT 2010
WebLogic Utils 1.9 Thu Mar 3 12:10:10 EST 2011
Agent Utililities 1.1 Tue Feb 16 00:16:03 EST 2010
WebLogic Utility Classloader implementations Client Capable 1.9 Wed Mar 2 14:10:
04 PST 2011
WebLogic Utils for working with Expressions Client Capable 1.4 Tue Sep 29 14:45:
53 EDT 2009
WebLogic Utils for Dynamically Generated Class Wrappers Client Capable 1.4 Fri F
eb 13 14:44:23 MST 2009
WebLogic Timers Client Capable 1.7 Thu Feb 18 13:08:44 EST 2010
WebLogic Work Manager Client Capable 1.10 Thu Feb 17 10:25:54 PST 2011
WebLogic Workarea Client Capable 1.7 Wed Feb 24 17:18:56 PST 2010
WebLogic XML XPath Implementation Client Capable 1.4 Mon Feb 22 15:07:14 PST 201
0
Weblogic Tuxedo Connector Core Client Capable 1.5 Sat Jul 3 19:05:38 EDT 2010
WebLogic Security 1.0 Fri Oct 8 10:32:52 EDT 2010
Weblogic Server Java Authentication Helper Classes Client Capable 1.1 Mon Jul 5
20:42:35 EDT 2010
Weblogic Server Message Digest Utilities Client Capable 1.0 Thu Aug 2 12:51:30 E
DT 2007
Weblogic Server Authenticated Subject Client Capable 1.1 Thu Oct 28 05:46:37 PDT
2010
Weblogic Server Authenticated Subject Client Capable 1.5 Thu Sep 9 10:23:21 MDT
2010
PrintingSecurityManager - PSM 1.1 Tue Feb 16 05:30:08 PST 2010
WebLogic security ssl classes 1.0 Tue Jun 15 17:39:53 EDT 2010
WebLogic Nodemanager Plugin Client Capable 1.3 Tue Nov 18 18:23:10 EST 2008
nodemanager module for managed processes 1.0 Thu Apr 8 15:14:38 PDT 2010
WebLogic JMS Pool Client Capable 1.8 Thu Mar 3 14:11:40 PST 2011
Contains compiled schema type from WLS 9.0 for WLP compatibility 1.3 Wed Feb 24
19:15:33 EST 2010
WebLogic Http Pub/Sub Module Client Capable 1.6 Mon Jul 12 02:31:07 EDT 2010
Class Redefinition Project 1.5 Mon May 10 19:48:21 EDT 2010
Class Redefinition Project Client Capable 1.5 Mon Apr 5 17:00:52 PDT 2010
Class Redefinition Project 1.5 Binding Bundle
Commonj SDO 1.0 Wed Sep 24 19:11:23 PDT 2008
WebLogic Coherence Descriptor 1.1 Wed May 5 15:17:47 EDT 2010
WebLogic Coherence Descriptor 1.1 Binding Bundle
This module contains all message catalogs 1.1 Fri Dec 17 08:04:35 PST 2010
WebLogic WebService Public API's 1.1 Tue Sep 21 22:15:05 EDT 2010
WebLogic EclipseLink Integration 1.0 Thu Feb 25 14:56:43 PST 2010
WebLogic SCA Client 1.0 Thu Feb 25 00:27:10 EST 2010
WebLogic RAC Module UCP Client Capable 1.0 Mon Sep 13 09:03:00 PDT 2010
BEA Patches of apache ant Client Capable 1.2 Wed Jan 13 08:48:17 PST 2010
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server Datatier 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
WebLogic SIPServer Extension API 10.3.4.0 at 709997 built on 2010/09/27
WebLogic SIPServer Extension API 10.3.4 at 709997 built on 2010/09/27
WebLogic SIPServer CallState 10.3.4 at 709997 built on 2010/09/27
Oracle WebLogic Communications SCTP 10.3.1 at 688160 built on 2009/03/11
WebLogic WebService Databinding Plugins 1.3 Wed Dec 1 17:41:28 EST 2010
WebLogic WebService Databinding 1.3 Tue Oct 18 16:38:56 EDT 2011
WebLogic SIP Activator 10.3.4 at 710163 built on 2010/09/30
>
<Aug 30, 2012 1:14:08 AM IST> <Error> <WLSS.Engine> <BEA-330075> <There are no s
ip nor diameter channels targeted to server "soa_managed_server01">
<Aug 30, 2012 1:14:08 AM IST> <Error> <WLSS.Engine> <BEA-330049> <Failed to star
t the sip service, shutting down>
C:\Oracle\Middleware\user_projects\domains\sudheers_domain\bin
Thanks in advance,
SudheerHi Vlad, Kalyan
Thanks for the response. Actually i am not planning to configure weblogic SIP... as it may need little insight. I just created domain including everything.
Now i have created a new domain with basic functionality with default configuration. Now everything is working fine. I can see the Admin console as well.
But i have stuck up in running the EM console. Below is the CMD prompt trace.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\suchalam>cd C:\Oracle\Middleware\user_projects\domains\sudheer_domain\b
in
C:\Oracle\Middleware\user_projects\domains\sudheer_domain\bin>startManagedWebLog
ic.cmd soa_server1
** Setting up SOA specific environment for win...
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1
\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\nat
ive\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\O
RGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bi
n;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\serv
er\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System
32\WindowsPowerShell\v1.0\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program File
s (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (
x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\O
racle\Middleware\jdeveloper\ant\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Oracle\Mid
dleware\jdk160_24\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920
_8;C:\Oracle\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
USER_MEM_ARGS=-Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=512m
JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="C:\Oracle\Middleware\wls
erver_10.3\server\lib\cacerts" -Xverify:none
** End SOA Specific environment setup for win.
** SOA specific environment is already set. Skipping ...
JAVA Memory arguments: -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
:\Oracle\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\
Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\patch_wls1035\profil
es\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jd
ev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDD
LE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp
.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\mo
dules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.
3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.j
ar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~
1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modul
es\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_SOA1\so
a\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Or
acle\Middleware\Oracle_SOA1\communications\modules\usermessaging-config_11.1.1.j
ar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MID
DLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Mid
dleware\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\USER_P~1\domains\
SUDHEE~2\config\soa-infra;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\fabric-ur
l-handler_11.1.1.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6
.5.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\ora
cle.soa.fabric.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabri
c_11.1.1\fabric-runtime-ext-wls.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules
\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\Oracle_SO
A1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\MIDDLE~1\ORACL
E~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby
\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;C:\Oracle
\Middleware\jdeveloper\ant\lib;C:\Oracle\Middleware\jdk160_24\lib;
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1
\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\nat
ive\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\O
RGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bi
n;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\serv
er\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System
32\WindowsPowerShell\v1.0\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program File
s (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (
x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\O
racle\Middleware\jdeveloper\ant\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Oracle\Mid
dleware\jdk160_24\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920
_8;C:\Oracle\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\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_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms512m -Xmx512m -XX:PermSize=12
8m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Or
acle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.security.SSL.trus
tedCAKeyStore="C:\Oracle\Middleware\wlserver_10.3\server\lib\cacerts" -Xverify:
none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MID
DLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -D
common.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.ap
ache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.ho
me=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2 -Djrockit.optfile=C:\Oracle\MIDD
LE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.conf
ig.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\config\FMWCON~1\servers\soa_
server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\
config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\
SUDHEE~2\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P
~1\domains\SUDHEE~2\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=
C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\config\fmwconfig\jps-config.xml -Do
racle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\servers\soa_
server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirec
tory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~
1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle
.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.
common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnable
d=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org
.apache.xmlbeans... -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dso
a.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MID
DLE~1\USER_P~1\domains\SUDHEE~2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -D
tangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soa
p.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transact
ion.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.n
et.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.or
acle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.orac
le.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\
Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=ht
tp://SUCHALAM-WS:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.lo
gErrorsToConsole=false -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\prof
iles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profile
s\default\sysext_manifest_classpath weblogic.Server
<Sep 2, 2012 6:51:28 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ J
CE Provider self-integrity check for better startup performance. To enable this
check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 2, 2012 6:51:29 PM IST> <Info> <Security> <BEA-090906> <Changing the defaul
t Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable
this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 2, 2012 6:51:30 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsyste
ms Inc.>
<Sep 2, 2012 6:51:32 PM IST> <Info> <Security> <BEA-090065> <Getting boot identi
ty from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Sep 2, 2012 6:51:42 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Sep 2, 2012 6:51:45 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Sep 2, 2012 6:51:45 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing sel
f-tuning thread pool>
<Sep 2, 2012 6:51:46 PM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\Oracle\Middleware\user_projects\domains\sudheer_domain\servers\soa_s
erver1\logs\soa_server1.log is opened. All server side log events will be writte
n to this file.>
<Sep 2, 2012 6:51:59 PM IST> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm myrealm.>
<Sep 2, 2012 6:53:56 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STANDBY>
<Sep 2, 2012 6:53:56 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Sep 2, 2012 7:19:07 PM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.m
odel, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, referenced
from: C:\Oracle\Middleware\user_projects\domains\sudheer_domain\servers\soa_ser
ver1\tmp\_WL_user\usermessagingserver\y73z7z]. Make sure the referenced optional
package has been deployed as a library.>
<Sep 2, 2012 7:19:12 PM IST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRec
eiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.jar
), the value for the activation config property 'connectionFactoryJNDIName' will
be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactor
y';>
It kept on waiting here for so long. Can u please suggest me what is missing here.
Thanks in advance,
Sudheer -
Starting WLS 10.3.5 Managed Server in MSI mode
(1) The first time you start the managed server in MSI, should the Admin Server be in Running Mode?
Or
(2) The Managed Server can be started in MSI mode (first time) with out having Admin Server in RUNNING MODE.
Which is true?
I think (1) is correct as the managed server directory wont be available under <DOMAIN_HOME>/Servers directory until you start the Managed Server. So only once you start the Managed Server, then only you can copy the config folder under Managed Server to start it in MSI mode (Having ADMIIN SERVER in SHUTDOWN state).
Is that correct?
So you can never ever start the Managed Server in MSI mode for the first time (with out having Admin Server in RUNNING MODE) after you create the managed server.
Is that correct?
Edited by: user734247 on Apr 18, 2012 2:58 PMYour understanding is right.
The first time you are trying to start a managed server, you need admin server in RUNNING state.
From the next time onwards you can start managed server in MSI mode.
Although, as a workaround you can probably create certain files and directories to try and start managed server in MSI mode the first time itself:
1. Ensure that the entire domain directory is present in the machine where managed server is started.
2. Create directory <DOMAIN_HOME>/Servers/<ManagedServerName>/security
3. Create boot.properties file in <DOMAIN_HOME>/Servers/<ManagedServerName>/security/boot.properties with username and password
4. Create config-msi.xml copying from the config.xml in config directory
This list is not exclusive, it might need some more additional files.
You will have to create additional files like startServer.properties etc if we use node manager to start a managed server in MSI mode.
ORACLE strongly recommends to start the managed server through admin server the first time.
Arun -
WC_Spaces Managed server not showing up in AdminServer
I am trying to install the webCenter spaces managed server. I installed the schema to database and extended my existing domain with the spaces product and I have all the products that you have to install with it, but when I start the admin server the spaces managed server is not showing up. I created a new domain and put space on that one and when i start the new domains admin server is see the WC_Spaces managed server. Why is it not showing up on my existing domain?
Hi,
By default any managed server will not be up we need to start them by help of Nodemanager or by standalone using script called startManagedWebLogic.sh or cmd file.
when you try to start Managed server from Admin Console then try to enable to Machine for the Managed server where Machine will configure Nodemanager details. Start Nodemanager then in Monitoring of Nodemanager under Machine will show Reachable.
Then we are able to start Managed server through Admin Console.
If you dont want to start through Nodemanager then use following command.
Under Domain_Home / bin / folder
you will find startManagedWebLogic.sh file in Unix and .cmd file in Windows.
Now you following command ./startManagedWebLogic.sh t3://<AdminServer URL >:<Admin Port>
This will help to start Managed server.
Note: Make sure that you have security folder under managed server and provide boot.properties with username and password so that it can encrypted once it get started or else every time we need to provide username and password at startup.
Regards,
Kal -
Problem while starting managed server using nodemanager
Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig> -
Question:managed server status display unknown ??
platform: AS5 weblogic8.16 cluter
when managed server startup,status ok,but after some days,managed server status is unknown or shutdown in console web
I check process "ps -ef|grep java" managed server process exit
and application on managed server is ok
this is log in domain.log
####<2009-9-9 <Warning> <Management> <web3> <myserver> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <BEA-141138> <Managed Server web03 is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting.>
after restart managed server ,status running
so why managed server status display unknown/shutdown after some days?? how can i solve this problem??Status unknown means that node manager can't establish contact with the mgd server. If your server is dropping out of the cluster, that would result in Unknown.
Your server could be dropping out of the cluster for many, many reasons. If it is always the same server dropping out, that points to a particular node in your cluster. -
OIM 11gR2 : Problem while starting managed server
Hello Experts,
I ran config.sh in order to extend my schema to include APM (Authorization Policy Manager) in OIM 11gR2.
After that i took a restart of the servers. When i am trying to start the managed servers they're not starting in the RUNNING mode. Instead they're starting in the ADMIN mode.
The logs are showing the following error :
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Kindly help me out.1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig> -
Start Managed Server from Admine clonsole FAILED_NOT_RESTARTABLE
when trying to start the managed server Managed-Server-01 from the WLS Admin Console the managed server status becomes <FAILED_NOT_RESTARTABLE> and not coming up:
Managed servers logs:
/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-01/logs:
3/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false>
<Sep 13, 2011 6:15:46 PM> <Debug> <NodeManager> <Environment: SERVER_NAME=Managed-Server-03>
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server-03.out">
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: expr: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: test: argument expected
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <Waiting for the process to die: 1226>
<Sep 13, 2011 6:15:47 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
--=--
Node Manager log during Managed-Server-01 start from WLS Admin Console shows:
15:46 PM> <Info> <eShop> <Managed-Server-03> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <eShop> <Managed-Server-03> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server
-03.out">
<Sep 13, 2011 6:15:47 PM> <Info> <eShop> <Managed-Server-03> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Warning> <Exception while starting server 'Managed-Server-03': java.io.IOException: Server failed to start up. See server output log for more details.
>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:6
Note:
The installation of WLS done using Root.
We can start/stop MS using conventional ways.
Cheers,although i am not an expert,
but i am very confident that any WLS you install,
it can be configured like i tried it,
First Environment-----Machine
Add a machine by giving a name
Second Environment------Server
Add a server giving a sever name
Third Environment----machine
Add the server to the machine from the tab server
Fourth Environment-------server
Add A a SSL Port to the Sever and save
Click Start Server and every thing goes well
Thanks
Edited by: kashif, pakistan on Sep 14, 2011 4:09 AM -
Error while starting Managed server in wls
I am using WebLogic Server Version: 10.3.4.0. I have created one managed server thru admin console. I am starting managed server using startManagedWebLogic.cmd batch file. Chnages I made in this cmd file is added managed server name and wls userid/password.
When execute this, I get below error:
Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/Server
Caused by: java.lang.ClassNotFoundException: weblogic.Server
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: weblogic.Server. Program will exit.
The contents of the startManagedWebLogic.cmd is as below:
@ECHO OFF
@REM WARNING: This file is created by the Configuration Wizard.
@REM Any changes to this script may be lost when adding extensions to this configuration.
SETLOCAL
@REM --- Start Functions ---
GOTO :ENDFUNCTIONS
:usage
echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
echo them in command line:
echo Usage: %1 SERVER_NAME {ADMIN_URL}
echo for example:
echo %1 managedserver1 http://localhost:7001
GOTO :EOF
:ENDFUNCTIONS
@REM --- End Functions ---
@REM *************************************************************************
@REM This script is used to start a managed WebLogic Server for the domain in
@REM the current working directory. This script can either read in the SERVER_NAME and
@REM ADMIN_URL as positional parameters or will read them from environment variables that are
@REM set before calling this script. If SERVER_NAME is not sent as a parameter or exists with a value
@REM as an environment variable the script will EXIT. If the ADMIN_URL value cannot be determined
@REM by reading a parameter or from the environment a default value will be used.
@REM
@REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
@REM (http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm)
@REM *************************************************************************
@REM Set SERVER_NAME to the name of the server you wish to start up.
Set SERVER_NAME=*ManagedServer1*
set DOMAIN_NAME=mydomain
set ADMIN_URL=http://localhost:7001
@REM Set WLS_USER equal to your system username and WLS_PW equal
@REM to your system password for no username and password prompt
@REM during server startup. Both are required to bypass the startup
@REM prompt.
set WLS_USER=*weblogic*
set WLS_PW=*weblogic1*
@REM Set JAVA_OPTIONS to the java flags you want to pass to the vm. i.e.:
@REM set JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value
set JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="d:\Perforce\weblogic1\src_16020jr\bea\wlserver_10.3\server\..\server\lib\cacerts" %JAVA_OPTIONS%
@REM Set JAVA_VM to the java virtual machine you want to run. For instance:
@REM set JAVA_VM=-server
set JAVA_VM=
@REM Set SERVER_NAME and ADMIN_URL, they must by specified before starting
@REM a managed server, detailed information can be found at
@REM http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm
if "%1"=="" (
if "%SERVER_NAME%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set SERVER_NAME=%1
shift
if "%1"=="" (
if "%ADMIN_URL%"=="" (
CALL :usage %0
GOTO :EOF
) else (
set ADMIN_URL=%1
shift
@REM Export the admin_url whether the user specified it OR it was sent on the command-line
set ADMIN_URL=%ADMIN_URL%
set SERVER_NAME=%SERVER_NAME%
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
if "%1"=="" (
@REM Call Weblogic Server with our default params since the user did not specify any other ones
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" nodebug noderby noiterativedev notestconsole noLogErrorsToConsole
) else (
@REM Call Weblogic Server with the params the user sent in INSTEAD of the defaults
call "%DOMAIN_HOME%\bin\startWebLogic.cmd" %1 %2 %3 %4 %5 %6 %7 %8 %9
ENDLOCAL
Any help is really appreciated.I could see calling to setDomainEnv.cmd script:
*@REM Call setDomainEnv here.*
set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
set SAVE_CLASSPATH=%CLASSPATH%
But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
This might be the issue? Or anything else? -
WLS 7.0 Active Directory authenticator - problems starting managed server (Solaris 8)
Has anyone managed to setup a WLS 7.0 Active Directory authenticator and booted
a managed server using the node manager? I can boot the server without the AD
authenticator and I can also boot the server using a script and successfully authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT. This
configuration works fine with weblogic running on W2K, but not on Solaris (it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01> <main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01> <main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException: RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine> <server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException: Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)Solved the problem. The 'domain root' directory specified in the remote start configuration,
must contain a copy of the file 'SerializedSystemIni.dat' that was created along
with the domain, in order to boot when an AD authenticator is configured. If an
AD authenticator is not configured, no file is required. This was not a platform
specific issue; on Win2K I had configured the 'domain root' remote start parameter
to point to an existing domain root and not a new directory.
"Andrew Walker" <[email protected]> wrote:
>
Has anyone managed to setup a WLS 7.0 Active Directory authenticator
and booted
a managed server using the node manager? I can boot the server without
the AD
authenticator and I can also boot the server using a script and successfully
authenticate
through AD. My AD control flag is set to OPTIONAL and I have also setup
a default
authenticator to boot weblogic - the control flag here is set to SUFFICIENT.
This
configuration works fine with weblogic running on W2K, but not on Solaris
(it
looks like the control flag is being ignored). Errors as follows
####<Oct 1, 2002 1:59:08 PM BST> <Info> <Logging> <mymachine> <server01>
<main>
<kernel identity> <> <000000> <FileLo
gger Opened at /opt/app/live/appserver/domains/test/NodeManager/server01/server01.log>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000415> <System
has file descriptor limits of - soft: 1,024, hard: 1,024>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000416> <Using e
ffective file descriptor limit of: 1,024 open sockets/files.>
####<Oct 1, 2002 1:59:09 PM BST> <Info> <socket> <mymachine> <server01>
<main>
<kernel identity> <> <000418> <Allocat
ing: 3 POSIX reader threads>
####<Oct 1, 2002 1:59:19 PM BST> <Critical> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <0003
64> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException:
Problem instantiating
Authentication Providerjavax.management.RuntimeOperationsException:
RuntimeException
thrown by the getAttribute method of the Dynam
icMBean for the attribute Credential>
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
####<Oct 1, 2002 1:59:19 PM BST> <Emergency> <WebLogicServer> <mymachine>
<server01>
<main> <kernel identity> <> <000
342> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.security.service.SecurityServiceRuntimeException:
Problem
instantiating Authentication Providerjavax.management.
RuntimeOperationsException: RuntimeException thrown by the getAttribute
method
of the DynamicMBean for the attribute Credential
weblogic.security.service.SecurityServiceRuntimeException: Problem instantiating
Authentication Providerjavax.management.RuntimeOper
ationsException: RuntimeException thrown by the getAttribute method of
the DynamicMBean
for the attribute Credential
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:186)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:236)
at weblogic.security.service.SecurityServiceManager.doATN(SecurityServiceManager.java:1506)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1308)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1247)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1364)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1107)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31) -
Query regarding the Node manager configuration(WLS and OAM Managed server)
Query regarding the Node manager configuration(WLS and OAM Managed server):
1) In the nodemanager.properties I have added the ListenAddress:myMachineName and ListenPort: 5556
My setup : One physical Linux machine(myMachineName) has : WLS admin server, managed server(OAM 11G) and nodemanager.No clustered environment.
2) nodemanager.log has the following exception when I start the oam_server1 using EM(Enterprise Manager11g):
Mar 23 2012 1:39:55 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:202)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:125)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
Default port on which node manager listen for requests is localhost:5556.I have changed it to point to my machine. The port should be of WLS admin server or it should be the managed server port?
3) I have started the NodeManager using the startNodeManager.sh script.
4) The admin server port is 7001 and the oam managed server port is 14100.
Any inputs on what might be wrong in the setup will be helpful.Thanks !By using netstat -anp|grep 5556 you can check which process on your machine is using the 5556 port.
-
WLS Admin and managed server startup issue
Hi ,
In one of WLS Domain both the Admin Server and Managed Server startup is just hanging at the below mentioned point :
<Security> <BEA-090082> <Security initializing using security realm myrealm.>
After this there are no error messages or logs being generated and the server start up is not proceeding .
Only message shown a while after this is :
Warning : domain runtime mbean server has not been found after trying for 600 seconds
Please provide some inputs on how to troubleshoot this issue .
Checked the AdminServer.log and there are no errors reported there as well .
Some more data from AdminServer.log :
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845368> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448845632> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846193> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846208> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm myrealm.>
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1336448846433> <BEA-090082> <Security initializing using security realm myrealm.>
Thanks
Srinath
Edited by: Srinath Menon on May 8, 2012 9:36 AMHi Ashish ,
Thanks for the inputs.
Tried the same steps as mentioned but the issue still remains like that .
Posting the thread dump collected for AdminServer:
===== FULL THREAD DUMP ===============
Tue May 8 10:04:58 2012
Oracle JRockit(R) R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32
"Main Thread" id=1 idx=0x4 tid=9341 prio=5 alive, waiting, native_blocked
-- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x9f81d3c0[fat lock]
at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:459)
at weblogic/t3/srvr/ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
^-- Holding lock: java/lang/Class@0x9fa95598[biased lock]
at weblogic/t3/srvr/T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:566)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:467)
at weblogic/Server.main(Server.java:71)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Signal Handler)" id=2 idx=0x8 tid=9342 prio=5 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at sigiSignalHandlerThread+135(signalhandler.c:131)@0xb7ec2fd8
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(OC Main Thread)" id=3 idx=0xc tid=9343 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at ocMainThread+663(gcthreads.c:581)@0xb7d8a098
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(GC Worker Thread 1)" id=? idx=0x10 tid=9344 prio=5 alive, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(GC Worker Thread 2)" id=? idx=0x14 tid=9345 prio=5 alive, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventWaitNoTransition+32(event.c:62)@0xb7d6bc31
at mmGCWorkerThread+134(gcthreads.c:797)@0xb7d89d67
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(Code Generation Thread 1)" id=4 idx=0x18 tid=9348 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(Code Optimization Thread 1)" id=5 idx=0x1c tid=9349 prio=5 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at cg_thread+380(compilerqueue.c:203)@0xb7d4be5d
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"(VM Periodic Task)" id=6 idx=0x20 tid=9350 prio=10 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at block_for_safepoint+106(safepoint.c:34)@0xb7ebad5b
at eventTimedWait+239(event.c:83)@0xb7d6bd30
at periodic_task_thread+627(periodictask.c:367)@0xb7e90dd4
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"Finalizer" id=7 idx=0x24 tid=9351 prio=8 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeWait+71(nativelock.c:721)@0xb7e79008
at RJNI_jrockit_memory_Finalizer_waitForFinalizees+211(finalhandles.c:1007)@0xb7d751f4
at jrockit/memory/Finalizer.waitForFinalizees(J[Ljava/lang/Object;)I(Native Method)
at jrockit/memory/Finalizer.access$700(Finalizer.java:12)
at jrockit/memory/Finalizer$4.run(Finalizer.java:189)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Reference Handler" id=8 idx=0x28 tid=9352 prio=10 alive, native_waiting, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+894(nativelock.c:614)@0xb7e78caf
at nativeUnlockAndWait+71(nativelock.c:686)@0xb7e790a8
at RJNI_java_lang_ref_Reference_waitForActivatedQueue+38(semiref.c:342)@0xb7ebd9b7
at java/lang/ref/Reference.waitForActivatedQueue(J)Ljava/lang/ref/Reference;(Native Method)
at java/lang/ref/Reference.access$100(Reference.java:11)
at java/lang/ref/Reference$ReferenceHandler.run(Reference.java:82)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"(Sensor Event Thread)" id=9 idx=0x2c tid=9353 prio=5 alive, native_blocked, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at eventTimedWaitNoTransition+62(event.c:72)@0xb7d6bb3f
at eventTimedWait+138(event.c:56)@0xb7d6bccb
at eventWait+32(event.c:50)@0xb7d6bd81
at sensor_event_loop+37(sensor.c:68)@0xb7ebfda6
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"VM JFR Buffer Thread" id=10 idx=0x30 tid=9354 prio=5 alive, in native, daemon
at <unknown>(???.c)@0xb7fe9410
at bufferthread+2135(vmjfr.c:1008)@0xb71744b8
at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"Timer-0" id=13 idx=0x34 tid=9358 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0x9f9fc350[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0x9f9fc350[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"Timer-1" id=14 idx=0x38 tid=9363 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0xa20ee240[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/util/TimerThread.mainLoop(Timer.java:509)
^-- Lock released while waiting: java/util/TaskQueue@0xa20ee240[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=15 idx=0x3c tid=9364 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at netscape/ldap/LDAPMessageQueue.waitForMessage(LDAPMessageQueue.java:200)
^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[recursive]
at netscape/ldap/LDAPMessageQueue.waitFirstMessage(LDAPMessageQueue.java:101)
^-- Lock released while waiting: netscape/ldap/LDAPResponseListener@0x9724f0c8[fat lock]
at netscape/ldap/LDAPConnection.sendRequest(LDAPConnection.java:1796)
^-- Holding lock: netscape/ldap/LDAPConnection@0x9721f310[biased lock]
at netscape/ldap/LDAPConnection.simpleBind(LDAPConnection.java:1763)
at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1264)
at netscape/ldap/LDAPConnection.authenticate(LDAPConnection.java:1273)
at netscape/ldap/LDAPConnection.bind(LDAPConnection.java:1562)
at weblogic/security/providers/authentication/LDAPAtnDelegate$LDAPFactory.newInstance(LDAPAtnDelegate.java:4134)
at weblogic/security/utils/Pool.newInstance(Pool.java:37)
at weblogic/security/utils/Pool.getInstance(Pool.java:33)
at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3478)
at weblogic/security/providers/authentication/LDAPAtnDelegate.getConnection(LDAPAtnDelegate.java:3470)
at weblogic/security/providers/authentication/LDAPAtnDelegate.authenticate(LDAPAtnDelegate.java:3522)
at weblogic/security/providers/authentication/LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:227)
at com/bea/common/security/internal/service/LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
at com/bea/common/security/internal/service/LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at javax/security/auth/login/LoginContext.invoke(LoginContext.java:769)
at javax/security/auth/login/LoginContext.access$000(LoginContext.java:186)
at javax/security/auth/login/LoginContext$4.run(LoginContext.java:683)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:254)
at jrockit/vm/AccessController.doPrivileged(AccessController.java:268)
at javax/security/auth/login/LoginContext.invokePriv(LoginContext.java:680)
at javax/security/auth/login/LoginContext.login(LoginContext.java:579)
at com/bea/common/security/internal/service/JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy28.login(Ljava/lang/String;Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
at weblogic/security/service/internal/WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
at com/bea/common/security/internal/service/JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
at jrockit/vm/Reflect.invokeMethod(Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Native Method)
at sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java/lang/reflect/Method.invoke(Method.java:597)
at com/bea/common/security/internal/utils/Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy46.authenticate(Ljavax/security/auth/callback/CallbackHandler;Lweblogic/security/service/ContextHandler;)Lcom/bea/common/security/service/Identity;(Unknown Source)
at weblogic/security/service/WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
at weblogic/security/service/PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:348)
at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
at weblogic/security/service/CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic/security/service/SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic/security/SecurityService.start(SecurityService.java:141)
at weblogic/t3/srvr/SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:207)
at weblogic/work/ExecuteThread.run(ExecuteThread.java:176)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"JFR request timer" id=16 idx=0x40 tid=9365 prio=5 alive, waiting, native_blocked, daemon
-- Waiting for notification on: java/util/TaskQueue@0xa2049280[fat lock]
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at syncWaitForSignal+157(synchronization.c:85)@0xb7ee7dbe
at syncWaitForJavaSignal+53(synchronization.c:93)@0xb7ee7ea6
at RJNI_jrockit_vm_Threads_waitForNotifySignal+53(rnithreads.c:72)@0xb7eb78a6
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:485)
at java/util/TimerThread.mainLoop(Timer.java:483)
^-- Lock released while waiting: java/util/TaskQueue@0xa2049280[fat lock]
at java/util/TimerThread.run(Timer.java:462)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"weblogic.time.TimeEventGenerator" id=18 idx=0x44 tid=9366 prio=9 alive, waiting, native_blocked, daemon
-- Waiting for notification on: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/time/common/internal/TimeTable.snooze(TimeTable.java:286)
^-- Lock released while waiting: weblogic/time/common/internal/TimeTable@0xa2089c70[fat lock]
at weblogic/time/common/internal/TimeEventGenerator.run(TimeEventGenerator.java:117)
at java/lang/Thread.run(Thread.java:662)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
"JMAPI event thread" id=19 idx=0x48 tid=9367 prio=5 alive, in native, daemon
at <unknown>(???.c)@0xb7fe9410
at eventTimedWaitNoTransitionImpl+79(event.c:90)@0xb7d6bae0
at syncWaitForSignalNoTransition+81(synchronization.c:28)@0xb7ee7c62
at innerNativeDoWait+526(nativelock.c:614)@0xb7e78b3f
at nlMonitorWaitInner+79(nativelock.c:1112)@0xb7e78df0
at nlMonitorWaitNoTransition+38(nativelock.c:1132)@0xb7e78e47
at nativeRawMonitorWait+78(rawmonitor.c:161)@0xb7ea8caf
at jvmti_RawMonitorWait+111(jvmtirawmonitors.c:95)@0xb7e1b420
at threadProc+291(jmapi.c:305)@0x90452bd4
at run_agent_thread+128(jvmtithreads.c:524)@0xb7e1f361
at thread_stub+146(lifecycle.c:808)@0xb7e2c333
at start_thread+225(:0)@0x515832
at __clone+93(:0)@0x46ae0e
"weblogic.timers.TimerThread" id=20 idx=0x4c tid=9368 prio=9 alive, waiting, native_blocked, daemon
-- Waiting for notification on: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
at <unknown>(???.c)@0xb7fe9410
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/timers/internal/TimerThread$Thread.run(TimerThread.java:262)
^-- Lock released while waiting: weblogic/timers/internal/TimerThread@0xa203dbf0[fat lock]
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace -
WLS 10.3: Node Manager error while starting managed server
Hi,
I get the following error when trying to start a managed server using Node Manager from the Admin console on WLS 10.3
Error:
<27/11/2009 3:21:34 PM> <Info> <NodeManager> <Server output log file is "/opt/osb/osb_env/domains/DevVVDomain/servers/dev_osb_server1/logs/dev_osb_server1.out">
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : grepuname: : not foundnot found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: : not foundgrep
: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: grep: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: uname: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: expr: not found
/opt/osb/osb_env/domains/DevVVDomain/bin/startWebLogic.sh: test: argument expected
<27/11/2009 3:21:35 PM> <Debug> <NodeManager> <Waiting for the process to die: null>
<27/11/2009 3:21:35 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<27/11/2009 3:21:35 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>My nodemanager.properties file looks like this:
DomainsFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
javaHome=/opt/osb/osb1031/jrockitR27.6.5-32
AuthenticationEnabled=true
NodeManagerHome=/opt/osb/osb1031/wlserver_10.3/common/nodemanager
JavaHome=/opt/osb/osb1031/jrockitR27.6.5-32/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=mcsdev3
NativeVersionEnabled=false
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=true
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=/opt/osb/osb1031/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
StopScriptName=stopWeblogic.shPlease let me know what additional configuration is required to get the server started properly
Regards
VikasFound a workaround:
Manually, add PATH (and probably the other environment variables also) to
${WLS_HOME}/common/bin/commEnv.sh. -
Impossible to start UCM managed server with the WLS console
Hi,
I cannot start the UCM managed server with the WLS console. The node manager is running by startNodeManager.cmd. The admin server by startWebLogic.cmd.
When I start the UCM server with the console WLS (Environment, Servers, Control tab and Start on the checked server), it seems to be running (the state is RUNNING) but when I open the url on the the web server UCM there is a 404 error
In the log, there are many java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup, oracle.security.jps.wls.JpsWlsStartupClass, oracle.core.ojdl.weblogic.ODLConfiguration, oracle.jrf.AppContextStartup, oracle.as.jmx.framework.wls.spi.StartupListener, oracle.ias.cache.Startup, oracle.dms.wls.DMSStartup ...
If I start UCM directly by startManagedWebLogic.cmd and not with the WLS console, everything is OK. No error in the log and UCM server is working well
Any idea ?
Thanks
HuguesGreat!
I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
Is there a way/script to start the node manager automatically?
Regards, -
Managed Server Monitoring tools for WLS 8.1 on linux
Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciatedOur organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciated
Maybe you are looking for
-
How to find serial number on software already installed
how do i locate serial number on cs6 installed on pc
-
Less than symbol, shows as XML value < ; in translate table drop down
We are upgrading from 8.19 to 8.49. We have set up a field that has translate values of <, <=, >, >=, <> and =. We use this field as a drop down on a page and they should display as shown. For some reason, when you click the drop down, any of the cho
-
Gift certificate sale GL postings
Hi Sap Gurus I would like to know how to acheive Gift certificate sale. we are setting up gift certficates as NLAG materials. And we will sell them to customers with other products. But the difference between gift certificates and the other products
-
Data Migration Assistant Errors
Trying to upgrade from CallManager 4.3 to 7.1 using the DMA software. The export is successful but the validation is not. I receive the attached errors and can't find what they mean anywhere. Thanks in advance.
-
hello all. i have had a bit of a problem i got a MSI 990FXA-GD80 AMD mobo i bought it here http://www.aria.co.uk/SuperSpecials/Other+products/MSI+990FXA-GD80+AMD+990FX+%28Socket+AM3%2B%29+DDR3+PCI-Express+ATX+Motherboard+?productId=44727&rqcType=c#rq