Whole server migarion issue in weblogic

I have configured the Script Based node manager. Through admin console i am able to start the remote managed servers psMS1 , psMS2.
192.168.9.11 –> Adminserver , psMS1
192.168.9.22 –> psMS2
We have create Two unix machine Unix1 , Unix1.
Unix1 –> assign servers Adminserver , psMS1.
Unix2 –> assing server psMS2.
The Two manager servers (psMS1,psMS2) is configured with Cluster (CLUST).
But If i configure the Whole server migration option in the weblogic Admin console. I am unable to start Two managed servers. I mentioned the Two managed severs errors logs.
psMS1 Error log :- ( 192.168.9.11 ) –> Unix1 machine
<Fri Dec 3 15:14:09 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS1 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS1/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS1 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:14:11 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:14:13 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:14:15 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:15 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:14:16 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS1/logs/psMS1.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:14:22 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:14:27 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:14:31 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:15:01 PM IST> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.11:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:250:56ff:feaf:649a:5003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:15:01 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS1" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:15:04 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:07:19 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:250:56ff:feaf:649a:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5003 was shutdown.>
<Dec 3, 2010 4:07:19 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.11:5003 was shutdown.>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:07:25 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
psMS2 Error log :- ( 192.168.9.22 ) –> Unix2 machine
<Fri Dec 3 15:32:35 IST 2010)> <Info> <NodeManager> <Starting WLS with command line: /prosun/Middleware_1033/user_projects/domains/clustdomain/bin/startManagedWebLogic.sh >
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=/prosun/Middleware_1033/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6dms.jar:/prosun/Middleware_1033/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_ocp353/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/lib/tools.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic_sp.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.jar:/prosun/Middleware_1033/modules/features/weblogic.server.modules_10.3.3.0.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/webservices.jar:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/prosun/Middleware_1033/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/prosun/Middleware_1033/wlserver_10.3/common/derby/lib/derbyclient.jar:/prosun/Middleware_1033/wlserver_10.3/server/lib/xqrl.jar
PATH=/prosun/Middleware_1033/wlserver_10.3/server/bin:/prosun/Middleware_1033/modules/org.apache.ant_1.7.1/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/jre/bin:/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/prosun/Middleware_1033/wlserver_10.3/common/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
Starting WLS with line:
/prosun/Middleware_1033/jrockit_160_17_R28.0.0-679/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=psMS2 -Djava.security.policy=/prosun/Middleware_1033/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/prosun/Middleware_1033/wlserver_10.3/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.system.BootIdentityFile=servers/psMS2/data/nodemanager/boot.properties -da -Dplatform.home=/prosun/Middleware_1033/wlserver_10.3 -Dwls.home=/prosun/Middleware_1033/wlserver_10.3/server -Dweblogic.home=/prosun/Middleware_1033/wlserver_10.3/server -Ddomain.home=/prosun/Middleware_1033/user_projects/domains/clustdomain -Dcommon.components.home=/prosun/Middleware_1033/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/prosun/Middleware_1033/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig -Doracle.server.config.dir=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/servers/psMS2 -Doracle.security.jps.config=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/carml -Digf.arisidstack.home=/prosun/Middleware_1033/user_projects/domains/clustdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/prosun/Middleware_1033/oracle_common/modules/oracle.ossoiap_11.1.1,/prosun/Middleware_1033/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=http://sis-prosun02.sis.ad:5001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/prosun/Middleware_1033/patch_wls1033/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_ocp353/profiles/default/sysext_manifest_classpath:/prosun/Middleware_1033/patch_jdev1111/profiles/default/sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Dec 3, 2010 3:32:38 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32 from Oracle Corporation>
<Dec 3, 2010 3:32:40 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 3, 2010 3:32:43 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:32:43 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 3, 2010 3:32:44 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /prosun/Middleware_1033/user_projects/domains/clustdomain/servers/psMS2/logs/psMS2.log is opened. All server side log events will be written to this file.>
<Dec 3, 2010 3:32:50 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 3, 2010 3:32:53 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 3, 2010 3:33:01 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of CLUST.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server psMS1.>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 3:33:07 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:225:11ff:feca:8710:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.9.22:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:5005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 3, 2010 3:33:08 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "psMS2" for domain "clustdomain" running in Production Mode>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 3, 2010 3:33:10 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Dec 3, 2010 4:00:32 PM IST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:225:11ff:feca:8710:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.9.22:5005 was shutdown.>
<Dec 3, 2010 4:00:32 PM IST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:5005 was shutdown.>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server start script exited>
<Fri Dec 3 16:00:38 IST 2010)> <Info> <NodeManager> <Server was shut down normally>
How to resolve the problem during the Script based node manager during the Whole Server Migration in Clustered Environment(CLUST).
In my knowledge the main reason is " <Cluster> <BEA-000163> <Stopping "async" replication service> "
Regards,
S.Vinoth Babu
Edited by: Vinoth Babu on Dec 9, 2010 2:05 AM

