Failure to start SOA managed server after SOA 11.1.1.5 install

Installed SOA Suite 11.1.1.5, setup jdk_16025x64, XE, RCU, WLS, SOA (Disks1-5), setup WLS DOMAIN, etc. - no problems. Startup the Admin Server - no problems - on a Win7x64 box. When startup the soa_server1 managed server seems to start up okay then shortly into t he startup process get the following error message:
+...+
+<Mar 29, 2012 7:47:35 AM EDT> <Error> <oracle.mds> <BEA-000000> <+
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "soa-infra-store" is invalid.
ORA-04063: package body "DEV_MDS.MDS_INTERNAL_SHREDDED" has errors
ORA-06508: PL/SQL: could not find program unit being called: "DEV_MDS.MDS_INTERNAL_SHREDDED"
ORA-06512: at line 1
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:710)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:198)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
+... <many many more error lines> ...+
Any ideas as to what the iissue is?
THANKS for the help - Casey

Hi Casey
The issue is clearly due to some MDS Schema, Packages NOT getting compiled and hence not able to connect to that datasource and hence server cannot start.
Please see this post for the root cause and the fix:
Re: SOA infra is falied
Please note down password you gave for your rcu schemas (soa_infra, mds etc). Run RCU. Drop the existing schemas. Now run the 2 commands that I gave in above post. Start Rcu again. Select Create and follow and use the same password. IF you use same password, there is no need to make changes to data sources related jdbc.xml files.
Worst case, if you can access this MDS Schema, try to compile these packages like from toad, sql developer or some sort of client. I would not recommend this. I prefer above fix as permanent and clean. But if you want, you can try recompiling also.
Thanks
Ravi Jegga

Similar Messages

SOA managed server and SOA infra not starting

Hi
I have my database and listener up and running. I can also successfully start SOA Administration server.
But I am unable to start SOA managed server. I can see SOA managed server getting started with WARNING and SOA infra always fails to start.
I tried using both from command line as well as from NodeManager but without any luck. As a result I am unable to proceed with Deployment as soa_server1 does not appear in Step 4 in Jdeveloper deployment GUI dialog. I would also like to ask from the Gurus:
How can I start soa-infra alone as I cannot see any command from the command line to individually start soa-infra ?
Here is my part of output from soa_server1. The exception errors keep logging in loop and the file is growing. I had to terminate the process:
<Jun 3, 2010 10:40:03 PM> <INFO> <NodeManager> <Server output log file is '/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.out'>
** Setting up SOA specific environment...
EXTRA_JAVA_PROPERTIES= -da:org.apache.xmlbeans...
LD_LIBRARY_PATH=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386/jrockit:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/../lib/i386:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/thirdparty/edifecs/XEngine/bin
USER_MEM_ARGS=-Xms512m -Xmx512m
** End SOA specific environment setup
** SOA specific environment is already set, skipping...
JAVA Memory arguments: -Xms512m -Xmx512m
WLS Start Mode=Development
CLASSPATH=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/user-patch.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/soa-startup.jar::/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.xdk_11.1.0/xsu12.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.1.0.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/db2jcc4.jar:/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/soa-infra:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/fabric-url-handler_11.1.1.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/quartz-all-1.6.5.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle1/Oracle/Middleware
PATH=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/u02/app/oracle/product/11.1.0/db_1/bin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/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_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
Starting WLS with line:
/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da -Dplatform.home=/home/oracle1/Oracle/Middleware/wlserver_10.3 -Dwls.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dcommon.components.home=/home/oracle1/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig -Doracle.server.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/servers/soa_server1 -Doracle.security.jps.config=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/carml -Digf.arisidstack.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dtangosol.coherence.clusteraddress=227.7.7.8 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dcom.sun.management.jmxremote -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/home/oracle1/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dbam.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dums.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.2.103:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
[JRockit] Local management server started.
<Jun 3, 2010 10:40:15 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
<Jun 3, 2010 10:40:21 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
<Jun 3, 2010 10:40:35 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 3, 2010 10:40:35 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320400> <The log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log00281. Log messages will continue to be logged in /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log.>
<Jun 3, 2010 10:40:36 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
<Jun 3, 2010 10:41:10 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 3, 2010 10:43:51 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Jun 3, 2010 10:43:53 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/worklistapp/r8n7fr]. Make sure the referenced optional package has been deployed as a library.>
<Jun 3, 2010 10:44:07 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
<Jun 3, 2010 10:44:35 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "jsp" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Jun 3, 2010 10:44:46 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh], [Extension-Name: oracle.soa.adapter, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh]. Make sure the referenced optional package has been deployed as a library.>
<Jun 3, 2010 10:45:00 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-soa": Socket read timed out>
<Jun 3, 2010 10:45:02 PM EST> <Error> <oracle.mds> <BEA-000000> <
oracle.mds.lcm.exception.MDSLCMException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
     at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:170)
     at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
     at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
     at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
     at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.mds.exception.MDSException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
     at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:80)
     at oracle.mds.internal.persistence.db.DBStoreUtils.getConnectionManager(DBStoreUtils.java:389)
     at oracle.mds.persistence.stores.db.DBMetadataStore.checkRepositoryCompatibility(DBMetadataStore.java:815)
     at oracle.mds.persistence.stores.db.DBMetadataStore.checkCompatibility(DBMetadataStore.java:1092)
     at oracle.mds.persistence.stores.db.DBMetadataStore.<init>(DBMetadataStore.java:276)
     at oracle.mds.internal.lcm.MDSLCMManager.createMetadataStore(MDSLCMManager.java:2064)
     at oracle.mds.internal.lcm.deploy.DeployManager.createMetadataStore(DeployManager.java:660)
     at oracle.mds.internal.lcm.deploy.DeployManager.deployToDBRepository(DeployManager.java:974)
     at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:445)
     at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:168)
     at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160)
     at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
     at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
     at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
     at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi
