Register WebGate 11gR2 in cluster
Registering Webgate for a single OAM server works fine.
How to register webgate in case of cluster with two or more OAM servers? eg in the Request.xml file has IP and port for OAM server. For single node IP of OAM server is given.
In case of two or more OAM servers, what is the IP address to be given? Anyone done is this before, please share your configuration (remote registration via rreg tool)
Hi,
The registration request is sent to the OAM Admin Server, not the managed server(s). In a clustered environment, the agent will be automatically configured to communicate with all managed servers in the cluster.
Regards,
Colin
Similar Messages
-
We are evaluating the Cluster features of WebLogic and got a eval
license for the Cluster Support.
I am running a default cluster (mycluster) using the default Multicast
address (237.0.0.1) and am seeing
some strange behaviour/errors.
Would appreciate some asistance in this matter.
Our Environment
I created directory in a shared file system to host the cluster.
(h:\kkanth\weblogic)
Created the mycluster directory and other directories as recommended in
the Administrator's guide.
I have two WL Servers (asera190 and asera162) with permanent IP
addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
I'm using a NES proxy on asera190 with the plugin for WL specified in
obj.conf alongwith the other parameters.
I'm able to have both the servers join to cluster mycluster and the WL
Admin Console does display a tree that depicts the cluster as well as
servers in it (server61 and server70). The individual server directories
are being created in h:\kkanth\weblogic\mycluster directory with the
appropriate access.log and weblogic.log files.
When a browser attempts to access a URL such as
http://asera190/weblogic/snoop it does return the proper response, but
all requests are processed by asera162 which is listed first in the
obj.conf. Opening multiple sessions does not cause the requests to be
sent to asera190 which is the second server in the cluster. When
asera162 is shutdown and removed from the cluster, I hoped that
subsequent requests would go to asera190. However , depending on the
origin of the request, different errors were thrown. If I try to access
http://asera190/weblogic/snoop from a browser on asera190, I get an
error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
from asera162 cause "Failure at line 706 of file proxy.cpp".
I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
directory as well as the obj.conf file in the ....\config\ directory of
asera190.
We are running NES 3.5.1 and have setup proxy35.dll appropriately.
weblogic.properties
# THE WEBLOGIC PROPERTIES FILE
# This file, which conforms to the java.util.Properties file
# definition, configures your WebLogic products. You cannot run
# WebLogic Server without setting required configuration properties in
this
# file. Required properties are marked and appear first in the file.
# Details on each entry and important information about configuration
# and security are documented on our website. Please go to:
# http://www.weblogic.com/docs45/admindocs/properties.html
# for full instructions on how to edit this file.
# You do not need to include properties in this file unless you want to
# change the default, embedded property. Some properties on the
# T3AdminProps page are not listed here because the default property
# is being used. You can change the default by adding the property and
# its value to this file.
# You cannot set weblogic.system.home in this file, since the WebLogic
Server
# must know where home is in order to retrieve this file. You can
# change WebLogic home on the command line when you start the
# WebLogic Server.
# CLUSTER USERS: Note that the (shared) per-cluster properties file
should
# contain most all of the properties in this file. The only properties
# that potentially belong in a per-server properties file for a server
# running in a cluster are the registration (startup class) of pinned
# RMI objects, and a few tuning properties that may be different for
# servers in the cluster, depending upon hardware and memory. If you use
# a per-server properties file, please REMOVE all properties except
those
# that are specifically required in the per-server properties file. You
# can find specific notes on clusters by searching through this file for
# "CLUSTER USERS".
# The way this file is organized:
# Core properties (includes REQUIRED and RECOMMENDED)
# Core system properties
# Core security-related properties
# Core security-related properties for SSL
# Core HTTPD administrative properties
# Optional properties
# Administrator properties
# System properties
# System startup files
# System shutdown files
# Security-related properties for Workspaces
# Jolt for WebLogic properties
# WebLogic Enterprise Connectivity properties
# WebLogic File properties
# WebLogic JMS demo properties
# WebLogic RMI demo properties
# WebLogic EJB demo properties
# WebLogic ZAC demo properties
# HTTPD administrative properties
# WebLogic JDBC driver properties
# WebLogic JDBC connection pool management
# WebLogic demo connection pool
# WebLogic HTTP Servlet properties
# Proxy servlet registration
# Classpath servlet registration
# File servlet registration
# ServerSideInclude servlet registration
# PageCompileServlet (used by JHTML)
# JSPServlet (used by JSP)
# ServletServlet registration
# Servlet reload properties
# Servlet ACLs
# WebLogic JHTML properties
# User-written and demo servlet registrations
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first
time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for
connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8
characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=kaykayka
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs45/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# OPTIONAL PROPERTIES
# These properties affect the behavior of the WebLogic Server.
# You only need to set these properties if you want
# to change the default setting, which is the property shown.
# ADMINISTRATOR PROPERTIES
# Administrator properties are optional information properties,
# particularly useful for clusters.
#weblogic.administrator.location=3355 California Drive, West Hampshire,
CA 94104
#weblogic.administrator.name=Joe Administrator
#weblogic.administrator.phone=1 415 555 1234
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
# If you prefer to access the most recent help pages, you can do so
online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system
defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related
properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# Other system startup files for use with VisiBroker
# Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
# You must have installed Visigenic 2.5 for use with
# the WebLogic Server before you uncomment these properties
#weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
#weblogic.system.startupArgs.dovisi=\
# clientName=T3Client Manager,\
# connName=T3Connection Manager
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise
Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this
file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statefulSession.Trader to
# try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular
installation:
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/cluster_ejb.jar, \
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_isModified.jar, \
# d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
# d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
# d:/weblogic/myserver/ejb_sequence_oracle.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlets used by the EJB basic examples beanManaged and
# containerManaged. Uncomment to use:
#weblogic.httpd.register.beanManaged=\
# examples.ejb.basic.beanManaged.Servlet
#weblogic.httpd.register.containerManaged=\
# examples.ejb.basic.containerManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
"jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server
called
# "DEMO." If more than 4 connections are opened, after 15 minutes,
unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection poolsTry the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
Init fn="load-types" mime-types="mime.types"
Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
Init fn="wl-init"
Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
\"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
<Object name="tg" ppath="*/weblogic/*">
Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
</Object>
<Object name="default">
NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
PathCheck fn="nt-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index" index-names="index.html,home.html"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
AddLog fn="flex-log" name="access"
</Object>
<Object ppath="/usr/suitespot/docs/.perf">
Service fn="service-dump"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
Hope this helps
Krishna Kanth wrote:
> We are evaluating the Cluster features of WebLogic and got a eval
> license for the Cluster Support.
> I am running a default cluster (mycluster) using the default Multicast
> address (237.0.0.1) and am seeing
> some strange behaviour/errors.
> Would appreciate some asistance in this matter.
>
> Our Environment
> ----------------
>
> I created directory in a shared file system to host the cluster.
> (h:\kkanth\weblogic)
> Created the mycluster directory and other directories as recommended in
> the Administrator's guide.
>
> I have two WL Servers (asera190 and asera162) with permanent IP
> addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
> I'm using a NES proxy on asera190 with the plugin for WL specified in
> obj.conf alongwith the other parameters.
>
> I'm able to have both the servers join to cluster mycluster and the WL
> Admin Console does display a tree that depicts the cluster as well as
> servers in it (server61 and server70). The individual server directories
> are being created in h:\kkanth\weblogic\mycluster directory with the
> appropriate access.log and weblogic.log files.
>
> When a browser attempts to access a URL such as
>
> http://asera190/weblogic/snoop it does return the proper response, but
> all requests are processed by asera162 which is listed first in the
> obj.conf. Opening multiple sessions does not cause the requests to be
> sent to asera190 which is the second server in the cluster. When
> asera162 is shutdown and removed from the cluster, I hoped that
> subsequent requests would go to asera190. However , depending on the
> origin of the request, different errors were thrown. If I try to access
> http://asera190/weblogic/snoop from a browser on asera190, I get an
> error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
> from asera162 cause "Failure at line 706 of file proxy.cpp".
>
> I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
> directory as well as the obj.conf file in the ....\config\ directory of
> asera190.
>
> We are running NES 3.5.1 and have setup proxy35.dll appropriately.
>
> weblogic.properties
> *********
> # THE WEBLOGIC PROPERTIES FILE
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # This file, which conforms to the java.util.Properties file
> # definition, configures your WebLogic products. You cannot run
> # WebLogic Server without setting required configuration properties in
> this
> # file. Required properties are marked and appear first in the file.
> #
> # Details on each entry and important information about configuration
> # and security are documented on our website. Please go to:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # for full instructions on how to edit this file.
> #
> # You do not need to include properties in this file unless you want to
> # change the default, embedded property. Some properties on the
> # T3AdminProps page are not listed here because the default property
> # is being used. You can change the default by adding the property and
> # its value to this file.
> #
> # You cannot set weblogic.system.home in this file, since the WebLogic
> Server
> # must know where home is in order to retrieve this file. You can
> # change WebLogic home on the command line when you start the
> # WebLogic Server.
> #
> # CLUSTER USERS: Note that the (shared) per-cluster properties file
> should
> # contain most all of the properties in this file. The only properties
> # that potentially belong in a per-server properties file for a server
> # running in a cluster are the registration (startup class) of pinned
> # RMI objects, and a few tuning properties that may be different for
> # servers in the cluster, depending upon hardware and memory. If you use
>
> # a per-server properties file, please REMOVE all properties except
> those
> # that are specifically required in the per-server properties file. You
> # can find specific notes on clusters by searching through this file for
>
> # "CLUSTER USERS".
> #
> # -------------------------------------------------
> # The way this file is organized:
> # Core properties (includes REQUIRED and RECOMMENDED)
> # Core system properties
> # Core security-related properties
> # Core security-related properties for SSL
> # Core HTTPD administrative properties
> #
> # Optional properties
> # Administrator properties
> # System properties
> # System startup files
> # System shutdown files
> # Security-related properties for Workspaces
> # Jolt for WebLogic properties
> # WebLogic Enterprise Connectivity properties
> # WebLogic File properties
> # WebLogic JMS demo properties
> # WebLogic RMI demo properties
> # WebLogic EJB demo properties
> # WebLogic ZAC demo properties
> # HTTPD administrative properties
> # WebLogic JDBC driver properties
> # WebLogic JDBC connection pool management
> # WebLogic demo connection pool
> # WebLogic HTTP Servlet properties
> # Proxy servlet registration
> # Classpath servlet registration
> # File servlet registration
> # ServerSideInclude servlet registration
> # PageCompileServlet (used by JHTML)
> # JSPServlet (used by JSP)
> # ServletServlet registration
> # Servlet reload properties
> # Servlet ACLs
> # WebLogic JHTML properties
> # User-written and demo servlet registrations
> # -------------------------------------------------
>
> #################################################################
> # CORE PROPERTIES
> # -------------------------------------------------
> # You should set these before you start the WebLogic Server the first
> time.
> # If you need more instructions on individual properties in this
> # section, check the same section in the Optional Properties, where
> # we've left the long explanations. Or, better yet, go to our
> # website and read all about properties, at:
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #################################################################
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SYSTEM PROPERTIES
> # -------------------------------------------------
> # TCP/IP port number at which the WebLogic Server listens for
> connections
> weblogic.system.listenPort=7001
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES
> # -------------------------------------------------
> # Read important information about security at:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # REQUIRED: The system password MUST be set in order to start the
> # WebLogic Server. This password is case-sensitive, at least 8
> characters.
> # The username for the privileged user is ALWAYS "system".
> # This username and password also includes httpd access (see
> # HTTPD properties below).
> weblogic.password.system=kaykayka
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # RECOMMEND Set to 'everyone' if HTTPD is enabled
> weblogic.allow.execute.weblogic.servlet=everyone
> # Set individual ACLs to restrict access to HTTP-related resources,
> # such as the Administration servlets.
> # To make your own servlets generally available, follow this
> # pattern (provide a weblogic.allow.execute) for your packages and
> # set ACLs as appropriate.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES FOR SSL
> # ------------------------------------------------
> # Read important information about SSL at:
> #
> # http://www.weblogic.com/docs45/classdocs/API_secure.html
> #
> # Enable SSL
> # (default if property not defined is false)
> weblogic.security.ssl.enable=true
> #
> # SSL listen port
> weblogic.system.SSLListenPort=7002
>
> # Servlets for SSL
> # ------------------------------------------------
> # Authentication servlet for creating tokens for applets
> weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
>
> # Limits number of unclaimed stored tokens
> weblogic.security.certificateCacheSize=3
> # Capture CA root of client servlet
> weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
>
> # Certificates for SSL
> # ------------------------------------------------
> # Name of acceptable CA roots
> # For client authentication change value to a valid .pem file
> #weblogic.security.clientRootCA=SecureServerCA.pem
> #
> # Server certificates for SSL
> # ------------------------------------------------
> weblogic.security.certificate.server=democert.pem
> weblogic.security.key.server=demokey.pem
> weblogic.security.certificate.authority=ca.pem
>
> # registration for certificate generator servlet
> weblogic.httpd.register.Certificate=utils.certificate
> weblogic.allow.execute.weblogic.servlet.Certificate=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # True permits the HTTPD to run (default)
> # Uncomment this property to disable HTTPD
> #weblogic.httpd.enable=false
> #
> # If authentication is required, add username/password for each user
> # who will be included in an ACL, as in this commented-out example:
> #weblogic.password.peter=#8gjsL4*
>
> #################################################################
> # OPTIONAL PROPERTIES
> # ------------------------------------------------
> # These properties affect the behavior of the WebLogic Server.
> # You only need to set these properties if you want
> # to change the default setting, which is the property shown.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # ADMINISTRATOR PROPERTIES
> # ------------------------------------------------
> # Administrator properties are optional information properties,
> # particularly useful for clusters.
> #weblogic.administrator.location=3355 California Drive, West Hampshire,
> CA 94104
> #weblogic.administrator.name=Joe Administrator
> #weblogic.administrator.phone=1 415 555 1234
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM PROPERTIES
> # ------------------------------------------------
> # System properties in this section are set to system defaults
>
> # Performance pack. The shared library must be accessible from your
> # PATH (NT) or from your shared library path (UNIX; the name of the
> # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
> weblogic.system.nativeIO.enable=true
>
> # Outputs logging information to the console as well as to the log file
> weblogic.system.enableConsole=true
>
> # Sets the directory or URL for the WebLogic Admin help pages
> # The help pages are shipped in the "docs/adminhelp" directory, in the
> # default document root in public_html
> weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
>
> # If you prefer to access the most recent help pages, you can do so
> online
> # by commenting out the previous property and uncommenting this one:
> #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
>
> # Properties for tuning the server's performance
> # ------------------------------------------------
> # Number of WebLogic Server execute threads.
> weblogic.system.executeThreadCount=15
>
> # Other optional system properties
> # ------------------------------------------------
> # Limits size of weblogic.log (in K) and versions old log
> weblogic.system.maxLogFileSize=1024
>
> # Adjust minimum length of password
> weblogic.system.minPasswordLen=8
>
> # UNIX only: If running on port 80 on UNIX, enable the setUID program
> #weblogic.system.enableSetUID=false
>
> # UNIX only: Unprivileged user to setUID to after starting up
> # WebLogic Server on port 80
> #weblogic.system.nonPrivUser=nobody
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CLUSTER-SPECIFIC PROPERTIES
> # ------------------------------------------------
> # Cluster-specific properties in this section are set to system
> defaults.
> # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
>
> # in the per-cluster properties file ONLY.
> #
> # Time-to-live (number of hops) for the cluster's multicast messages
> # (default 1, range 1-255).
> #weblogic.cluster.multicastTTL=1
> #
> # Sets the load-balancing algorithm to be used between
> # replicated services if none is specified. If not specified,
> # round-robin is used.
> #weblogic.cluster.defaultLoadAlgorithm=round-robin
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SERVER-SPECIFIC CLUSTER PROPERTIES
> # ------------------------------------------------
> # Cluster-related properties in this section are set to system defaults.
>
> # CLUSTER USERS: Note that these server-specific cluster-related
> properties
> # should be set in the per-server properties file ONLY.
> #
> # Sets the weight of the individual server for the weight-based
> load-balancing.
> # Range is 0 - 100.
> # Larger numbers increase the amount of traffic routed to this server.
> #weblogic.system.weight=100
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM STARTUP FILES - Examples
> # ------------------------------------------------
> # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
> # objects should be registered in the per-server properties file.
> # All other startup classes should be registered in the per-cluster
> # properties file.
> #
> # For more info on writing and using startup file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a startup class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.startupClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the startup class
> #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/StartupQuery.java
> #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
> #weblogic.system.startupArgs.doquery=\
> # query=select * from emp,\
> # db=jdbc:weblogic:pool:demoPool
> #
> # Other system startup files for use with VisiBroker
> # ------------------------------------------------
> # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
> # You must have installed Visigenic 2.5 for use with
> # the WebLogic Server before you uncomment these properties
> #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
>
> #weblogic.system.startupArgs.dovisi=\
> # clientName=T3Client Manager,\
> # connName=T3Connection Manager
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM SHUTDOWN FILES - Examples
> # ------------------------------------------------
> # For more info on writing and using shutdown file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a shutdown class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the shutdown class
> #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/ShutdownTest.java
> #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
>
> #weblogic.system.shutdownArgs.ShutdownTest=\
> # outfile=c:/temp/shutdown.log
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SECURITY-RELATED PROPERTIES FOR WORKSPACES
> # ------------------------------------------------
> # For backward compatibility, the following entries disable Access
> # Control on Workspaces
> weblogic.allow.read.weblogic.workspace=everyone
> weblogic.allow.write.weblogic.workspace=everyone
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # JOLT FOR WEBLOGIC PROPERTIES
> # ------------------------------------------------
> # These properties configure a BEA Jolt connection pool for use with
> # the simpapp and bankapp examples, and register a servlet for use with
> # with the simpapp example. The default server address provided here
> # points to a public TUXEDO server that is hosted by BEA for use with
> # this example.
> #
> # Servlet registration for simpapp example:
> # ------------------------------------------------
> #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
>
> #
> # Pool creation and cleanup
> # note this example is set up to work with the public
> # demo TUXEDO server available from BEA's website:
> # ------------------------------------------------
> #weblogic.system.startupClass.demojoltpoolStart=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
> #weblogic.system.startupArgs.demojoltpoolStart=\
> # poolname=demojoltpool,\
> # appaddrlist=//beademo1.beasys.com:8000,\
> # failoverlist=//beademo1.beasys.com:8000,\
> # minpoolsize=1,\
> # maxpoolsize=3
> #
> #weblogic.system.shutdownClass.demojoltpoolStop=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
> #weblogic.system.shutdownArgs.demojoltpoolStop=\
> # poolname=demojoltpool
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
> # ------------------------------------------------
> # The registrations enable a BEA IIOP connection pool and
> # register servlets for use with the simpapp and university examples.
> # Configure for your environment and uncomment to use.
> # Uncommenting these properties requires WebLogic Enterprise
> Connectivity
> # and an operating WebLogic Enterprise Server.
> #
> # Servlet registration for simpapp servlet example
> # ------------------------------------------------
> #weblogic.httpd.register.SimpappServlet=\
> # examples.wlec.servlets.simpapp.SimpappServlet
> #
> #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
> #
> # Servlet registration for simpapp EJB example
> # (You'll need to add the wlec_ejb_simpapp.jar to the
> # weblogic.ejb.deploy property in this file.)
> # --------------------------------------------
> #weblogic.httpd.register.ejbSimpappServlet=\
> # examples.wlec.ejb.simpapp.ejbSimpappServlet
> #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
> #
> # Pool creation and cleanup for the simpapp example
> # -------------------------------------------------
> #weblogic.CORBA.connectionPool.simplepool=\
> # appaddrlist=//wlehost:2468,\
> # failoverlist=//wlehost:2468,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # domainname=simpapp
> #
> # Servlet registration for university Servlet example:
> # ---------------------------------------------------
> #weblogic.httpd.register.UniversityServlet=\
> # examples.wlec.servlets.university.UniversityServlet
> #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
> #
> # Pool creation and cleanup for the University example:
> # ----------------------------------------------------
> #weblogic.CORBA.connectionPool.Univpool=\
> # appaddrlist=//wlehost:2498,\
> # failoverlist=//wlehost:2498,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # apppassword=wlepassword,\
> # domainname=university
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC FILE PROPERTIES
> # ------------------------------------------------
> # Maps a volume name to a path, for client file read/write
> #weblogic.io.fileSystem.[volumeName]=[fullPathName]
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC JMS DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL JMS deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # You set up a JDBC connection pool if you want persistent messages
> # (including durable subscriptions). To use JMS and EJBs in the same
> # transaction, both must use the same JDBC connection pool. Uncomment
> # the following property to use the default JDBC connection pool
> # 'demo', which is defined in the Demo connection pool section of this
> file.
> #
> #weblogic.jms.connectionPool=demoPool
> #
> # The JMS Webshare example demonstrates how the ClientID for a
> # durable subscriber is configured in the connection factory:
> #
> #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
> #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
>
> #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
> #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
> #
> # The JMS trader example shows how to use JMS with an EJB. In addition
> # to uncommenting the following properties, you must also set up and
> # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
> # try out this JMS example:
> #
> #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
> #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
> #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
> #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
> #
> # Registers the underlying servlet
> #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
> #
> # These properties are used with the ServerReceive JMS example,
> # which demonstrates how to establish a JMS message consumer
> # in a startup class:
> #
> #weblogic.system.startupClass.serverReceive=\
> # examples.jms.startup.ServerReceive
> #weblogic.system.startupArgs.serverReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
> #
> # These properties are used with the PoolReceive JMS example,
> # which demonstrates how to establish a pool of JMS message consumers
> # in a startup class:
> #weblogic.system.startupClass.poolReceive=\
> # examples.jms.startup.PoolReceive
> #weblogic.system.startupArgs.poolReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC RMI DEMO PROPERTIES
> # ------------------------------------------------
> # CLUSTER USERS: Note that pinned RMI objects should be registered
> # in the per-server properties file ONLY. All other RMI startup
> # classes should be registered in the per-cluster properties file.
> #
> # Remote classes registered at startup after the pattern:
> #weblogic.system.startupClass.[virtualName]=[fullPackageName]
> #
> # These examples can be compiled to see RMI in action. Uncomment to use:
>
> #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
>
> #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC EJB DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL EJB deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # See WebLogic Demo Connection Pool below for a connection pool
> # to use with these examples.
> #
> # Deploys EJBeans. Uncomment the appropriate lines below and
> # modify DBMS-related info and paths to match your particular
> installation:
> #weblogic.ejb.deploy=\
> # d:/weblogic/myserver/cluster_ejb.jar, \
> # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
> # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
>
> # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
> # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
> # d:/weblogic/myserver/ejb_subclass.jar, \
> # d:/weblogic/myserver/jolt_ejb_bankapp.jar
> #
> # Servlets used by the EJB basic examples beanManaged and
> # containerManaged. Uncomment to use:
> #weblogic.httpd.register.beanManaged=\
> # examples.ejb.basic.beanManaged.Servlet
> #weblogic.httpd.register.containerManaged=\
> # examples.ejb.basic.containerManaged.Servlet
> #
> # Add a list of users (set the password with
> weblogic.password.[username]=XXX)
> # to set an ACL for this servlet:
> #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
> #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
>
> #weblogic.password.user1=user1Password
> #weblogic.password.user2=user2Password
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ZAC DEMO PROPERTIES
> # -------------------------------------------------
> # These registrations enable the ZAC Publish Wizard.
> #
> weblogic.zac.enable=true
> #
> # Set the publish root for a WebLogic Server. Edit and
> # uncomment to use
> #
> #weblogic.zac.publishRoot=d:/weblogic/zac
> #
> # Set an ACL for each package you publish. The [name] is
> # the "Package name" you assign in the ZAC Publish Wizard.
> # Publish a package, edit this property, and uncomment to use.
> #weblogic.allow.read.weblogic.zac.[name]=[user list]
> #weblogic.allow.write.weblogic.zac.[name]=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # Enables logging of HTTPD info in common log format and
> # sets the log file name (default is "access.log" in "myserver")
> weblogic.httpd.enableLogFile=true
> weblogic.httpd.logFileName=access.log
>
> # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
> weblogic.httpd.enableEvents=false
>
> # Enables HTTP sessions
> weblogic.httpd.session.enable=true
>
> # Sets an optional cookie name. The default name is "WebLogicSession".
> # Prior to version 4.0, the default was "TengahSession". To make
> # this backward compatible with cookies generated from previous
> # installations, you should set this property to "TengahSession".
> # Uncomment t -
Unstable session replication in a HA cluster (CF10)
Hi,
We have tried to create a HA cluster with requests being distributed round robin to N instances of coldfusion, we are NOT using sticky sessions as we are replication session state to all cf instances. What we are seing is that all is fine with low to moderate load, however under heavy load and at random times the replication fails and leads to things in session scope not working. This manifests in users not being able to login to our application (we store a token in session scope to store logged in status).
Again key point, under low to moderate load it all works fine, users are directed to random nodes in the cluster and their session is picked up fine as the session is distributed to all nodes,so pretty confident config is right.
Linux servers using CF10 with update 12 applied. Also running is fusion reactor 5.04 on all instances. Each instance has a 64GB heap, Java 7.0.15 (latest certified).
Firstly apache setup.
workers.properties
worker.list=balancer, jkstatus
worker.jkstatus.type=status
worker.balancer.type=lb
worker.balancer.balance_workers=cfusion_master,cfusion_slave2,cfusion_slave1
worker.balancer.method=R
worker.balancer.sticky_session=False
worker.balancer.ping_mode=A
worker.cfusion_master.type=ajp13
worker.cfusion_master.host=localhost
worker.cfusion_master.port=8012
worker.cfusion_master.max_reuse_connections=250
worker.cfusion_master.lbfactor=100
worker.cfusion_slave2.reference=worker.cfusion_master
worker.cfusion_slave2.port=8014
worker.cfusion_slave1.reference=worker.cfusion_master
worker.cfusion_slave1.port=8013
Now the server.xml from 2 nodes (as an example if I run a 2 node cluster)
One of the configs from a server in the cluster
<Server port="8007" shutdown="SHUTDOWN">
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on">
</Listener>
<Listener className="org.apache.catalina.core.JasperListener">
</Listener>
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener">
</Listener>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener">
</Listener>
<GlobalNamingResources>
<Resource description="User database that can be updated and saved" name="UserDatabase" pathname="conf/tomcat-users.xml" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" type="org.apache.catalina.UserDatabase" auth="Container">
</Resource>
</GlobalNamingResources>
<Service name="Catalina">
<Executor name="tomcatThreadPool" minSpareThreads="4" maxThreads="150" namePrefix="catalina-exec-">
</Executor>
<Connector port="8012" protocol="AJP/1.3" connectionTimeout="600000" redirectPort="8445" tomcatAuthentication="false">
</Connector>
<Engine jvmRoute="cfusion" name="Catalina" defaultHost="localhost">
<Realm className="org.apache.catalina.realm.LockOutRealm">
<Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase">
</Realm>
</Realm>
<Host name="localhost" autoDeploy="false" unpackWARs="true" appBase="webapps">
<Valve pattern="%h %l %u %t "%r" %s %b" directory="logs" prefix="localhost_access_log." className="org.apache.catalina.valves.AccessLogValve" suffix=".txt" resolveHosts="false">
</Valve>
</Host>
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8">
<Manager notifyListenersOnReplication="true" expireSessionsOnShutdown="false" className="org.apache.catalina.ha.session.DeltaManager">
</Manager>
<Channel className="org.apache.catalina.tribes.group.GroupChannel">
<Membership port="45564" dropTime="3000" address="228.0.0.4" className="org.apache.catalina.tribes.membership.McastService" frequency="500">
</Membership>
<Receiver port="4001" autoBind="100" address="auto" selectorTimeout="5000" maxThreads="6" className="org.apache.catalina.tribes.transport.nio.NioReceiver">
</Receiver>
<Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
<Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender">
</Transport>
</Sender>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector">
</Interceptor>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor">
</Interceptor>
</Channel>
<Valve className="org.apache.catalina.ha.tcp.ReplicationValve" filter="">
</Valve>
<Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve">
</Valve>
<ClusterListener className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener">
</ClusterListener>
<ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener">
</ClusterListener>
</Cluster>
</Engine>
<Connector port="8499" protocol="org.apache.coyote.http11.Http11NioProtocol" connectionTimeout="20000" redirectPort="8443" executor="tomcatThreadPool">
</Connector>
</Service>
</Server>
Config from one of the other nodes
<Server port="8008" shutdown="SHUTDOWN">
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on">
</Listener>
<Listener className="org.apache.catalina.core.JasperListener">
</Listener>
<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener">
</Listener>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener">
</Listener>
<GlobalNamingResources>
<Resource description="User database that can be updated and saved" name="UserDatabase" pathname="conf/tomcat-users.xml" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" type="org.apache.catalina.UserDatabase" auth="Container">
</Resource>
</GlobalNamingResources>
<Service name="Catalina">
<Executor name="tomcatThreadPool" minSpareThreads="4" maxThreads="150" namePrefix="catalina-exec-">
</Executor>
<Connector port="8013" protocol="AJP/1.3" connectionTimeout="600000" redirectPort="8446" tomcatAuthentication="false">
</Connector>
<Engine jvmRoute="cfusion" name="Catalina" defaultHost="localhost">
<Realm className="org.apache.catalina.realm.LockOutRealm">
<Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase">
</Realm>
</Realm>
<Host name="localhost" autoDeploy="false" unpackWARs="true" appBase="webapps">
<Valve pattern="%h %l %u %t "%r" %s %b" directory="logs" prefix="localhost_access_log." className="org.apache.catalina.valves.AccessLogValve" suffix=".txt" resolveHosts="false">
</Valve>
</Host>
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8">
<Manager notifyListenersOnReplication="true" expireSessionsOnShutdown="false" className="org.apache.catalina.ha.session.DeltaManager">
</Manager>
<Channel className="org.apache.catalina.tribes.group.GroupChannel">
<Membership port="45564" dropTime="3000" address="228.0.0.4" className="org.apache.catalina.tribes.membership.McastService" frequency="500">
</Membership>
<Receiver port="4002" autoBind="100" address="auto" selectorTimeout="5000" maxThreads="6" className="org.apache.catalina.tribes.transport.nio.NioReceiver">
</Receiver>
<Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
<Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender">
</Transport>
</Sender>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector">
</Interceptor>
<Interceptor className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor">
</Interceptor>
</Channel>
<Valve className="org.apache.catalina.ha.tcp.ReplicationValve" filter="">
</Valve>
<Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve">
</Valve>
<ClusterListener className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener">
</ClusterListener>
<ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener">
</ClusterListener>
</Cluster>
</Engine>
<Connector port="8500" protocol="org.apache.coyote.http11.Http11NioProtocol" connectionTimeout="20000" redirectPort="8443" executor="tomcatThreadPool">
</Connector>
</Service>
</Server>
So what do i see in the logs?. Well sometimes I see exceptions like this
Mar 05, 2014 9:55:19 PM org.apache.catalina.ha.session.DeltaManager messageReceived
SEVERE: Manager [localhost#/]: Unable to receive message through TCP channel
java.lang.IllegalStateException: removeAttribute: Session already invalidated
at org.apache.catalina.ha.session.DeltaSession.removeAttribute(DeltaSession.java:617)
at org.apache.catalina.ha.session.DeltaRequest.execute(DeltaRequest.java:171)
at org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaManager.java:1347)
at org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager.java:1293)
at org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaManager.java:1014)
at org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(ClusterSessionListe ner.java:92)
at org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:897)
at org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:878)
at org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChannel.java:278)
at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelIntercepto rBase.java:84)
at org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailu reDetector.java:113)
at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelIntercepto rBase.java:84)
at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelIntercepto rBase.java:84)
at org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.ja va:253)
at org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:2 87)
at org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTa sk.java:212)
at org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:1 01)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
I'm unsure why this happens as tribes uses certified mesaging so it should have resent right?, in any case I believe I can change it so messages are not sent asynchronously, should sort this out.
I see (good) messages like this
Mar 05, 2014 9:42:19 PM org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Register manager localhost#/ to cluster element Engine with name Catalina
Mar 05, 2014 9:42:19 PM org.apache.catalina.ha.session.DeltaManager startInternal
INFO: Starting clustering manager at localhost#/
Mar 05, 2014 9:42:19 PM org.apache.catalina.ha.session.DeltaManager getAllClusterSessions
INFO: Manager [localhost#/], requesting session state from org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 128, 50}:4001,{192, 168, 128, 50},4001, alive=68824148, securePort=-1, UDP Port=-1, id={123 126 89 39 96 -59 69 8 -113 79 51 122 25 108 -11 -110 }, payload={}, command={}, domain={}, ]. This operation will timeout if no session state has been received within 60 seconds.
Mar 05, 2014 9:42:20 PM org.apache.catalina.ha.session.DeltaManager waitForSendAllSessions
INFO: Manager [localhost#/]; session state send at 3/5/14 9:42 PM received in 929 ms.
Mar 05, 2014 9:42:20 PM org.apache.catalina.ha.session.JvmRouteBinderValve startInternal
INFO: JvmRouteBinderValve started
So session state dies appear to be flying around the cluster, I do nightly restarts of some of the nodes due to another issue I have with an ever growing heap (separate issue), interestingly I also see nodes leave and join the cluster, again this is good (shows the multicast is working, and also that replication should be working).
Mar 05, 2014 2:30:16 AM org.apache.catalina.tribes.group.interceptors.TcpFailureDetector memberDisappeared
INFO: Verification complete. Member disappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 128, 50}:4001,{192, 168, 128, 50},4001, alive=18629101, securePort=-1, UDP Port=-1, id={-2 65 10 -79 53 -75 76 52 -99 63 -90 -120 34 -89 -14 100 }, payload={}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={}, ]]
Mar 05, 2014 2:30:16 AM org.apache.catalina.ha.tcp.SimpleTcpCluster memberDisappeared
INFO: Received member disappeared:org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 128, 50}:4001,{192, 168, 128, 50},4001, alive=18629101, securePort=-1, UDP Port=-1, id={-2 65 10 -79 53 -75 76 52 -99 63 -90 -120 34 -89 -14 100 }, payload={}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={}, ]
Mar 05, 2014 2:35:16 AM org.apache.catalina.ha.tcp.SimpleTcpCluster memberAdded
INFO: Replication member added:org.apache.catalina.tribes.membership.MemberImpl[tcp://{192, 168, 128, 50}:4001,{192, 168, 128, 50},4001, alive=1083, securePort=-1, UDP Port=-1, id={123 126 89 39 96 -59 69 8 -113 79 51 122 25 108 -11 -110 }, payload={}, command={}, domain={}, ]
So stuck now on how to proceed, to establish why at random times the replication fails, leading to cluster collapse. Could it be the size of the session?, I have a few CFCs stuffed into session scope, but perhaps when the load is high there is too many?. Things fail even with a cluster of 2 on one server, initially I had a 8 node cluster on 2 separate machines but when it failed it rolled it back to a cluster of 2 instances on the one server to see if that was stable (its not 100% which is what I need).
Any advice, points gratefully received.So Lynux, that’s an interesting sounding solution. Would be great if it made some difference for Guitsboy. We’ll see. I notice that you say you’ve not yet tried it, though, and fair enough. Thanks for offering it.
But I’m curious: did you ever resolve your original problem? And if not, hopefully you saw the note I just wrote to Guitsboy, asking him something that may well interest you if you still have your problem. On rereading this thread, from back in April, I’ve also had some new thoughts come to mind which I’ll share, if it may help either of you, or others with this seeming same issue.
To remind readers who may not want to review the whole thread, you had said originally that “all is fine with low to moderate load, however under heavy load and at random times the replication fails“, and that this failure “manifests in users not being able to login to our application (we store a token in session scope to store logged in status)”. Then it seems you may have concluded that things were down to the error you were seeing in the logs:
Mar 05, 2014 9:55:19 PM org.apache.catalina.ha.session.DeltaManager messageReceived
SEVERE: Manager : Unable to receive message through TCP channel
java.lang.IllegalStateException: removeAttribute: Session already invalidated
And now guitsboy reports seeing the same error.
But here’s the thing that came to mind for me tonight as I read this: you know, there can be a lot of other reasons that users can feel that they “lose their session”, even without using clustering and replication.
There are issues related sometimes to folks having duplicate session tokens (which can happen for various reasons, including perhaps ones in your code, and maybe only when people visit pages in a certain pattern, so that it happens only occasionally and not always).
Then there is an issue that can arise if you are supporting both http and https requests, where Tomcat (not CF) balks at that (see http://www.petefreitag.com/item/817.cfm, and though he shows a solution in IIS you should be able to implement a similar one in mod_rewrite if that was indeed perhaps your issue).
So I’d be curious if either of you may be in a position to have a failing client use any sort of client tool (like Chrome’s dev tools, or Firebug or Firefox’s new builtin tools, or IE’s f12 dev tools) to watch the communication between the client and the server, and especially to watch the cookies being sent. You guys both mention using jsessionid. Are they the same cookie value on each request? And/or are there more than jsessionid? I’ve seen it happen. There could be differences in the domain property reported for the cookie, the httponly property, the secure property, and so on. And you really do want to view the value sent from the client to the server, because if you view the cookie scope on the server a) it may show values set ON the server rather than sent TO the server, and b) it won’t show these additional cookie properties that were in play on the client. CF only sees the cookie name and value.
I’ve helped many people find out that this was the reason for the seeming session loss (and sometimes it was not all requests by all clients but perhaps only some requests for some clients, all on the same server). At least if this is the crux of the problem, you can then tackle WHY it’s happening. There can be many reasons, from code to configuration, so I won’t belabor them now.
But if either of you may be able to confirm this, perhaps we can help you both get a little closer to a real explanation and solution for your problem. Again, I’m just guessing a bit based on what you’ve written. I realize it may be that none of this is the problem and you have hit some other real unrelated bug. But I really feel confident that you ought to try to check this out first, as it’s indeed been the crux of problems for others, without respect to clustering. It seems worth ruling out, so that you don’t get misled chasing the problem on the assumption that it is about clustering.
As always, hope that helps.
/charlie -
Seek help: How to make XI 3.0 BOE Cluster
My aim to make cluster is:
1. High availability, that is, when Server A is down, Server B can take place.
2. Let job servers on Server B to join Server A's large load publication task to improve performance.
My Steps:
1. New install BOE XI 3.0 on both Server A and Server B, both win2003 sp2 OS.
2. Server A is installed first, so it use an Oracle DB as the CMS repository. And Server B is pointed to the same repository.
I want to change Server B's file store's location after adding Server B's CMS into cluster, however, I found when logging into the CMC, I can only see all servers from server A, and Server B's cms in the server List, and no Server B's node in CCM's SIA list.
The problem is :
1. Server B's cms is stoped, (it's enabled), and I tried manully start it, but failed.
2. How can I let job servers on Server B to register into the new cluster, I don't find any place to see them.
In XI R2, I can add -ns newCluster into servers' command line.
I think, I don't follow the right steps, any one can help?
Thanks in advance!
JennieClustering XI3 servers is explained in detail starting on page 266 in the Admin Guide.
In a nut shell, you will need to delete your current SIA on server B, then add a new SIA in CCM pointing it to the same CMS DB SIA on server A is using.
Once you see new node in CMC, you can clone all servers from node A to node B, which will keep all the server settings they have in A. Including FRS location. -
Using dbca to extend RAC cluster error
Hi all,
I'm trying to extend my 11gR2 RAC cluster (POC) using the Oracle documentation (http://vishalgupta.com/oracle/docs/Database11.2/rac.112/e10718/adddelunix.htm). I've already cloned and extended Clusterware and ASM (Grid Infrastructure) to the new node, as well as cloned the RAC database software to the new node. When I run the below statement to have dbca extend add a new instance on the node for the RAC I get the error shown:
CMD:
$ORACLE_HOME/bin/dbca -silent -addInstance -nodeList newnode13 -gdbName racdb -instanceName racdb4 -sysDBAUserName sys
-sysDBAPassword manager123
ERROR:
cat racdb0.log
"Adding instance" operation on the admin managed database racdb requires instance configured on local node. There is no instance configured on the local node "newnode13".
I set ORACLE_HOME before running dbca, and I've also tried setting ORACLE_SID to both racdb4 and racdb, no change. My environment is below, any help is appreciated.
OS: SLES 11.1
Database: 11.2.0.1
Existing Nodes: node01,node02, node03
New Node: newnode13
DB Name: racdb
Instances: racdb1, racdb2, racdb3
New Instance: racdb4
Thanks.Silly me, I was running the command from the new node instead of an existing node. I guess it was a rough weekend after all. Thanks all!
-
Adding a Cluster Hyper-V 2012 into SCVMM 2012 SP1 causes a Crash in VMMService.exe
I'm trying to register a 5 node Cluster into SCVMM 2012 SP1 host, but when the registration job is running the SCVMMService crashes and then registration becomes inconsistent.
this is the error log from App Event Viewer:
Event 1000: Application Error:
Faulting application name: vmmservice.exe, version: 3.1.6011.0, time stamp: 0x50aaba3f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fae7615fdb
Faulting process id: 0x1050
Faulting application start time: 0x01ce1b77516905f8
Faulting application path: F:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\Bin\vmmservice.exe
Faulting module path: unknown
Report Id: a450c591-876d-11e2-93fe-00155d011c01
Faulting package full name:
Faulting package-relative application ID:
Event 1026: .Net Runtime
Application: vmmservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at Microsoft.VirtualManager.Engine.RefreshDriver`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].RefreshThreadFunction(System.Object)
at Microsoft.VirtualManager.Utils.Multithreading.ThrottledThreadPool+<>c__DisplayClass3.<ScheduleNextThread>b__2(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Faulting application name: vmmservice.exe, version: 3.1.6011.0, time stamp: 0x50aaba3f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fae7615fdb
Faulting process id: 0x1050
Faulting application start time: 0x01ce1b77516905f8
Faulting application path: F:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\Bin\vmmservice.exe
Faulting module path: unknown
Report Id: a450c591-876d-11e2-93fe-00155d011c01
Faulting package full name:
Faulting package-relative application ID:
Its important that this error occurs only with my Windows 2012 Datacenter cluster, with a Windows 2008R2 Cluster doesn't, and works perfect the registration.
What's going wrong???
Thank you very much.Dear All,
I can't find a solution for this error....
Faulting application name: vmmservice.exe, version: 3.1.6011.0, time stamp: 0x50aaba3fFaulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6Exception code: 0xe0434352Fault offset: 0x000000000003811cFaulting process id: 0x1070Faulting application start time: 0x01cf1b5d8e2c9535Faulting application path: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\Bin\vmmservice.exeFaulting module path: C:\Windows\system32\KERNELBASE.dllReport Id: e35b1662-8750-11e3-9417-00155d00795aFaulting package full name: Faulting package-relative application ID:
I've a cluster with 2 nodes.
1) The NIC teaming is configured in the cluster (the VMM is installed in one VM in the cluster).
2) yes
3) yes
Thanks a lot for the replies!
SF -
Multiple access codes in single uc cluster
Dears,
I have a customer will migrade from Nortel to Cisco.
Nortel PBX has internal access codes between sites. If site A need to call site B should dail access code + Internal extenstion.
We will install one cisco UC cluster v9.1 and they need to use the same access code and extesions.
Please advise.
BR,
HaythamThanks Janse for your reply.
I have only one Custer and all phones registered to the same uc cluster no Trunks no Gateways.
In Nortel the Design is Distributed soo there are access codes between sites but in cisco its centralized all phones registered to the same cluster.
Is there any posibility to use access codes between internal phones registed on the same cucm server.
Thanks
HS -
Problems with Deploying WLI Tutorial App to a cluster
I'm using Weblogic 8.1 SP3 and have built the app (steps 1-5) listed below:
Tutorial
The app works fine in Workshop and even works fine deployed to a simple one-server WLI configuration once the 2 JMS Queus and required db tables are created manually. The problem is in deploying to a cluster. No error messages are generated but when loading the test page (http://localhost:8001/Tutorial_Process_ApplicationWeb/requestquote/RequestQuote.jpd?.EXPLORE=.TEST
) I do not get the same results as when loading in the single server setting (Note the port number is the port that my clustered managed server is running on). Basically the multi-tab page that loads in the one-server scenario only comes up as one tab - the Overview tab. None of the other tabs allowing you to test the web services are available.
I tried to cheat it by saving the SOAP test page from the working version and posting the form to the non-working version - but all that was returned was the Overview page. I suspect the issue is JTX-related but I am new the Weblogic so I'm somewhat lost.
Any help appreciated. I can be reached at [email protected]I am getting the following output from the Admin Server when I attempt to access the JPD process:
<19-Nov-2004 13:58:56 o'clock GMT> <Error> <JTA> <BEA-110412> <Xid=BEA1-0046F2A8360F0D4CF282(73146307),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=500,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=committed,assigned=cgServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@429b2ce,re-Registered = false),SCInfo[integration-cluster-xa-changed+cgServer]=(state=committed)) completed heuristically: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: No connection associated with xid = BEA1-0046F2A8360F0D4CF282-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C)) -
Oracle clusterware for 11gR2 ?
We are trying to install 11gR2 for RAC on Linux and have downloaded the Enterprise Edition 11gR2 binary. But cannot see any clusterware software to download. Like in 10gR2, you have to down both database and clusterware for RAC install. Should the 11gR2 have include the clusterware in the DB enterprise edition binary?
Thanks in advance,No. The 11gR2's cluster s/w is called Grid Infrastructure and is a separate download. The s/w includes the new CRS s/w stack and ASM - and note that the installation recommendations include installing it as a separate o/s user (with new o/s groups) and not as the traditional oracle o/s user (the user grid is recommended). This way there is better physical separation of the cluster s/w stack from the RBMS s/w stack and makes monitoring and management and administration a lot easier.
-
Whenever cluster boots zpool disappers
Dear Community,
I have following setup
Oracle Solaris 10 -> 5.10 Generic_147147-26 sun4v sparc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
Oracle Solaris Cluster 3.3u2 for Solaris 10 sparc
Oracle Solaris Cluster Geographic Edition 3.3u2 for Solaris 10 sparc
I installed Oracle Solaris 10 with ZFS
I have a pool called db for mount point /oradata
When ever I reboot/power cycle my cluster ZFS pool disappears
because of that clster cannot start properly so oracle database resource/group fails
Everytime I reboot/power cycle I have to do manually
zpool import db
clrg online ora-rg
what can be the reason?
the only thing I know
db zpool, the pool is imported with ora-has resource which I created as shown below (with Zpools option)
# /usr/cluster/bin/clresourcegroup create ora-rg
# /usr/cluster/bin/clresourcetype register SUNW.HAStoragePlus
# /usr/cluster/bin/clresource create -g ora-rg -t SUNW.HAStoragePlus -p Zpools=db ora-has
---> under working conditions zpool status
# zpool status db
pool: db
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
db ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t2d0 ONLINE 0 0 0
c0t3d0 ONLINE 0 0 0
errors: No known data errors
---> boot log:
Booting in cluster mode
impdneilab1 console login: Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1 (nodeid = 1) with votecount = 1 added.
Apr 21 17:12:24 impdneilab1 sendmail[642]: My unqualified host name (impdneilab1) unknown; sleeping for retry
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1: attempting to join cluster.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Cluster has reached quorum.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1 (nodeid = 1) is up; new incarnation number = 1429629142.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Cluster members: impdneilab1.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: node reconfiguration #1 completed.
Apr 21 17:12:24 impdneilab1 cl_runtime: NOTICE: CMM: Node impdneilab1: joined cluster.
Apr 21 17:12:24 impdneilab1 in.mpathd[262]: Successfully failed over from NIC nxge1 to NIC e1000g1
Apr 21 17:12:24 impdneilab1 in.mpathd[262]: Successfully failed over from NIC nxge0 to NIC e1000g0
obtaining access to all attached disksHello Juergen,
Thank you for your suggestion.
Yes I am running 2 single-node cluster communicating them via geo-edition.
Yes, c0t2d0 and c0t3d0 are local devices.
I understand that nofencing will allow to reach disks from outside of the cluster.
once we turn off fencing ZFS/OS will able to import them during boot.
Is this your theory?
nofencing
After checking for and removing any Persistent Group Reservation (PGR) keys, turns off fencing for the specified device or devices.
regards,
Halit -
CF 7 cluster does not respond to configuration changes
I am evaluating the clustering capabilities of CF 7 in order
to upgrade our current CF6 + ClusterCats cluster.
I installed CF7 (enterprise edition – multiserver) in
two physical servers (Win 2003). On each server I created one
instance of CF and successfully registered the remote instance on
each server. Then, I configured the cluster on the first server,
selecting the weighted random algorithm for load balance and
session replication. Then, I used the webserver configuration tool
to bind the cluster to each IIS server.
The cluster worked properly, balancing the load between the
two cf instances, but when trying to find a way to temporally
restrict the load on one server for maintenance purposes I found
that the cluster does not respond to cluster configuration changes.
I changed the load to 0-100% using the coldfusion administrator
interface but it did not work. The cluster still sends requests to
the “restricted” instance. I even eliminated that
instance from the list of instances that integrates the cluster,
but it did not affect the behavior of the cluster. The eliminated
instance still serves request from the cluster. I even eliminated
the remote instance register and nothing… the cluster still
balancing the load between the two instances that originally
integrated the cluster.
I do not understand how this is supposed to work. Does the
cluster configuration interface works only when creating the
cluster? When the changes in the cluster configuration performed
from the CF admin interface should be reflected by the behavior of
the cluster? What is the recommended procedure to temporally
restrict one instance from the cluster without stopping the
service?
I appreciate your help
EduardoThanks for the information Jochem. I am afraid that these are
not good news. If I have to restart the webserver in order to
change the load balance, some requests in progress could be lost.
My current configuration is composed by two physical severs,
each one running a web server and a coldfusion instance. We balance
the load between both webservers using hardware load balancing.
This is the procedure that I have to follow in order restrict one
instance without loosing any request:
1.- Change server weight using Coldfusion admin interface
2.- Configure hardware load balance to restrict server 1
3.- Restart webserver at server 1
4.- Configure hardware load balance to enable server 1 and
restrict server 2
5.- Restart webserver at server 2
6.- Configure hardware load balance to enable server 2
A similar procedure should be followed in order to enable the
restricted instance. I know that I can do it for 2 servers; but,
how is it handled in larger clusters? Is there a better procedure
to restrict one instance without missing requests?
Eduardo -
Change cluster node's hostname
Just install a 4 node RAC cluster with 11gR2 infrastructure (cluster + asm), 10g RAC and 11g RAC database. Then customer told us to change the cluster node IP and hostname.
According to metalink (220970.1), it requires to reinstall the cluster.
Wondering is there any alternate way to rename cluster node's IP/hostname?Hi user5544520,
as far as I know it is not supported to change your hostname with CRS.
You will have to remove the node from the cluster.
Change hostname and do other necessary changes.
Add node to the cluster.
There are lots of documentation available.
Look at the following:
http://www.pythian.com/news/482/changing-hostnames-in-oracle-rac/In above mentioned blog they say:
If you are brave enough, there is another way to do this.
It’s not described anywhere on the Metalink, but there are no major hacks needed to implement it.
The idea is to simply re-run the configuration of CRS (including re-formatting OCR and voting disks) and re-create the CRS resources after that.
Obviously, this is not an online operation and the whole cluster is down for the duration of rename.Hope this helps.
Edited by: user11150436 on Oct 29, 2010 4:09 PM -
How to install Oracle 11.2.0.4.0 Rac Database on Grid Infrastructure 12.1.0.2.0 (Windows 2012 R2)
Hi all.
This is the scenario:
I have a 2 node cluster Microsoft Windows 2012 R2 x86_64, the nodes are part of domain.
Installed Oracle 12cR1 (12.1.0.2.0) as follows:
Installation done using domain administrator named "installoracle" that has been EXPLICIT promoted to local administrator in both nodes.
One domain user named "oracle12c" with no administrator privileges neither in the domain or nodes.
Installation, after a lot of customization in the OS of the nodes, has gone ok, perfect indeed, not even a warning during runinstaller execution.
All services and resources are up & running, I have rebooted nodes and all comes back ok in place. In windows services I can see some services started with "oracle12c" user, and all windows groups: DBA, SYSKM, etc, has been created.
Now I have to install Oracle RAC database in 11gR2 version (11.2.0.4.0) to accomplish with application requirements.
So, I execute runInstaller (setup.exe) logged as administrator via domain administrator "installoracle" (the one that was able to do the smooth 12c GI installation) and the gui comes with out problems, but at 4th screen the one in which you have to choose what kind of installation you want to do (Single, RAC or RoN) I select RAC option, the gui returns error: crs is not running in the local node...
Finally, in order to deliver some database 11.2.0.4.0 for my customer, I try to do installation of SW for Single Node, I did using "installoracle". The sw has been installed in one of the nodes. Then I have created a database and I have stored datafiles in ASM (this ASM is part of 12c clusterware) and also register the 11gR2 single instance database in the Grid Infrastructure listener
So, whats next??? Why is this behavior??? I did similar installations in Linux/Solaris with no issue (well as everyone can imagine, always there are some issues, but when solved you got GI in 12c and databases in the release that you want 12c, 11g, 10g...)
Any clue?
Thanks in advance!!
Best Regards!!To go back to old version (without changing compatible parameter), you can perform downgrade.
Instructions are available at
How to Downgrade from Database 11.2 to Previous Release (Includes 11.2.0.4 - 11.2.0.1) (Doc ID 883335.1)
In this case you will having all the data file including the new one.
But remember database may not be in the same status as before (Before upgrade). it may have invalid objects of higher version after downgrade.
Downgrade is applicable only to successfully upgraded databases. In case upgrade faced some issue, do not try downgrade there.
Your second approach it not correct. Note that each datafile header will have db version. We can not open database in normal mode when header version and binary versions are different. -
Need help adding services to clusrter
I'm trying to add two new services to an existing 2 node 11Gr2 RAC cluster. I want to use them for application partitioning. I want some apps to always connect to node 1 and others to always connect to node 2, unless a node is down in which case I want them all to go to the surviving node.
I added both new service names to both instances with - ALTER SYSTEM SET SERVICE_NAMES ='...,service1,service2' scope=both sid='*';
I created 2 new service names with - srvctl add service -d dbname -s servicename -r "InstName1" -a "InstName2". For the 2nd new service I reversed preferredInstName and otherInstName.
I enabled the services with - srvctl enable service -d dbname -s "service1,service2".
I started the services with - srvctl start service -d dbname -s "service1,service2".
I tested the new service names with - sqlplus user/password@scanName:1521/serviceN (where N is 1 or 2).
My problem is that it's not always connecting me to the preferred instance. Sometimes it does and sometimes it doesn't. What did I do wrong?
I also noticed that if I run - srvctl status service -d dbname - it does not contain the last line that I usually see which says "Service is enabled on instances:"
If I run - srvctl status service -d dbname -s service1 - it only shows it running on one instance (the preferred one). Sam thing with service2.In addition to not adding the services with ALTER SYSTEM you should also try lsnrctl status on all your scan listeners to check if the service gets registered against all listeners correctly
bjoern -
Does SCAN redirect to node-IP or node-VIP?
I have a 2 node 11gR2 RAC cluster with both SCAN and node VIPs configured. Users connect to the SCAN address. The SCAN listener then redirects connections to the node listener. Does it redirect to the node listener via the node's address or the node's VIP address?
Here's why I'm asking. I'm trying to troubleshoot a recurring problem where node2's VIPs (scan and node-vip) keep failing over to node1 every few weeks. CRS logs on node1 say that it thinks (incorrectly) that node2 is inaccesible so it failed over both VIPs (scan and node-vip). Within a minute or so however, node1 can see node2 again without anyone intervening.
Node2 however remains up the entire time and is running normally. Neither the node listener, database instance, or ASM instance show any indication of a problem in their logs.
On node2's database instance however, all sessions have dropped even though the instance remained up. If the SCAN listeners redirect directly to node2, I would not expect this to happen and I can pin the problem down to some network component (switch, NIC, etc). If SCAN redirects to the node-VIP then I would expect this and need to troubleshoot why node1 is incorrectly thinking node2 went down.Chuck1958 wrote:
Users connect to the SCAN address. The SCAN listener then redirects connections to the node listener. Does it redirect to the node listener via the node's address or the node's VIP address?That depends on
a) the service the user requests to be connected to
b) the registered hostnames of that service in the Listener
The SCAN listener is a remote listener, with which local listeners, register. The SCAN listener hands off/redirects connections based on what has been registered with it.
Also, a redirect is done using hostname and not dotted IP. Which means in exceptional circumstances, the client can use a hosts file with all static and virtual hostnames, referring to the same single (static or virtual) IP address.
Irrespective of what the SCAN Listener provides as hostname for the redirect, will in such a case be resolved, by the client, to the same IP address. Useful when troubleshooting, or when dealing with NAT firewalls.
Maybe you are looking for
-
Updates no longer work since I installed a trial of After Effects CC
Hi there I have a work computer with a fully licensed suite of CS6 apps. However I installed an trial of After Effects CC using my personal adobe id and now I cannot receive any updates. They fail immediately. I installed the latest Adobe Application
-
CD won't eject, doesn't appear on desktop, or in restart ... how do I?
Cannot eject the CD/DVD that is currently in the drive. It does not appear on the desktop, and when I restart the PowerBook pressing C it doesn't boot from it. The Media eject button doesn't display the eject hologram when I press it, and restarting
-
Nokia N8 user with PR 1.2 Hi all! I have a serious problem with my orange Nokia N8. I went to the beach for some time and phone was inside of the beach bag which had no direct contact with sun light exposure. There is 0.02 mm screen protector which
-
I am new to apple, when I try to drag and drop pictures from my camera to my portable hard drive it won't let me, why? I can copy anything almost to the mac hard drive but nothing to my portable???
-
Exception in Service Mapping Tool
Hello, I'm trying to use the Service Mapping Tool, but run into the exception "Parameter CH_CHANGE was not transferred" when executing the mapping. Does anyone have any insight why this might be? Regards Mattias