Maybe this helps, there are some system requirements before you can use whole server migration
- WSM uses a floating IP address, for each migratable server. This means that the migratable server candidate machines have to be in the same subnet
(because the virtual IP address must be valid on all candidate machines).
- WSM requires the use of the node manager. You must make sure the node manager on each candidate machine is properly initialized with the security-related
files it need to authenticate and accept commands from the admin server.
- WSM uses the node manager to migrate the floating IP address and assign it to the target machine. As such, the default configuration assumes that the
machines are similar; specifically, it assumes the following:
1 The netmask associated with the virtual IP is the same on all machines.
2 The network device name is the same on all machines.
3 The functional behavior of the platform-specific OS command used to add and remove the virtual IP is the same.
- WSM only supports migration of a single virtual IP address for each migratable server. Therefore, a migratable server cannot define any network channels
that use a Listen Address different from the virtual IP address associated with the server. If you need your servers to use multiple network channels associated
with multiple IP addresses, you cannot use the WSM framework.
- WSM assumes that any server-specific state is already shared through some highly available sharing mechanism. For example, the server’s default persistent store
where it keeps its XA transaction logs must be accessible on all candidate machines using the exact same path.
The configuration steps are as follows:
- Create your domain. Make sure that you set up each managed server's to Listen Address to its virtual IP address and assign it to a machine.
- Set up the node manager for each candidate machine. For each machine, edit the nodemanager.properties file to set the NetMask property to the netmask
associated with the virtual IP addresses being used and Interface to the network device name with which to associate the virtual IP address.
- Verify the domain and node manager configuration. Start up the domain and each clustered managed server via its node manager. This not only ensures that the
node managers and servers are properly configured but also initializes the node managers with the password files they need to accept commands from the admin server.
Do not forget to start managed servers on all candidate machines to ensure that the node manager and domain directory are properly initialized.
- Choose and configure your leasing mechanism. Like automatic service migration, automatic whole server migration relies on leasing. Use the cluster's Migration Configuration
tab to select the appropriate Migration Basis.
- If you choose database leasing, be sure to create and configure your nontransactional data source, create the leasing table, and use the cluster's Migration Configuration tab
to set the Data Source for Automatic Migration and Auto Migration Table Name appropriately.
- Grant superuser privileges to the wlsifconfig script. Node managers use the ${WL_HOME}/common/bin/wlsifconfig.sh script to add and remove virtual IP addresses from the
machines. By default, the file is set up to use sudo; sudo typically prompts you for your password the first time you run it and periodically after that. To do this without needing
to input your password, you need to add the NOPASSWD option to the relevant entry in your /etc/sudoers file. Do not forget to add the wlsifconfig script to your PATH so that
the node managers can locate it. (weblogic machine1 = NOPASSWD: /wlserver_10.3/common/bin/wlsifconfig.sh)
- Enable automatic server migration. The last step is to use each managed server's Migration Configuration tab to select the Automatic Server Migration Enabled checkbox
and restart the servers.
Debugging problems with whole server migration can be tricky so you will probably want to add -Dweblogic.debug.DebugServerMigration=true to the Java command line
used to start your servers.