Thanks for your reply
Here is my installation details on Linux 32 bit OS:
Weblogic server- wls1032_linux32.bin
Repository Creation Utility- ofm_rcu_linux_11.1.1.2.1_disk1_1of1.zip
SOA Suite- ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip
JDeveloper Studio, base install- jdevstudio11112install.jar
SOA Extension for JDeveloper- ofm_osb_generic_11.1.1.3.0_disk1_1of1.zip
The installation went very smooth and there was no errors in the same.
I can successfully start the Weblogic Administration server from the command line but unable to start successfully SOA Managed (soa_server1), Infra and BAM server (bam_server1). I tried starting SOA Managed (soa_server1) from command line as well as from Weblogic console EM (after starting Node Manager) but always receiving the errors I uploaded in my post earlier. As a result I am unable to deploy any composite application
Please advice
Thanks
Rohit

Error in server.log , while starting soa managed server - B2B not running

Hi All
After starting SOA managed server , we found following error in the server.log , we are successfully able to access em and admin console , but while trying to access B2B console getting no response.
Please help us in understaning this error.
[ServletContext@15501276[app:b2bui module:/b2bconsole path:/b2bconsole spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@4e8b8[ GET /b2bconsole/faces/login.jspx HTTP/1.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Referer: http://172.16.130.34:7001/console/console.portal?_pageLabel=WebAppModuleTestingPage&_nfpb=true&WebAppModuleTestingPortletexpandNode=ROOTCHILDNODE1 Cookie: JSESSIONID=8R1ZM24XMQDs1Z22QNJ4YM1cMrGlKbd77nCTLkTW62Bkvw2nG6vx!-1614137459; ADMINCONSOLESESSION=LKZJM23fPzQQsM2GyHDHWtJ2L8nNNzmB3gNQG1n1phMwv41mJMVN!-145877631 ]] Root cause of ServletException. java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.trinidadinternal.convert.ColorConverter at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.faces.application.ApplicationImpl.newConverter(ApplicationImpl.java:1114) at com.sun.faces.application.ApplicationImpl.createConverter(ApplicationImpl.java:770) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.addConverterByTargetClass(ConverterValidatorRegistrationUtils.java:164) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:84) at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:77) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:206) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:329) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:86) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64) at oracle.adfinternal.controller.application.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:56) at oracle.adfinternal.controller.application.model.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:70) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.tip.b2b.ui.util.SessionTimeoutFilter.doFilter(SessionTimeoutFilter.java:240) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:143) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
Satendra Pare

Which version of weblogic and SOA suite have you installed? Which OS are you using? Check on em whether soa-infra is up?
BTW, for Oracle B2B related questions, you should raise threads in Oracle B2B forum -
Integration - B2B
Regards,
Anuj

Could not create JVM Virtual machine(While starting soa managed server)?

Hi,
While starting managed server I am getting following errors:
Could not commit 1048576KB heap memory at 0x0000000004790000.
Could not create JVM Virtual machine.
After above error SOA managed server is to be down.
Please help me that how can i resolve this issue.
Thanks
Dharm

Hi Dharm,
This is typically printed when we are short on memory.
What is OS version and JDK being using here ? 32bit or 64bit ?
Current Xms and Xmx values ?
Thanks,
Sharmela

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Error while starting Soa Managed server on weblogic11g

Hi All,
I am facing one issue while starting the soa managed server on weblogic11g.
it gives error like :
"<Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
What can be done to get over this issue & start the soa server ???
Thanks & Regards,
Nupur

Hi,
Full stack trace of log is :
<Apr 12, 2011 7:04:19 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
     at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
     at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
     at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
     at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
     Truncated. see log file for complete stacktrace
>
<Apr 12, 2011 7:04:41 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'soademoDatabase1' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: ORA-28001: the password has expired
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:479)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:173)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
     at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
     Truncated. see log file for complete stacktrace
Apr 12, 2011 7:05:49 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
     at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
     at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
     at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
     at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
     Truncated. see log file for complete stacktrace
<Apr 12, 2011 7:05:53 AM IST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
<Apr 12, 2011 7:05:56 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FtpAdapter' due to error weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty..
weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty.
     at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:224)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     Truncated. see log file for complete stacktrace
