SOA Cluster- Server Migration

Hi All,
I m installing SOA suite in high availability environment (cluster) and I want to understand why I do need to configure Server Migration for SOA and OSB managed servers, what will happened if one of the managed serves fails and I didn't migrate it to the node? Does this affect the running BPEL instance by any mean? And how the users will be affected?
Any helpful answers will be appreciated
Regrads,
Ahmed Saber

Thank you Robert for your reply.
I still want to understand what will happen for the BPEL process and oracle service bus if server migration is not configured and one of the node get down.
I understood from the link you sent that there are some singleton services that can only run on one node that's fine but I still want to understand from the business point of view how this might affect BPEL process and oracle service bus?
Regards,
Ahmed

Similar Messages

  • BAM Cluster setup - issue with whole server migration configuration

    HI,
    We are working on a SOA , BAM , BPM Cluster setup on OEL VMs
    With Admin server running on Host1 and Soa_server1, BAM_server1 , Host2 - Soa_server2 , Bam_server2.
    We were successfully able to setup clustering for Soa without using the webTier utilities in our environment, Just by adding entries in the /etc/hosts file.
    Followed the document - except for web tier setup
    http://www.namredlek.nl/orasoa/InstallSOASuite11gOnCluster_v1.pdf
    1)     Installed Weblogic 11g.
    2)     Soa 11g.
    3)     Domain creation
    4) Configured Node manager
    5) Soa Clustering completed successfully.
    6) Domain up and running with SOA_Cluster up and running.
    7)     Extended the domain with BAM
    The issue revolves when we are doing teh Migration configurations from the console for BAM and we restart BAM server we get an error -
    Apr 14, 2011 2:30:35 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'bam_server1'
    java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
    and Bam server goes to Failed Not Restartable state.

    The error is clearly out there
    java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
    This error occurs due to a failure in adding the virtual IP of BAM server to the network interface you have specified in nodemanager.properties.
    You need to check whether you have specified the correct interface and subnet mask in node manager.properties as below :
    The fourth step is to edit the Node Manager's properties file. This file is called nodemanager.properties
    and is located in the ORACLE_BASE/product/osbmw/wlserver_10.3/common/nodemanager directory.
    For server migration to work properly, you need to add the properties listed below:
    Interface=eth0
    NetMask=255.255.255.0
    UseMACBroadcast=true
    · Interface
    This property specifies the interface name for the floating IP (for example, eth0).
    · NetMask
    This property specifies the net mask for the interface for the floating IP. The net mask should the
    same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
    · UseMACBroadcast
    This property specifies whether or not to use a node's MAC address when sending ARP packets,
    that is, whether or not to use the -b flag in the arping command.

  • SOA Managed Server cloning and adding it to a cluster.

    Hi,
    The following is the configuration I have in my machine already.
    ->Weblogic 10.3
    ->Domain : soa_domain
    ->Contains AdminServer and a soa manged server (soa_server1)
    I would like to have another managed server (soa_server2) so that I can create a cluster around soa_server1 , soa_server2.
    Note : I have only one machine here and both my managed servers are going to be on the same machine.
    What is the easiest way to do the same. I tried out the cloning of existing managed server ( soa_server1) to create another managed server(soa_server2) but it doesnt make a complete copy ie., the Jdbc,jms,wormanagers,application deployments etc...are not copied.
    Is it possible to create an exact replica of an existing managed server with all the deployments and conofgurations.
    Help is appreciated. Thanks.
    Regards,
    Sridhar.

    If you did not build the cluster in the first place, I don't think it is possible to add a cluster and a second server.
    You can add nodes to exsisting clusters but the last time we tried adding a cluster and a second node, we could not do it.

  • 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

  • SOA Cluster Deployment of Composite through FMW Control - 401 Error

    When I am deploying to SOA from Fusion Middleware Control with the "weblogic" domain account, I get a 401 error in the AdminServer.out. It cannot deploy the composite to the SOA Cluster. This user is in the Administrator's group, so it should have complete access to the domain.
    Anyone seen this before or have any ideas how to debug?
    Processing sar=/tmp/dir3336911530631824248tmp/sca_TestingMain_rev1.0.jar
    Adding sar file - /tmp/dir3336911530631824248tmp/sca_TestingMain_rev1.0.jar
    INFO: Creating HTTP connection to host:soahost2vh.mydomain.com, port:8001
    INFO: Received HTTP response from the server, response code=401
    SEVERE: Problem in sending HTTP request to the server. Please make sure the server is up and/or check standard HTTP response code for 401
    Processing sar=/tmp/dir3336911530631824248tmp/sca_TestingMain_rev1.0.jar
    Adding sar file - /tmp/dir3336911530631824248tmp/sca_TestingMain_rev1.0.jar
    INFO: Creating HTTP connection to host:soatest1vh.mydomain.com, port:8001
    INFO: Received HTTP response from the server, response code=401
    SEVERE: Problem in sending HTTP request to the server. Please make sure the server is up and/or check standard HTTP response code for 401
    Edited by: Josh on Sep 15, 2011 11:05 PM

    Hi Josh
    I hope you have a SOA Domain created that has AdminServer and atleast one soa_server1 managed server. Ofcourse you can have Developers SOA Domain that has only AdminServer with SOA modules also deployed. So first make sure you have SOA Domain. Assuming you have SOA Domain, generally it is recommended to deploy/undeploy any SOA Composite JAR from the Enterprise Manager console (not from core weblogic admin console like http://host:port/console). The Enterprise Manager facet has to be checked when you create SOA Domain. Then you can access it like http://host:port/em. Then on left side, select your soa_server1 and right click mouse and deployments and deploy your soa sca jar file. This takes care of backend soa_infra and other db tables properly updated with all the info from your sca jar file.
    So try from Enterprise manager.
    Infact if you have JDeveloper, just configure your soa domain there. And you can deploy directly from JDeveloper itself on this SOA Domain.
    Thanks
    Ravi Jegga

  • Server Migration

    I'm having a problem setfing up migration on my Managed Servers on Welbogic 9.2 mp2. First, My problem.
    When I try to manually migrate ManagedServer1 from MachineA to MachineB:
    Nodemanger shutdowns ManagedServer1
    Nodemanager removes the interface with the floating IP (so far so good)
    (here is where the problem starts)
    Nodemanager brings up the interface back on MachineA
    Nodemanager starts ManagesServer1 on MachineA (all this is suppose to happen on MachineB).
    This doesn't help me if it migrates it to the same machine!!!
    I quick overview of how things are set up.
    1) I have two machines, MachineA and MachineB running Solaris 10
    2) I have the admin server running on MachineA listening on the static ip of 139 and ManagedServer1 listening on the floating IP of 169 (fyi, don't want give out IP, so I made a number up)
    3) I have ManagedServer2 running on MachineB with the floating IP of 170.
    4) I created a weblogic user that has ssh trust config between the two machines and has the proper authority to create and bring down an interface.
    5) Created 2 Unix machines, Type SSH with the shell command ssh -l legalint -o PasswordAuthentication=no -p %P %H /opt/bea/weblogic92/common/bin/wlscontrol.sh -d %D -n /legalint/mtdom/ndmgr -c -f startManagedWebLogic.sh -s %S %C
    6) Network Time Protocal Config is set
    7) Lease database schema is created with corresponding data source and has two tables ACTIVE and ACTIVE_MT
    8) Server migration progerties configured: cluster datasource is set (In my directions it tells me to leave the Canidate machines blank). Managed servers auto migration set to true and primary and back-up machine set and auto-restart set to true.
    Any help is appreciated.
    Tom.

    The best way to deal with certificates and FQDN's in ZESM is to use commercial issued certificates or from the company's internal CA. Don't use the built-in product self-signed certificates under any reason for production deployments. The reason behind that, is that the internal ZESM certificate has its private key marked as non-exportable. So you'll not be able to export it from one server and move to another.
    For the server FQDN, create an A or Alias record in DNS to something like: "zesm.company.com", and point it to the actual ZESM server, that way, once you need to move all users from server, all that you need to do is to import the commercial certificate and point the DNS record to the new server IP Address.
    I did a couple of deployments in that way, with no issues.
    Hope this helps.
    >>>
    From: mauro vaccari<[email protected]>
    To:novell.support.zenworks.endpoint-security-management
    Date: 1/19/2010 7:36 AM
    Subject: Server Migration
    Hi,
    planning the upgrade to the imminent release of ZESM 4.1 we would like
    to reinstall the server because it has undergone many installations.
    For security reason and for don't stop production we want to install
    ZESM 4.1 in a new server with the same ip and name of the actual then we
    want try It in a test VLAN.
    My question is:
    when we want to pass the new server in production or before ZESM
    instalation could we migrate the IIS certificate from the old server to
    new one? so the client should not be involved.
    Thank you for help
    mauro_vaccari
    mauro_vaccari's Profile: http://forums.novell.com/member.php?userid=16902
    View this thread: http://forums.novell.com/showthread.php?t=398639

  • 10.3 Whole Server Migration

    Hi,
    I need some enlightenments from all. Here is my setup (in Windows 2003 R2)
    2 physical Server, PS A, PS B (PS: physical server)
    PS A contains, 1 Admin Server, 1 Managed server
    PS B contains, 1 Managed Server
    I've done the necessary clustering setup and tested its working, using node manager (nmenroll, conseus, etc). now what I'm trying to perform is to try out whole sever migration.
    I've found out the script, wlsifconfig.cmd (found under %wls_home%\user_projects\domains\abc\bin\server_migration\, contains some linux command such as grep and rm. Workaround installed grep command for windows and replace rm with del.
    I've shut down all managed servers and configure the managed servers to be whole server migration ready, set the node manager properties etc. I start the managed server 1 in PS A, PS A contains the floating IP upon starting. I checked using ipconfig, the floating IP is added. Then I tried to start managed server 2 through the admin console in PS A. Here comes the problem, managed server 2 also add in the floating IP which resulted in windows IP conflict. I'm not sure what went wrong, as of now i suspect is the wlsifconfig.cmd is the root of the problem. Therefore writing in to ask help from all. (Could it be im using 10.3 which does not support whole server migration?)
    Best Regards

    This appears to be working on Windows using 10.0.3 Server. For the lack of step-by-step tutorial, my best suggestion is to read Node Manager Administrator's Guide chapter 1,2,3,4,6 and "Using Clusters" chapter 7. I ran into many error messages and had to apply several hacks from google results.
    The whole server migration design does not appear to be too useful though.
    I have the whole server migration configured on two hosts.
    1. Machine A has AdminServer and M1 (runs a pinned application and happens to be assigned a cluster master)
    2. Machine B has node manager and M2.
    3. M1 is set up to be migratable to A and B
    I shutdown Machine A, but nothing is migrated. From the document, it seems both cluster master and AdminServer need to be running in order for migration to happen. This is still a single point of failure.

  • SOA Suite 11g composite application deployment to SOA cluster?

    What is the best practice for 11g composite app deployments to a SOA cluster? Currently, when customer deploys SOA composite it only gets deployed to one of the SOA managed servers in the cluster and the only way for them to sync up SOA1 and SOA2 is by bouncing the servers. Is there a best practice on how to deploy composite apps to SOA clustered env?

    1) When we deploy the composite, will it be distributed across all the servers in the cluster ? or only in one server?
    If you deploy it on to cluster it will be distributed across all the servers.
    2) If i have a composite which polls the file, and we deploy this composite in the cluster, How to avoid the locking between two processes since both are same and polling to same directory?
    Set the connectionfactory to this value eis/HAFileAdapter for example
    <adapter-config name="FlatStructureIn" adapter="File Adapter"
    xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata"> *<connectionfactory*
    location="eis/HAFileAdapter" UIincludeWildcard="*.txt" adapterRef=""/>
    <endpoint-activation portType="Read_ptt" operation="Read"> <activation-spec
    className="oracle.tip.adapter.file.inbound.FileActivationSpec"../> <property../>
    <property../> </activation-spec> </endpoint-activation> </adapter-config>

  • 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

  • Bam Server migration - need info

    Hi All,
    SOA 11.1.1.7
      I have a question regarding bam server migration. As BAM Server is singleton, I just want to confirm if my understanding is correct.
    Example
         - bam_server1 & bam_server2 in BAM_CLUSTER.
         - bam_server1 is configured to be singleton.
    Scenario 1  - All 2 Server is up and running in BAM_CLUSTER.
           Request1 goes to bam_server1 which gets processed
           Request2 goes to bam_server2 which internally routes to bam_server1(which is hosting the singleton service)
    Scenario 2 - bam_server1(singleton) is killed, only bam_server2 is running
           Request 1 goes to bam_server2 which holds the request as there is no singleton service available.
           Request 2 goes to bam_server2 which is also held without getting processed.
           bam_Server1(singleton) is migrated to new machine and restarted.
           all the request waiting on bam_server2 is routed to bam_server1 which processes the request.
    Am i right in saying the request going to bam_server2 will be held and not lost while bam_server1(singleton) is migrated completely.?
    Thanks in advance.
    /SR

    Hi All,
    SOA 11.1.1.7
      I have a question regarding bam server migration. As BAM Server is singleton, I just want to confirm if my understanding is correct.
    Example
         - bam_server1 & bam_server2 in BAM_CLUSTER.
         - bam_server1 is configured to be singleton.
    Scenario 1  - All 2 Server is up and running in BAM_CLUSTER.
           Request1 goes to bam_server1 which gets processed
           Request2 goes to bam_server2 which internally routes to bam_server1(which is hosting the singleton service)
    Scenario 2 - bam_server1(singleton) is killed, only bam_server2 is running
           Request 1 goes to bam_server2 which holds the request as there is no singleton service available.
           Request 2 goes to bam_server2 which is also held without getting processed.
           bam_Server1(singleton) is migrated to new machine and restarted.
           all the request waiting on bam_server2 is routed to bam_server1 which processes the request.
    Am i right in saying the request going to bam_server2 will be held and not lost while bam_server1(singleton) is migrated completely.?
    Thanks in advance.
    /SR

  • Is Load Balancer a Must for SOA Cluster

    Hi,
    We are trying to bring up a soa cluster of 4 soa_servers
    We have deployed the code and seems to be picked up by all the soa_servers properly.
    The issue we are facing is all the partner link references (which are internal composites in the cluster) is pointing to one of the soa server (i.e. the one we have used during deployment)
    Because of this there is no load balancing happening and effectivly only one of the server is fully loaded.
    If this is the expected behaviour, is a load balancer/proxy server a must for a soa cluster ?
    Thanks,
    Ajay....
    Edited by: ajaykumar on Sep 6, 2010 8:54 AM

    Dear All
    Weblogic Server Cluster Domain by default WILL NOT have any Load Balancer and WILL NOT do any load balancing stuff. Any Weblogic Cluster should and must have some sort of Software or Hardware Load Balancer in front of WLS Cluster Domain. Most of the customers use open source Apache Http Server which is very simple configuration and works fine. See this below link for Apache details. Go back on this link to see other WebServers like IIS or Sun WebServer etc. You can use Hardware load balancer.
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e14395/apache.htm#CDEGCBAC
    The basic steps are in one of the webservers configuration files, you specify the details of backend WLS clustered managed servers host and ports with comma separated. Now this Apache or any other WebServer runs at some host and port. Now this is the host and port that you need to configure for any WebServices WSDL URLs. Then load balancing will happen. So even though we do development say from JDeveloper we create WSDLs or WebServices client using single WLS Server Domain. So naturally that WSDL will have that domains host and port hardcoded. But when you export this webservice .war file and deploy in cluster env you have option to invoke which wsdl url. When we get the WebService Service Object, usually there are 2 constructors. One that take no parameters and internally it goes to the default wsdl url specified in the .wsdl file. Another constructor takes 2 parameters like wsdl url and QName for Service. If you see that service .java file generated when you create client jar for the WebService you will get an idea. So the point is in your client program use the second constructor and for wsdl url, use load balancers host and port and rest will be same. Infact you can put this wsdl url in .properties file also which goes under say WLS Domain folder. So for diff env like Test, QA, Prod etc you can have diff values for wsdl url in .properties file specific to that environment.
    So bottom line for Load Balancing we do need external load balancer in front of Weblogic Cluster Domain.
    Thanks
    Ravi Jegga

  • Whole server migration

    Hi,
    I am setting up a cluster with two managed serves on different machines. In order to setup whole server migration, do I need to have third machine? In many of the examples i have seen they say when MACHINE1 is down, it can be migrated to MACHINE2..how is this possible if both managed servers listening on the same port? can you please let me know if I need to have third machine? if so, do I need to transfer the domain data via pack and unpack to third machine as well?
    Thanks.

    Hi
    Since your 2 managed servers are on 2 different physical machines, yes, they can share the same port number. Remember they had different host numbers. If they are on same physical machine, naturally you will have 2 different unique port numbers. Now coming to failover, generally for any Cluster Domain, in the front you will have some sort of Load Balancer. The typical example is Apache HTTP Server as Load Balancer. We install and configure apache and edit httpd.conf file to give backend weblogic servers. For example one line could be like this:
    ClusterAddress: host1:port1,host2:port2 (Ex: host1:8001,host2:8001). So it is Apache that takes care of Failover and load balancing. If host is dead or server1 on host1 is crashed, apache will remove this server from its internal list (till it is back and up and running. So all next requiests will go to host2:8001.
    This has nothing to do with same or diff port numbers. All that matters is, port numbers are unique if servers are on same physical machine.
    This means, there is no need for any other 3rd machine.
    If your question is something else, please give more details.
    Thanks
    Ravi Jegga

  • OIM-SOA CLUSTER add new node

    Hi All,
    i need to add a new node to my cluster OIM/SOA.
    My env is:
    1) cluster 6 nodes whit SOA and OIM
    2) the first node have a console weblogic server admin
    3) More patchs are installed on
    Look at this picture: [https://dl.dropboxusercontent.com/u/9054488/OIM-SOA-CLUSTER.jpg]
    I found the proc to doc.id [e10106 pag.523 - 8.9.3.20.1 Scaling Up Oracle Identity Manager] but I don't understand if it is applicable to systems already patched.
    There is a procedure already proven and clearer?
    Thanks.

    In order to add a new node, you must first install all the applications/modules in your middleware home. Install the same patches on top of those. Then using the packEnv scripts to pack up the domain, and then unpack it to your new host.
    From the weblogic console, use the option to clone your app server and create a new machine for your new machine instance. Startup your node manager on your new machine, and start your app server.
    You just need to make sure to do all the same modifications, if you have any, to your new server, like deploy jar files, make changes to UI interface, etc.
    -Kevin

  • Coherence issues on SOA Cluster

    Hi,
    Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,TST,UAT on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
    Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>>   <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>>   <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
    Message "SeniorMemberHeartbeat"
      FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
      FromMessageId=0
      Internal=false
      MessagePartCount=1
      PendingCount=0
      MessageType=17
      ToPollId=0
      Poll=null
      Packets
        [000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
      Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
      ToMemberSet=null
      NotifySent=false
      LastRecvTimestamp=none
      MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
      }>>
    <Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
         at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
         at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
         Truncated. see log file for complete stacktrace
    <div class="jive-quote"> </div>
    .....As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
    Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing.
    Thanks

    This appears related to bug 9874750. Make sure you retrieve the latest copy of the Install/Upgrade guide from support.oracle.com. Under this bug, the guide was updated to remove some preinstallation steps that were causing the installation to fail
    Edited by: rwunderl on Aug 23, 2010 6:08 AM

  • Oracle SOA Cluster soa-infra failing, startup coherence issues

    Hi,
    Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,*TST*,*UAT* on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
    Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
    Message "SeniorMemberHeartbeat"
      FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
      FromMessageId=0
      Internal=false
      MessagePartCount=1
      PendingCount=0
      MessageType=17
      ToPollId=0
      Poll=null
      Packets
        [000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
      Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
      ToMemberSet=null
      NotifySent=false
      LastRecvTimestamp=none
      MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
      }>>
    <Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
         at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
         at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
         Truncated. see log file for complete stacktrace
    >
    <anonymous>] [ecid: 0000JhFIXrrEWN0pnwh8iZ1Gi2DE000009,0] [APP: soa-infra] Cluster communication initialization failed.  If you are using multicast, please make sure multicast is enabled on your network and that there is no interference on the address in use.  Please see the documentation for more details.[[
    com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
    <Nov 29, 2012 9:20:13 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
    )As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
    Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing. Here are the unicast coherence settings we have for both servers in the console under Start Server tab as per Oracle EDG
    WLS_SOA1
    -Dtangosol.coherence.wka1=web1.xxorg.com
    -Dtangosol.coherence.wka2=web2.xxorg.com
    -Dtangosol.coherence.localhost=web1.xxorg.com
    -Dtangosol.coherence.localport=8083
    -Dtangosol.coherence.wka1.port=8083
    -Dtangosol.coherence.wka2.port=8083
    WLS_SOA2
    -Dtangosol.coherence.wka1=web1.xxorg.com
    -Dtangosol.coherence.wka2=web2.xxorg.com
    -Dtangosol.coherence.localhost=web2.xxorg.com
    -Dtangosol.coherence.localport=8083
    -Dtangosol.coherence.wka1.port=8083
    -Dtangosol.coherence.wka2.port=8083Thanks

    Hi,
    Have a 2 Node cluster od soa 11.1.1.5. Have 3 instances of 2 Node cluster running on the same machine. It's basically one for DEV,*TST*,*UAT* on the same machine. We have cronjobs that run every night shuts down all the cluster instances and then bring them back up. Recently one of our UAT soa cluster having issues. Both the Nodes come up fine but soa-infra in one node is not getting deployed and is down. I tried to manually start that node but no luck these are the errors I am getting in the Node where soa-infra is down. It's been working fine since recently. Any idea what might be wrong and where to look at. Any help is appreciated.
    Inside the console all the servers are up and running but when going to Enterprise Manager it shows soa-infra down and only see one node.
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823364> <BEA-000000> <bpel.fatal.conection.max.retry is set to 3<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.360/533.658 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2012-11-28 23:09:52.784, Address=9.9.10.95:8083, MachineId=3944, Location=site:xxorg.com,machine:web1,process:19968, Role=WeblogicServer) has been attempting to join the cluster using WKA list [web2.xxorg.com/8.8.18.85:8083, web1.xxorg.com/9.9.10.95:8083] for 30 seconds without success; this could indicate a mis-configured WKA, or it may simply be the result of a busy cluster or active failover.>>
    ####<Nov 28, 2012 11:10:23 PM CST> <Notice> <Stdout> <soadev01> <WLS_SOA1> <Logger@2067016530 3.6.0.4> <<WLS Kernel>> <> <> <1354165823365> <BEA-000000> <<Nov 28, 2012 11:10:23 PM CST> <Warning> <Coherence> <BEA-000000> <2012-11-28 23:10:23.363/533.661 Oracle Coherence GE 3.6.0.4 <Warning> (thread=Cluster, member=n/a): Received a discovery message that indicates the presence of an existing cluster that does not respond to join requests; this is usually caused by a network layer failure:
    Message "SeniorMemberHeartbeat"
      FromMember=Member(Id=1, Timestamp=2012-11-28 21:28:09.017, Address=8.8.18.85:8083, MachineId=3968, Location=site:xxorg.com,machine:web2,process:3396, Role=WeblogicServer)
      FromMessageId=0
      Internal=false
      MessagePartCount=1
      PendingCount=0
      MessageType=17
      ToPollId=0
      Poll=null
      Packets
        [000]=Broadcast{PacketType=0x0DDF00D2, ToId=0, FromId=1, Direction=Incoming, ReceivedMillis=23:10:23.353, MessageType=17, ServiceId=0, MessagePartCount=1, MessagePartIndex=0, Body=0}
      Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.6}
      ToMemberSet=null
      NotifySent=false
      LastRecvTimestamp=none
      MemberSet=MemberSet(Size=1, BitSetCount=1, ids=[1])
      }>>
    <Nov 28, 2012 11:14:53 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:6)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
         at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:637)
         at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
         Truncated. see log file for complete stacktrace
    >
    <anonymous>] [ecid: 0000JhFIXrrEWN0pnwh8iZ1Gi2DE000009,0] [APP: soa-infra] Cluster communication initialization failed.  If you are using multicast, please make sure multicast is enabled on your network and that there is no interference on the address in use.  Please see the documentation for more details.[[
    com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
    <Nov 29, 2012 9:20:13 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'soa-infra'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=ServiceMemberSet(
        OldestMember=n/a
        ActualMemberSet=MemberSet(Size=0, BitSetCount=0
        MemberId/ServiceVersion/ServiceJoined/MemberState
    )As we have 2 physical machines and have DEV (2-node soa cluster), TST (2-node soa cluster), UAT (2-node soa cluster) all running on the same machines and comes up and down for daily DB maintenance everynight. As it the UAT environment any help appreciated in pointing to tle location to debug.
    Also have Unicast operation, and use Well-Known Addressing (WKA) configured in Console under server(s)->start tab. But looks like something with coherence that's not working for the cluster to come up and failing. Here are the unicast coherence settings we have for both servers in the console under Start Server tab as per Oracle EDG
    WLS_SOA1
    -Dtangosol.coherence.wka1=web1.xxorg.com
    -Dtangosol.coherence.wka2=web2.xxorg.com
    -Dtangosol.coherence.localhost=web1.xxorg.com
    -Dtangosol.coherence.localport=8083
    -Dtangosol.coherence.wka1.port=8083
    -Dtangosol.coherence.wka2.port=8083
    WLS_SOA2
    -Dtangosol.coherence.wka1=web1.xxorg.com
    -Dtangosol.coherence.wka2=web2.xxorg.com
    -Dtangosol.coherence.localhost=web2.xxorg.com
    -Dtangosol.coherence.localport=8083
    -Dtangosol.coherence.wka1.port=8083
    -Dtangosol.coherence.wka2.port=8083Thanks

Maybe you are looking for