Similar Messages

Server Startup issue with Weblogic 10!!!

Hi All,
We are on weblogic 10 and have deployed few portlets along with Vignette Portl 7.4. Whenever, we are doing a restart of managed server, we are getting below error in managed01.out:
Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)log4j:ERROR Could not parse address [].
javax.mail.internet.AddressException: Illegal address in string ``''
 at javax.mail.internet.InternetAddress.<init>(InternetAddress.java:66)
 at org.apache.log4j.net.SMTPAppender.getAddress(Unknown Source)
 at org.apache.log4j.net.SMTPAppender.activateOptions(Unknown Source)
 at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
 at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
 at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
 at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
 at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
After this, all applications are starting up without any issue. Please let me know if someone have already faced this issue before or any pointers on this?
Thanks & Regards,
Sanjeev

Hi,
I have deployed 10 or more portlets on same managed server and every portlet have a logging initiator servlet which uses log4j. During managed server startup, above exception only comes ones and after that, all portlets are starting fine. There is no issue at all with other portlet.
I was getting same error if I am not having log4j.jar in manged server JVM startup classpath for every portlet. But, once I added log4j.jar to classpath, it is coming only once and after that, all portlets are starting fine.
Any pointer to look at? I tried to add log4j.properties to startup classpath as well, but with no luck :(
Thanks,
Sanjeev

Issue in Weblogic Server - Server Stops abruptly

Hi All,
I am facing an issue with Weblogic server(8.1). One of the managed servers stops abruptly. Server run for some days. After 5 or 6 days it stops without giving any log message. Admin(mgt server) and this managed server are running in the same box(AIX Environment). Below is the only log I got. Any idea why it is happening?
According to the BEA Message it may be due to network problem. Since both the servers are running in same box, i don't think it is network issue.
Can anyone please help me on this? - thanks in advance
Log Trace Message:
==================
<AF[196]: Allocation Failure. need 528 bytes, 67173345 ms since last AF>
<AF[196]: managing allocation failure, action=1 (0/1040390840) (32611304/33283912)>
<GC(197): freeing class jsp_servlet._ofr._invoice._shipper._jsp.__exceptioninvoicelist(302453c8)>
<GC(197): freeing class jsp_servlet._lcom._common._jsp.__page_navigation(3024ecc8)>
<Dec 21, 2005 10:47:18 PM KST> <Warning> <Management> <BEA-141138> <Managed Server ofrserver is disconnected from the ad
min server. This may be either due to a managed server getting temporarily partitioned or the managed server process exi
ting.>
<GC(197): freeing class jsp_servlet._ofr._filter._jsp.__filterdetails(30252718)>
<GC(197): freeing class jsp_servlet._lcom._admin._jsp.__devtools(3040f898)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__devtoolslogin(3040f260)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__processdevtoolslogin(30411870)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__xmlcommmanagerimport(30413e58)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__processxmlcommmanagerimport(30414a88)>
<GC(197): unloaded and freed 8 classes>
<GC(197): GC cycle started Wed Dec 21 22:47:23 2005
<GC(197): freed 721499624 bytes, 70% free (754110928/1073674752), in 263157 ms>
<GC(197): mark: 248258 ms, sweep: 1857 ms, compact: 13042 ms>
<GC(197): refs: soft 0 (age >= 32), weak 0, final 27363, phantom 0>
<GC(197): moved 0 objects, 0 bytes, IC reason=14>
<GC(197): stop threads time: 1356, start threads time: 19>
<AF[196]: completed in 282883 ms>
Thanks,
Shanmuga perumal
[email protected]

I think you should be able to follow the same steps but whenever you come across Domain B in the instructions, just substitute the values for Domain A. Because it is the same domain you may not even have to go through some of the certificate steps. If you have questions I suggest you post them in the WLS Security forum.
WebLogic Server - Security

Security issue between weblogic server

Hello,
Here is security issue that we are facing.
Here is setup
Environment 1
Admin server say "env1admin"
Managed Weblogic Server say "env1managed"
We deployed an EJB called HelloEJB in env1managed server and this has an api
sayHello(). HelloClient is a client to HelloEJB.
S/w Weblogic 6.1 sp3
Environment 2
Admin server say "env2admin"
Managed Weblogic Server say "env2managed"
We deployed an EJB called ServiceEJB in env2managed server and this has an api
serviceRequest(). We use weblogic role based security and restrict access to this
api by user HelloEJB.
s/w Weblogic 6.1 sp3
Here is how the system works:
We start the env2admin, env2managed (ServiceEJB is which is a Stateless session
EJB deployed in env2Managed)
We start the env1admin and env1managed (HelloEJB(which is a Stateless session
EJB is deployed in env1Managed)
Test case:
1)HelloClient invokes HelloEJB api sayHello().
2)Now at this point in ejbCreate() at HelloEJB() end we get a reference to ServiceEJB
using Jndi and the context is never closed ). HelloEJB then calls serviceRequest()
api in ServiceEJB. Then gets back a response and then returns response to HelloClient.
Now if we repeat the above testcase.
After step1 in step2 HelloEJB though has all the permissions to invoke api on
ServiceEJB gets an SecurityException.
Question is why doe this happen. Only way HelloEJB can make api calls to serviceEJB
is by making a lookup() every single time. Which is very expensive. I looked at
documents what they say is leave the context open and never close it. Though I
am doing that I am getting this exception.
Any thoughts ?
Thanks in advance,
Vijay