No this is not a clustered environment.
yeah but under domains there are two domains we have created.
i.e. domains/ domain1 domain2
both are having soa servers as managed server.
in one domain soa is up but in domain2 it is not getting up causing above errors while starting.
FYI : It is causing problem now only.. before this , soa server on both the server have been up & running simultaneously.
Regards,
Nupur

Error in Starting soa Managed server on WEBLOGIC 11g..Windows 7

Hi All,
I have an exception coming up while starting the soa_server1 managed soa server in Weblogic Domain.
I have started the Admin server but while starting the soa managed server we are getting the following error :
<Jul 26, 2010 9:29:04 PM PDT> <Critical> <EmbeddedLDAP> <BEA-000000> <java.io.Fi
leNotFoundException: D:\Oracle\Middleware\user_projects\domains\SOA_Domain\serve
rs\AdminServer\data\ldap\replicadata\soa_server1.status (The process cannot acce
ss the file because it is being used by another process)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
at com.octetstring.vde.replication.Replicator.increment(Replicator.java:
88)
at com.octetstring.vde.replication.Replicator.run(Replicator.java:301)
at com.octetstring.vde.replication.Replication.run(Replication.java:339)
>
Pointers on this error would help us.
Regards,
Ramnath

Lets us try to start your environment by using a WLST script.
Before you try starting the servers by using the script, could you first check your weblogic console,
to see if the server soa_server1 is running or not (click on environment, servers) maybe the enterprise manager is out of sync.
The following steps are necessary the run the script:
First edit the nodemanager.properties (which is located in the directory <middleware-home>/wlserver_10.3/common/nodemanager).
Find the entry StartScriptEnabled and set this property to true.
Open a command shell and navigate to the directory <middleware-home>/wlserver_10.3/server/bin and run the file setWLSEnv.cmd
(this sets your environment variables, so that we can run a WLST script).
Copy the following script into a file named for example StartScript.py and adjust variables as needed
beahome = '<middleware-home>';
linux = false;
adminusername = 'weblogic';
adminpassword = 'transfer-solutions';
domainname = 'base_domain';
pathseparator = '/';
if not linux:
print 'SETTING WINDOWS PATH SEPARATOR';
pathseparator = '\\';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START SOA SERVER';
start('soa_server1','Server');
nmServerStatus('soa_server1');Run this script as follows, but first stop the servers already running
java weblogic.WLST <directory>/StartScript.py

Error while starting the Weblogic Server in SOA Suite