Here are the details of exception stack trace:
java.rmi.AccessException: Security violation: insufficient permission to access
method; nested exception is:
java.lang.SecurityException: Security violation: insufficient permission
to access method
java.lang.SecurityException: Security violation: insufficient permission to access
method
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:92)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at service.ServiceBean_nr0s19_EOImpl.sendServiceRequest(ServiceBean_nr0s19_EOImpl.java:25)
at service.ServiceBean_nr0s19_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
Vijay
"Vijay" <[email protected]> wrote:
>
Hello,
Here is security issue that we are facing.
Here is setup
Environment 1
Admin server say "env1admin"
Managed Weblogic Server say "env1managed"
We deployed an EJB called HelloEJB in env1managed server and this has
an api
sayHello(). HelloClient is a client to HelloEJB.
S/w Weblogic 6.1 sp3
Environment 2
Admin server say "env2admin"
Managed Weblogic Server say "env2managed"
We deployed an EJB called ServiceEJB in env2managed server and this has
an api
serviceRequest(). We use weblogic role based security and restrict access
to this
api by user HelloEJB.
s/w Weblogic 6.1 sp3
Here is how the system works:
We start the env2admin, env2managed (ServiceEJB is which is a Stateless
session
EJB deployed in env2Managed)
We start the env1admin and env1managed (HelloEJB(which is a Stateless
session
EJB is deployed in env1Managed)
Test case:
1)HelloClient invokes HelloEJB api sayHello().
2)Now at this point in ejbCreate() at HelloEJB() end we get a reference
to ServiceEJB
using Jndi and the context is never closed ). HelloEJB then calls serviceRequest()
api in ServiceEJB. Then gets back a response and then returns response
to HelloClient.
Now if we repeat the above testcase.
After step1 in step2 HelloEJB though has all the permissions to invoke
api on
ServiceEJB gets an SecurityException.
Question is why doe this happen. Only way HelloEJB can make api calls
to serviceEJB
is by making a lookup() every single time. Which is very expensive. I
looked at
documents what they say is leave the context open and never close it.
Though I
am doing that I am getting this exception.
Any thoughts ?
Thanks in advance,
Vijay

Weblogic server proxy issues with twitter4j api

I am using weblogic 10.3.4 using twitter4j Api running behind the proxy. I am not sure why I am getting this error. I do have the proxy name,port number, userid and password set in the twiiter4j api. The same code works fine for me in tomcat behind proxy. When I was trying to migrate from tomcat to weblogic i am getting following error. Any help is really appreciated. I am not sure its the issue with weblogic
Thanks for the help
Vinoj
<Failed to communicate with proxy: tmsproxy.tms.toyota.com/80. Will try c
onnection stream.twitter.com/443 now.
weblogic.net.http.HttpUnauthorizedException: Proxy or Server Authentication Required
at weblogic.net.http.HttpURLConnection.getAuthInfo(HttpURLConnection.java:297)
at weblogic.net.http.HttpsClient.makeConnectionUsingProxy(HttpsClient.java:440)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:351)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:527)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:239)
Truncated. see log file for complete stacktrace
Dumping beanImpl -> ejbName map
weblogic.management.j2ee.mejb.MejbBean: Mejb
connect timed out
Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=944a924a or
http://www.google.co.jp/search?q=24fd66dc
TwitterException{exceptionCode=[944a924a-24fd66dc 944a924a-24fd66b2], statusCode=-1, message=null, code=-1, retryAfter=-1, rateLim
itStatus=null, version=3.0.4-SNAPSHOT(build: f34757f6d8512eca8028601d9de303e0173d8d42)}
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java:177)
at twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java:61)
at twitter4j.internal.http.HttpClientWrapper.post(HttpClientWrapper.java:98)
at twitter4j.TwitterStreamImpl.getFilterStream(TwitterStreamImpl.java:304)
at twitter4j.TwitterStreamImpl$7.getStream(TwitterStreamImpl.java:292)
at twitter4j.TwitterStreamImpl$TwitterStreamConsumer.run(TwitterStreamImpl.java:462)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at weblogic.net.http.HttpsClient.openWrappedSSLSocket(HttpsClient.java:565)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:287)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:364)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:527)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:239)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:255)
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java

Hi,
Has anybody got the solution like 64-bit libroxy or its source code to compile as 64-bit? I'm facing the same problem.

WebLogic 6.1 server hung issues

Our WebLogic 6.1 server hangs up around 12 times a day. We had this same issue
using WebLogic 5.1.
The hang ups started when we had some code changes and moved from a 8.1.7 oracle
database to using a 9.2 oracle database connecting using an oracle thin jdbc driver
on a sun solaris box.
Any ideas what might be causing our server to hang?
Thanks!
Deb

yes we are running on unix ..
we are running 2 weblogic instances but on different port...
one on 7001 and other on 7003 ...
and if one background process already running on 7001 ..then i think it is impossible for OS to assign this port to weblogic instance..
but we are facing problem in this way...that we start weblogic server ..it stared.and works ...for few hours..
and in between ...we find below error ...
<Oct 21, 2004 11:22:13 AM IST> <Notice> <WebLogicServer> <Reopening listen socket on port 7001>
<Oct 21, 2004 11:22:13 AM IST> <Critical> <WebLogicServer> <Failed to listen on port 7001, failure count: 64, failing for 1,098,337,347 seconds, java.net.BindException: Address already in use>
this error is not coming when we are starting weblogic server ...it is coming when weblogic server is running ...on port 7001...
i hope you get my point ...what is happing...
thanks..

I need to download the server runtime for BEA WEBLOGIC server

Hi ^^,
I am trying to create a web project in Eclipse WTP europa. I do not have the bea weblogic server installed on my desktop. My organization has issues running it locally. I need to first create a project and then create a war and then deploy it on server.
I am going through the tutorial at the following website:
http://www.eclipse.org/webtools/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html
It says "To do this tutorial you will need a server runtime that is supported by WTP"
Also "During web application development, we will need a server runtime environment to test, debug and run our project".
Hence I need the link where I can download the server runtime for bea weblogic server.
T&R,
Prashant