Hi All,
I installed SOA Suite 11.1.1.4.0 (weblogic server and SOA managaed server) couple of days back.The same machine has two more weblogic servers which contain different applications.(Means there total three Weblogic admin servers and one SOA manage server).
I used to start all the servers successfully .I also used to start SOA server successfully .
But today when I am trying to start Weblogic Admin server(SOA related),I am getting below error:
Error Log:
***C:\Oracle\Middleware\user_projects\domains\mdm_soadomain\bin>startWebLogic***
***The system cannot find the path specified.***
-------------------------- --------------------------- some error log content here -------------------------------------
***ib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=true -Dwlw.iterativeDev***
***= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= weblogic.Server***
***Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Server***
***Caused by: java.lang.ClassNotFoundException: weblogic.Server***
***at java.net.URLClassLoader$1.run(URLClassLoader.java:202)***
***at java.security.AccessController.doPrivileged(Native Method)***
***at java.net.URLClassLoader.findClass(URLClassLoader.java:190)***
***at java.lang.ClassLoader.loadClass(ClassLoader.java:306)***
***at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)***
***at java.lang.ClassLoader.loadClass(ClassLoader.java:247)***
***Could not find the main class: weblogic.Server. Program will exit.***
***C:\Oracle\Middleware\user_projects\domains\mdm_soadomain\bin>***
I saw setDomainEnv.cmd file and all other files.I did not change anything recently.But I am nit getting any idea why that exception is coming.
PLease give me guidance for this.
Thanks in advance
Edited by: 899283 on Jun 7, 2013 5:06 AM