Crossposted over all places:
[http://forums.sun.com/thread.jspa?threadID=5347690]
[http://forums.sun.com/thread.jspa?threadID=5348001]
[http://forums.sun.com/thread.jspa?threadID=5348002]
Don't crosspost. It's very rude.

Issue with Weblogic services in Linux OBIEE 11G

Hello All,
I have a OBI 11G set up on a linux OS.I am facing a issue with weblogic service.
Whenever I am trying to start the Admin server from command line using its .sh , it is starting successfully.
But whenever I am closing that Linux session or coming out of the Admin server log , this service is getting stopped on its own.
OBI is working perfectly when that Linux session and Admin server log is intact, but as soon as i close either of them Admin server shut itself down.
Please any help on this will be appreciated.
Thanks,
Bhavnesh

Hi Bhavnesh.
Try this way and let me know the outcome.
nohup ./startWeblogic.sh -Dweblogic.management.username=Username -Dweblogic.management.password=password & tail -f nohup.out
Mark if helps,
Thanks,

WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file

WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log file
 We are using WLS 7.0.4 - One of JMS connection factory setting in admin console we selected "Server Affinity" options.
 We see this messages appear in Weblogic log file,
 ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster> <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000123> <Conflict start: You tried to bi
 nd an object under the name sbetrmi2 in the JNDI tree. The object you have bound from liberatenode2.dc2.adelp
 hia.com is non clusterable and you have tried to bind more than once from two or more servers. Such objects ca
 n only deployed from one server.>
 and then,
 ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster> <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <000125> <Conflict Resolved: sbetrmi2 for
 the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2 in the JNDI tree.>
 Should we use 'load balancing option' instead of 'server affinity' ?
 Any thuoghts?
 Thanks in adv.
 Vijay

Test Reply
 <Vijay Kumar> wrote in message news:[email protected]..
 > WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
 > file
 >
 > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
 > console we selected "Server Affinity" options.
 >
 > We see this messages appear in Weblogic log file,
 > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
 > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000123> <Conflict start: You tried to bi
 > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
 > bound from liberatenode2.dc2.adelp
 > hia.com is non clusterable and you have tried to bind more than once from
 > two or more servers. Such objects ca
 > n only deployed from one server.>
 >
 > and then,
 > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
 > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000125> <Conflict Resolved: sbetrmi2 for
 > the object from liberatenode5.dc2.adelphia.com under the bind name
 > sbetrmi2 in the JNDI tree.>
 >
 >
 > Should we use 'load balancing option' instead of 'server affinity' ?
 >
 > Any thuoghts?
 >
 > Thanks in adv.
 > Vijay

[URGENT] UTF-8 issue in weblogic SOAP implementation

Guyz,
I am finding an issue with **weblogic.xml.saaj.MessageFactoryImpl** SOAP message factory mplementation class of weblogic. When it creates SOAP from inputstream which includes portuguese characters it does not recognise those characters.
Any idea how to solve this issue?
Chinmoy

Will this really be a problem? UTF-8 is a superset of US-ASCII, I believe,
 so there should be no incompatability. This is assuming that you will only
 be sending latin characters in the form, since the recieving end can only
 accept latin characters. If this is NOT true, then they need to use UTF-8.
 Otherwise, I would test it and see what happens.
 "Volker Mader" <[email protected]> wrote in message
 news:3d3326c4$[email protected]..
 >
 > Hi there,
 >
 > can anybody help me.
 > I have a webapp in wls 6.1 sp2. All of the web is utf-8 based, so i set
 the charset
 > in the page-directive and the html content type to utf-8. Also I set the
 <input-charset>
 > Tag in weblogic.xml to utf-8 for context "/".
 > Problem: I want to send a from out of this webapp to another server which
 serves
 > a iso-8859-1 based application.
 > How can I do that?
 >
 > Thanks for help
 > Volker

Sun Identity Server 6.1 with Weblogic 8.1 sp2

Hi,
I've installed the IS 6.1 with WLS 8.1 sp2 and the agent 2.1.1 and followed the agent configuration guide to configure the xml files (web.xml and weblogic.xml) and agent authenticator.
When I login to the restricted resource, the browser is redirected to the IS server login page. After login, the browser is redirected back to the resource with 403 forbidden.
Is there any step missing? Should I additional add some policy in the IS console? .....
Clive

I have just installed Sun Identity Server 6.2 with WebLogic 8.1 SP3 and am experiencing the same results. Have you resolved this issue in your environment? We are evaluating Portal Server running on a BEA WLS Container and thus do not have Sun Support on the Identity Server Component of this configuration.

Java.rmi.server.ExportException: while stopping weblogic Managed server

Hello,
I am getting the below error while I try to stop the weblogic managed server from the stop script in the server. I am able to do it thru the console.
the weblogic version is 9.23.
-server -Xms1536m -Xmx1536m
Stopping Weblogic Server...
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9990; nested exception is:
java.net.BindException: Address already in use
I am a newbie , so anyone could help me figure out the things I need to check so that I can troubleshoot the issue?
thanks in advance.

Are you using a custom script or <domain>/bin/stopManagedWebLogic.sh ?
The msg you've informed seems to be an error that happens when you try to start a managed server that is trying to use a port that is already in use.

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

I need the server run time for weblogic server. Please help

Hi ^^,
I am trying to create a web project in Eclipse WTP europa. I do not have the bea weblogic server installed on my desktop. My organization has issues running it locally. I need to first create a project and then create a war and then deploy it on server.
I am going through the tutorial at the following website:
http://www.eclipse.org/webtools/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html
It says "To do this tutorial you will need a server runtime that is supported by WTP"
Also "During web application development, we will need a server runtime environment to test, debug and run our project".
Hence I need the link where I can download the server runtime for bea weblogic server.
I have tried to download the tomcat runtime from the following location:
http://apr.apache.org/download.cgi
But tomcat is not accepting it as a server runtime, pls help...

Crossposted over all places:
[http://forums.sun.com/thread.jspa?threadID=5347690]
[http://forums.sun.com/thread.jspa?threadID=5348001]
[http://forums.sun.com/thread.jspa?threadID=5348002]
Don't crosspost. It's very rude.

WLS 7.0.4 - JMS connection Factory for RMI queues - server affinity issues help pls

We are using WLS 7.0.4 - One of JMS connection factory setting in admin
console we selected "Server Affinity" options.
We see this messages appear in Weblogic log file,
####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
<liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000123> <Conflict start: You tried to bi
nd an object under the name sbetrmi2 in the JNDI tree. The object you have
bound from liberatenode2.dc2.adelp
hia.com is non clusterable and you have tried to bind more than once from
two or more servers. Such objects ca
n only deployed from one server.>
and then,
####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
<liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000125> <Conflict Resolved: sbetrmi2 for
the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2
in the JNDI tree.>
Should we use 'load balancing option' instead of 'server affinity' ?
Any thuoghts?
Thanks in adv.
Vijay

Test Reply
 <Vijay Kumar> wrote in message news:[email protected]..
 > WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
 > file
 >
 > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
 > console we selected "Server Affinity" options.
 >
 > We see this messages appear in Weblogic log file,
 > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
 > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000123> <Conflict start: You tried to bi
 > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
 > bound from liberatenode2.dc2.adelp
 > hia.com is non clusterable and you have tried to bind more than once from
 > two or more servers. Such objects ca
 > n only deployed from one server.>
 >
 > and then,
 > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
 > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000125> <Conflict Resolved: sbetrmi2 for
 > the object from liberatenode5.dc2.adelphia.com under the bind name
 > sbetrmi2 in the JNDI tree.>
 >
 >
 > Should we use 'load balancing option' instead of 'server affinity' ?
 >
 > Any thuoghts?
 >
 > Thanks in adv.
 > Vijay

Whole server migarion issue in weblogic

Similar Messages

Maybe you are looking for