Hi,
Is the message "The system cannot find the path specified." reported as a direct response on the "C:\Oracle\Middleware\user_projects\domains\mdm_soadomain\bin>startWebLogic" command, by Windows? Or do you see that this command really is executing but is the message reported later in the logs? Is it also reported on the command window output?
From your questioning I take it that the command initially really is executing and that the path not found message is reported later in the process. In that case it you should debug the start process. My method in these cases is adding recognizable echo statements in the weblogic start scripts. Firstly to see how far the process comes, which statements are executed. Basically to narrow down at what specific statement/command the scripts fails.
Secondly to echo the specific environment variables used. These things don't happen "magically" somehow, somewhere, something is changed. Although you might not find out when it was and who was responsible.
What might help is to know that the startWeblogic script is calling the setDomainEnv script in the same folder and also does a call to a weblogic settings script in the weblogic binaries folder from the weblogic home. (I don't know the scripts name by heart and I haven't have a VM started with a WLS env right now.
Then after these two scripts and doing some Environment variable checking to build up the arguments (java vendor, memory-args, etc.) for the java-process, it in the end calls the java-process from the choosen JVM-home. So it might be interesting to look up the place where it actually calls java. And right before that put echo's to display the JAVA_HOME and the complete java-command that it plans to execute. It might be that you installed another JVM/JDK, maybe you updated the default JVM on windows? And that it just can't find the correct JVM.
In setDomainEnv you can set up the paths to the different JVM's. Using the JAVA_VENDOR environment variable you can switch between them.
For instance, if you want to use JRockit, look voor the BEA_JAVA_HOME. The variable for Sun Hotspot should be around there as well. Validate those.
Hope this helps.
Regards,
Martien

ADF Logger in SOA Managed Server

Hi All,
I have implemented an ADF Logger in my ADF Application which is deployed on the SOA Managed Server.
I have followed the steps shown here :- http://digitalspace.wordpress.com/2011/04/08/adf-debugging-how-to-add-custom-log-messages-using-adflogger/
and then as per the blog , i have changed the logging.xml file,specified the custom logger and modify the setDomainEnv of SOA Managed Server.
I am able to print the log message using the ADF Logger when my custom logger level sets to FINEST.
Now i need to modify or remove the Custom Logger from logging.xml, and i did but it didn't reflect at runtime.It still prints the log.
After restarting the server, i get the appropriate result i.e it doesn't print the log message.
My question is :- 1.Do we need to restart the managed server if we modify the logging.xml ?
2.Is there any other configuration file where i need to put the custom logger definition?
3.Is there any way to modify all these things using the enterprise manager?
Please Suggest!!
Regards,
Shah

Hi,
I have implemented the above mentioned suggestions. But seems to have no luck. I had
1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
prps=makePropertiesObject(arg)
nmStart('soa_server1',props=prps)
This started throwing Boot Identity file not valid.
I changed my way.
1. Connected to Admin Server using WLST
connect (username, password)
2. Start MS
start('soa_server1')
Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
Regards,
Bhaskar

SOA Managed Server -- STATE -- Admin

Hello Experts:
Env:
Sun Solaris 10
Web Logic 10.3.6
SOA 11.1.1.6.0
2 Node cluster
Installed WLS and SOA. Config went well. When I start SOA Managed server, the STATE is "Admin". The issue is SAME when starting SOA in Command line as well as Console.
When I use Console and try for "resume" it goes to "Active" STATE. How to fix this issue??
I must be able to start SOA from Console and it should go to "Active" state. Can you please help me to fix this??
Any help is appreciated.
Thanks
Rgds
Natrajan

Natrajan,
One of the reasons for the managed server to go to ADMIN state is due to the failed deployments.
The failed deployments can be the failed deployments of the application(.war,.ear files) or due to failure in the creation of JDBC Resources/JMS Resources.
Please check in the logs if the managed server reports of any failed deployments.
Regards,
Abhinav Gupta

SOA managed server startup problem

Hi All,
I am facing an issue while starting the SOA Managed Server (soa_server1) using NodeManager.
Backgound:
I have setup a soa domain, started up NM and admin server using NM in solaris environemnt. All runs fine but when I start MS using NM for the first time it throws error. If I start the MS from the admin console it starts fine. The execution steps I have performed-
1. Started NodeManager - using script
2. Shutdown the NodeManager , changed the nodemanager.properties file to update parameter [startScriptEnabled=true] and start it again.
3. Started AS using NM [nmConnect(..) and nmStart('AdminServer')]
4. Enrolled the NM with the current machine [connect(..), nmEnroll(domain_dir, nodemanager_home)]
5. Copied the boot.properties to security/ dir of soa_server1
6. Started MS using NM - Throws error
Does it really mean I have to start the MS through admin console everytime I start MS first time in the machine? (I am working on automation on SOA env where everynight env wipes off and installs the SOA stack from scratch)
The soa-server1.out looks like:
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<15-Mar-2012 10:26:41 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.1-b02 from Sun Microsystems Inc.>
<15-Mar-2012 10:26:42 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<15-Mar-2012 10:26:45 o'clock GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Booting as admin server, but servername, soa_server1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
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: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)
>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<15-Mar-2012 10:26:45 o'clock GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<15-Mar-2012 10:26:45 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <Waiting for the process to die: 20518>
<15-Mar-2012 10:26:45> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<15-Mar-2012 10:26:45> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Please help with your expertise.
Apologies if I have missed any info or posted in wrong forum, if you need more feel free to shout.
Thanks in advance.
Cheers,
Bhaskar

Hi,
I have implemented the above mentioned suggestions. But seems to have no luck. I had
1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
prps=makePropertiesObject(arg)
nmStart('soa_server1',props=prps)
This started throwing Boot Identity file not valid.
I changed my way.
1. Connected to Admin Server using WLST
connect (username, password)
2. Start MS
start('soa_server1')
Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
Regards,
Bhaskar

Delete & recreated SOA managed server - throws exception

Hi,
I have a weblogic admin server and soa,osb managed servers running in other machines.
From weblogic console, I deleted the SOA managed server and created it again. I have lot of deployments and in targets, I added the newly created soa server for only one deployment 'usermessagingserver'.
When starting the soa server, I get
<Nov 4, 2010 12:34:24 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Nov 4, 2010 12:34:25 PM CST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'usermessagingserver' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.sdp.messaging, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false], [Extension-Name: oracle.rules, exact-match: false], [Extension-Name: adf.oracle.domain, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.sdp.messaging, exact-match: false], [Extension-Name: oracle.sdp.client, exact-match: false], [Extension-Name: oracle.rules, exact-match: false], [Extension-Name: adf.oracle.domain, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
Truncated. see log file for complete stacktrace
Is there a way I can add the newly created soa server in targets for all the deployments with ease?
What is the resolution for this exception?
Is there a procedure to follow when deleting and creating managed server from console?
When i add soa server in target0s for soa-infra, b2b ..... it is also failing with the same exception.
Any help?
Thanks in advance.
Ganesh

You have to make sure that the libraries,which are references by your application,
are also targeted to the server.
In the weblogic-application.xml file of your appllication these libraries are referenced due to
for example the following entry:
<library-ref>
<library-name>oracle.sdp.messaging</library-name>
<exact-match>false</exact-match>
</library-ref>You can target the libraries by clicking on the library deployment in question, click on
the targets tab and choose the servers to which you want to target the library.

Is there any way changing the priviledge after starting the managed server with the other user

Hi,
is there any way to change the user privilege after i have started the managed
server with one user.....say for example ....i have started one of my Managed
server as "root" ...but after that i wanted to make this instance work under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Thanks again Rob.
Rob Woollen <[email protected]> wrote:
>
>
sangita wrote:
Thanks Rob for been so quick in responding.
I have 3 questions for you:
Running a server under root is a huge security hole.My Question: 1) what are the probable security issues while runninga server under
root ?
are these security issues external(from outside world) or internal(internally
within a company) ?
Iam basically curious to know external threats.
The problem is the root user can do anything. So if someone finds a
security hole in your server, then they have complete control of your
system.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.My Question: 2) What is the harm in using port 80 for webserver andwhy do the
people wanted to bind to a port < 1024 ?
People normally use 80 for web servers because that's the well-known
port.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.My Question: 3) Suppose iam having a cluster of 2 Managed servers runningon port
7070. And Iam having a Iplanet server working as a Webserver that basicallyproxies
requests to this cluster. Then what is the best approach that i shouldfollow
in this context.....to be honest with you ....i still couldnot understandwhat
does "binding" the webserver port to a managed server in weblogic mean.
I would have your firewall redirect 80 to whatever port Iplanet is
listening on and then have iplanet proxy to WLS.
Do not run your WLS servers as root.
-- Rob
Iam sorry for asking these "silly" questions(in your opinion) ...butiam a bit
confused.
thanks, sangita
Rob Woollen <[email protected]> wrote:
Running a server under root is a huge security hole.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.
There is a set uid option in WLS where you start the server as root
and
then after it binds to the low port, it will switch to another userthat
you specify.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.
-- Rob
sangita wrote:
<Sure, it's possible to do this, >
how to do this?
<but why do you want to do it? >
Iam not sure why this group (the other group than me) does start theirserver
as "root"...but somebody from that group asked me about this today.
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.then what is the best approach and what are the pros and cons if westart the
server as "root" OR as different user ????
please advise ....
thanks again.
Rob Woollen <[email protected]> wrote:
Sure, it's possible to do this, but why do you want to do it?
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.
-- Rob
sangita wrote:
Hi,
is there any way to change the user privilege after i have startedthe managed
server with one user.....say for example ....i have started one
of
my Managed
server as "root" ...but after that i wanted to make this instance
work
under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Problem in starting OIM managed server

Hello,
After configuring the Managed server in a cluster, when we try to start the server it is starting in ADMIN mode.
The SOA Managed server was started successfully.
23:41:38 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] - Nexaweb Server initialized successfully.
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of oim_cluster.>
<Sep 20, 2011 11:42:10 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.10.243:7003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 20, 2011 11:42:10 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "WLS_OIM1" for domain "IDM_Domain" running in Development Mode>
<Sep 20, 2011 11:42:13 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 20, 2011 11:42:13 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
Please let us know how to make the server run in RUNNING mode.
Thanks.

Have you done any changes in Weblogic Admin Console ?
Login into Weblogic Console and see what it shows for "Undo All Changes" and "Activate Changes" button.
If "Activate Changes" in enabled then click on that and try to restart.

Error while starting weblogic Managed Server

Hi ,
I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
while starting Managed Server.It gives me an error saying
<Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
from Sun Microsystems Inc.>
<Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
Server may already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
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: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)>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Can anyone help ?
Regards,
Vikas Manchanda
Edited by: 829347 on Feb 2, 2011 12:48 AM

How are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
Damien

Failure to start SOA managed server after SOA 11.1.1.5 install

Similar Messages

Maybe you are looking for