WLS Proxy in Cluster with Firewall
We are currently setting up a system that has a DMZ with Netscape inside
the DMZ proxying a WLS cluster that is behind the DMZ. When a cookie
based session is started a cookie is returned successfully, but it looks
like the physical address versuses a firewalled(NATed) address is placed
in the cookie. This in turn causes a failure on accessing the WLS
server. The firewall rejects future requests due to the use of the
physical instead of the NATed address.
If you understand the above and can help I would appreciate it.
Don Davis
D3, Inc.
Just wanted to let you know that everything is working with the latest patches for
4.5.1 and 5.1.
Thanks for the help
Don Davis
Prasad Peddada wrote:
> You might have to wait for the service pack. In the mean time I can give you a one
> of patch for testing.
>
> - Prasad
>
> Don Davis wrote:
>
> > Thanks for the help Prasad,
> >
> > I have migrated to 5.1 and set the DNSName property.
> >
> > I will let you know if all goes well.
> >
> > Don Davis
> >
> > Prasad Peddada wrote:
> >
> > > The problem has been fixed.
> > >
> > > Prasad Peddada wrote:
> > >
> > > > I assume you are using 451. WLS proxy with firewall was not behaving right.
> > > > Either you can wait for the next service pack or contact
> > > > [email protected] for a one of patch.
> > > >
> > > > Remember to set weblogic.system.DNSName in the properties file for each
> > > > server.
> > > >
> > > > - Prasad
> > > >
> > > > Don Davis wrote:
> > > >
> > > > > We are currently setting up a system that has a DMZ with Netscape inside
> > > > > the DMZ proxying a WLS cluster that is behind the DMZ. When a cookie
> > > > > based session is started a cookie is returned successfully, but it looks
> > > > > like the physical address versuses a firewalled(NATed) address is placed
> > > > > in the cookie. This in turn causes a failure on accessing the WLS
> > > > > server. The firewall rejects future requests due to the use of the
> > > > > physical instead of the NATed address.
> > > > >
> > > > > If you understand the above and can help I would appreciate it.
> > > > >
> > > > > Don Davis
> > > > > D3, Inc.
Similar Messages
-
Load balancing to a WLS 8.1 cluster with BigIP 9.0
We are experiencing a problem load balancing to our 8.1 cluster using f5's 1500 with BigIP 9.02. The cluster is not configured with any failover capability; we are have configured the BigIP with active cookie insertion persistence; all is well untill we take down one of the nodes in the cluster; any session associated with that node via the load balancer is bounced repeatedly between the two remaining nodes; the only solution appears to be to close all browser instances and open a new one. Has anyone experienced this behavior and have some suggestions ?
We are experiencing a problem load balancing to our 8.1 cluster using f5's 1500 with BigIP 9.02. The cluster is not configured with any failover capability; we are have configured the BigIP with active cookie insertion persistence; all is well untill we take down one of the nodes in the cluster; any session associated with that node via the load balancer is bounced repeatedly between the two remaining nodes; the only solution appears to be to close all browser instances and open a new one. Has anyone experienced this behavior and have some suggestions ?
-
Cluster with WLS 5.1 and WLS 8.1 servers?
hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
AlexanderYou can have it but not for fail-safe configuration.
It is not possible to have clusters with different
WLS versions especially between 5.1 & 8.1
Kumar
Alexander von Alkier wrote:
hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
Alexander -
Apache 2.0.35 httpd.conf issue with Win2k WLS 6.1sp2 Cluster
Hi,
Anybody has a Win2K Apache 2.0.35 httpd.conf that works
with a WLS 6.1sp2 Cluster?
I am getting errors like
"..Cannot load D:/Apache2.0.35/Apache2/modules/mod_wl_20.so into server: The
specified procedure could not be found."
Thanks,
-ad
you should post this question plugin newsgroup.
I will ask one of our plugin engineer to get back to you...
Kumar
Toly Dedes wrote:
> Hi,
> Anybody has a Win2K Apache 2.0.35 httpd.conf that works
> with a WLS 6.1sp2 Cluster?
> I am getting errors like
> "..Cannot load D:/Apache2.0.35/Apache2/modules/mod_wl_20.so into server: The
> specified procedure could not be found."
>
> Thanks,
> -ad
>
>
>
-
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 -
WebLogic Server - Firewall between proxy and cluster causes errors
Product Name and Version, including Service Pack (if any):
=============================================
Weblogic 5.1 , SP8
Platform (OS Version)
=================
Windows 2000 server,
JDK Version (if applicable)
=====================
Jdk1.2
Detailed Problem Description
======================
We have 2 weblogic servers in a cluser on two windows 2000 Servers
, NT01 and NT02.The webservers are in a DMZ behind the firewall
and there is a second firewall between the webserver and the weblogic
servers.The webserver is a Linux box , running Apache 1.3.9 with
the weblogic Plugin(LIN01).The per server weblogic.properties file
has the weblogic.system.DNSName=LIN01.
We still get errors on the console when we run our jsp/Servlet
application.The errors are listed below.Could you please help us
identify the problem
Thanks,
Gigen Thomas
Error Message/Stack Trace
=====================
ed Mar 21 16:38:50 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway.java
Wed Mar 21 16:38:52 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway_45_leftframe.java
Wed Mar 21 16:39:41 PST 2001:<I> <Cluster> Adding server -255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
to cluster view
Wed Mar 21 16:39:41 PST 2001:<E> <Kernel> ExecuteRequest failed.
java.io.NotSerializableException: com.sun.mail.imap.IMAPStore
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:845)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
at java.util.Hashtable.writeObject(Hashtable.java:738)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1585)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:907)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java:118)
at weblogic.servlet.internal.session.ReplicatedSession.writeExternal(ReplicatedSession.java:74)
at weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(WLObjectOutputStreamBase.java,
Compiled Code)
at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(WLObjectOutputStreamBase.java,
Compiled Code)
at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java,
Compiled Code)
at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(WLObjectOutputStreamBase.java,
Compiled Code)
at weblogic.rmi.extensions.AbstractOutputStream2.writeObject(AbstractOutputStream2.java:82)
at weblogic.rmi.extensions.AbstractOutputStream.writeObject(AbstractOutputStream.java:83)
at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:86)
at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
--------------- nested within: ------------------
weblogic.rmi.MarshalException: error marshalling arguments
- with nested exception:
[java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]
at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:90)
at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException: Undeclared checked
exception - with nested exception:
[weblogic.rmi.MarshalException: error marshalling arguments
- with nested exception:
[java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]]
at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:108)
at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
Compiled Code)
at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
Wed Mar 21 16:40:12 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner.java
Wed Mar 21 16:40:14 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_mainframe.java
Wed Mar 21 16:40:14 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_leftframe.java
Wed Mar 21 16:43:41 PST 2001:<I> <RJVM> Signaling peer -255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
gone: weblogic.rjvm.PeerGoneException:
- with nested exception:
[java.net.SocketException: Connection reset by peer]
Wed Mar 21 16:44:28 PST 2001:<I> <ServletContext-General> Generated
java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_dtlogout.java
Thanks Prasad.Your comments are very much appreciated !!!
Prasad Peddada <[email protected]> wrote:
>This has nothing to do with firewall.
>
>
>You have a non serializable object com.sun.mail.imap.IMAPStore
>in session.
>
>You cannot have non serializable objects in sessions when
>you are using inmemory replication/file/jdbc persistence.
>
>-- Prasad
>
>Gigen Thomas wrote:
>
>> Product Name and Version, including Service Pack (if
>any):
>> =============================================
>> Weblogic 5.1 , SP8
>>
>> Platform (OS Version)
>> =================
>> Windows 2000 server,
>>
>> JDK Version (if applicable)
>> =====================
>> Jdk1.2
>>
>> Detailed Problem Description
>> ======================
>> We have 2 weblogic servers in a cluser on two windows
>2000 Servers
>> , NT01 and NT02.The webservers are in a DMZ behind the
>firewall
>> and there is a second firewall between the webserver
>and the weblogic
>> servers.The webserver is a Linux box , running Apache
>1.3.9 with
>> the weblogic Plugin(LIN01).The per server weblogic.properties
>file
>> has the weblogic.system.DNSName=LIN01.
>>
>> We still get errors on the console when we run our jsp/Servlet
>> application.The errors are listed below.Could you please
>help us
>> identify the problem
>>
>> Thanks,
>> Gigen Thomas
>>
>> Error Message/Stack Trace
>> =====================
>> ed Mar 21 16:38:50 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway.java
>> Wed Mar 21 16:38:52 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway_45_leftframe.java
>> Wed Mar 21 16:39:41 PST 2001:<I> <Cluster> Adding server
>-255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
>> to cluster view
>> Wed Mar 21 16:39:41 PST 2001:<E> <Kernel> ExecuteRequest
>failed.
>> java.io.NotSerializableException: com.sun.mail.imap.IMAPStore
>> at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:845)
>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
>> at java.util.Hashtable.writeObject(Hashtable.java:738)
>> at java.lang.reflect.Method.invoke(Native Method)
>> at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1585)
>> at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:907)
>> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
>> at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java:118)
>> at weblogic.servlet.internal.session.ReplicatedSession.writeExternal(ReplicatedSession.java:74)
>> at weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(WLObjectOutputStreamBase.java,
>> Compiled Code)
>> at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(WLObjectOutputStreamBase.java,
>> Compiled Code)
>> at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java,
>> Compiled Code)
>> at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(WLObjectOutputStreamBase.java,
>> Compiled Code)
>> at weblogic.rmi.extensions.AbstractOutputStream2.writeObject(AbstractOutputStream2.java:82)
>> at weblogic.rmi.extensions.AbstractOutputStream.writeObject(AbstractOutputStream.java:83)
>> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:86)
>> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
>> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
>Compiled
>> Code)
>>
>> --------------- nested within: ------------------
>> weblogic.rmi.MarshalException: error marshalling arguments
>> - with nested exception:
>> [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]
>> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:90)
>> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
>> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
>Compiled
>> Code)
>> --------------- nested within: ------------------
>> weblogic.rmi.extensions.RemoteRuntimeException: Undeclared
>checked
>> exception - with nested exception:
>> [weblogic.rmi.MarshalException: error marshalling arguments
>> - with nested exception:
>> [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]]
>> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:108)
>> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
>> Compiled Code)
>> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
>> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
>Compiled
>> Code)
>>
>> Wed Mar 21 16:40:12 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner.java
>> Wed Mar 21 16:40:14 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_mainframe.java
>> Wed Mar 21 16:40:14 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_leftframe.java
>> Wed Mar 21 16:43:41 PST 2001:<I> <RJVM> Signaling peer
>-255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
>> gone: weblogic.rjvm.PeerGoneException:
>> - with nested exception:
>> [java.net.SocketException: Connection reset by peer]
>> Wed Mar 21 16:44:28 PST 2001:<I> <ServletContext-General>
>Generated
>> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_dtlogout.java
>
-
Round Robin was not happening for my cluster with WebLogic Proxy Plugin
Hi,
I configured my cluster with software load balancer, HTTPClusterServlet. By default,
it is load balancing with Round Robin Algorithm. That means one HTTP request
goes to server1, and the other HTTP request goes to server2. However, it is not
what I can see no matter for the requests in one HTTP session or not.
Say I open two browser, and log into my application with two different users,
one is "cyang", the other is "xpression". Then the HTTP request (for servlet/jsp)
from two browsers always go to the same server1, server2 is not invoked at all.
I did see one time, with only one session (one browser with "xPression" user log
in), the most requests go to server1, suddenly I am brough into log in page, then
I noticed that the request for "xPression" moved to server2 although server1 is
still alive. Therefore, at most, I can say it is "Random", rather than "Round
Robin".
What is the real meaning for HTTP servlet/jsp load balancing algorithm? Does
Round Robin mean request go to each server in turns? Does it have to be different
session or it can be within one session?
It should be sticky. If not, then bug / config error.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Carole Yang" <[email protected]> wrote in message
news:[email protected]...
>
> Thanks. Yeh, with two kind of browsers, I do see the request goes to
different
> servers.
>
> That goes back to the original question. Does "Round Robin" here fall
into the
> scope of a HTTP session. However, that is not always true for my tests.
Sometimes,
> HTTP request just randomly goes to another server while in the same HTTP
session.
> It is not sticky to one particular server during one session.
>
>
>
> --Carole
>
>
> "Cameron Purdy" <[email protected]> wrote:
> >Has to be different sessions to go to different machines.
> >
> >Best way to test is to run one session in IE and the other in Mozilla
> >or
> >Netscape.
> >
> >Peace,
> >
> >Cameron Purdy
> >Tangosol, Inc.
> >http://www.tangosol.com/coherence.jsp
> >Tangosol Coherence: Clustered Replicated Cache for Weblogic
> >
> >
> >"Carole Yang" <[email protected]> wrote in message
> >news:[email protected]...
> >>
> >> Hi,
> >>
> >> I configured my cluster with software load balancer,
HTTPClusterServlet.
> >By default,
> >> it is load balancing with Round Robin Algorithm. That means one HTTP
> >request
> >> goes to server1, and the other HTTP request goes to server2. However,
> >it
> >is not
> >> what I can see no matter for the requests in one HTTP session or not.
> >>
> >> Say I open two browser, and log into my application with two different
> >users,
> >> one is "cyang", the other is "xpression". Then the HTTP request (for
> >servlet/jsp)
> >> from two browsers always go to the same server1, server2 is not invoked
> >at
> >all.
> >>
> >> I did see one time, with only one session (one browser with "xPression"
> >user log
> >> in), the most requests go to server1, suddenly I am brough into log
> >in
> >page, then
> >> I noticed that the request for "xPression" moved to server2 although
> >server1 is
> >> still alive. Therefore, at most, I can say it is "Random", rather
> >than
> >"Round
> >> Robin".
> >>
> >> What is the real meaning for HTTP servlet/jsp load balancing algorithm?
> >Does
> >> Round Robin mean request go to each server in turns? Does it have
> >to be
> >different
> >> session or it can be within one session?
> >
> >
>
-
[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)
Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface. -
WLS 8.1 cluster startup scripts
Hi all,
I'm new to WebLogic and so am stumped by a configuration issue that should be normally be simple. I'm running WebLogic Server 8.1 SP6 on a Linux server and the Sun 1.4.2 JVM. A single cluster with 3 managed servers is set up, all servers being on the same machine.
I'm trying to get the JProfiler 4.3 agent running on one of these servers to investigate a memory leak issue. Using the WLS administration console (TestDomain > Clusters > TestCluster > TestServer1 > Configuration > RemoteStart), I have changed the server's startup arguments to add "-Xrunjprofiler" and "-Xbootclasspath".
For now I'm getting a "Error occurred during initialization of VM Could not find -Xrun library: libjprofiler.so" message when I start the server using the admin console. To solve this I need to modify the LD_LIBRARY_PATH for this particular server to include this library's dynamic dependencies.
The current question is: where should I be making these changes? I thought that the setEnv.sh, startManagedWebLogic.sh and startWebLogic.sh scripts in ~/domains/TestDomain/TestServer would be executed when starting this individual server, but changing them doesn't seem to have any impact. This means that other scripts are invoked, but which ones?
Thanks a bunch for your help.
Cheers,
GB
Edited by gbilodeau at 08/13/2007 10:59 AM
Edited by gbilodeau at 08/13/2007 10:59 AMHi,
Go through the following link and check whether you configured load balancing settings correctly or not.
http://e-docs.bea.com/wls/docs81/cluster/load_balancing.html
Regards
Anilkumar kari -
Can JMS topics and queues be clustered in a WLS 7.0 Cluster?
We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
node servers. Two nodes have been clustered. We are at the point where we
need to configure JMS. Has any one implemented JMS in WLS 7 clustered
environment? What are the things to watch out when clustering JMS? Can JMS
topics and queues be clustered?
TIA for any helpful hints and comments.
Regards
"Karim Ali" <[email protected]> wrote:
>> Has any one implemented JMS in WLS 7 clustered
>> environment?
I'm currently working on a project with WLS 7 here at work, involving
the implementation of BEA's JMS Cluster. So far, I really haven't had
many hiccups.
"Karim Ali" <[email protected]> wrote:
>> What are the things to watch out when clustering JMS?
At least in WLS 7, the biggest thing that stands out is the lack of
automatic failover. Also, Message Paging -- make sure you configure
paging high/low thresholds. Or, if you don't wish for it to occur but
can't stop the server (very common these days with SLAs), set that
byte/message high threshold to a very large number (correct me if I'm
wrong, but I believe BEA recommends 2^63 -1).
"Karim Ali" <[email protected]> wrote:
>> Can JMS topics and queues be clustered?
Well, since Topics and Queues are extensions of the
javax.jms.Destination interface, the answer is: Yes!
(SIDE NOTE: most people usually refer to them as a [JMS] "destination"
-- it avoids a lot of conceptual baggage and plus, less typing!)
You'll probably want to see this section of BEA's e-docs:
http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
later,
Brian J. Mitchell
BEA Systems Administrator
TRX
Atlanta, GA
email: [email protected]
office: 404-327-7238
mobile: 678-283-6530
-
Apache in front of WLS in a cluster
hi all,
I have some doubts about apache and wls in a cluster. We have 2 Apache server
(installed on 2 different hosts) in front
of a clustered WLS 6.1. Now my doubt is: who will take care of authentication,
Apache or WLS?
In other words as the 2 instances of Apache don't know about each other (they
are chosen with DNS-round robin), will the
authentication be done twice? or it's possible to handle authentication on the
application
server rather ? if so, where the Cookie that identifies the session will be kept?
Tanks a lot
Francesco
It all depends on what you mean by authentication and how you configure each
node.
If you mean authentication re:SSL, then apache.
If you have ACL's defined in Apache, then Apache will, but this is http
basic auth, no cookies.
If you have security defined in WLS or are using session's in WLS, then
cookies will be set and passed from WLS all the way back to the client and
then when a new request is made the cookie will be passed from the client to
apache and back to wls.
Cheers
mbg
"Francesco" <[email protected]> wrote in message
news:[email protected]..
>
> hi all,
> I have some doubts about apache and wls in a cluster. We have 2 Apache
server
>
> (installed on 2 different hosts) in front
> of a clustered WLS 6.1. Now my doubt is: who will take care of
authentication,
> Apache or WLS?
> In other words as the 2 instances of Apache don't know about each other
(they
> are chosen with DNS-round robin), will the
> authentication be done twice? or it's possible to handle authentication on
the
> application
> server rather ? if so, where the Cookie that identifies the session will
be kept?
>
> Tanks a lot
> Francesco
-
Cluster with shared domain folder using OCFS2 and the domain /tmp folder
I've setup a cluster with two machines and one managed server on each machine. One of the machines also hosts the admin server.
Initially, both managed servers were running on the same machine. Everything worked well. When I move to having two machines, I didn't want to have to independently maintain the domain folder on each machine.
So I decided to setup a shared drive between the machines and use OCFS2 to share the domain folder between the two machines.
Everything started up fine, but when I deployed software to the server I would frequently (but not always) get this error:
[wldeploy] Target state: deploy failed on Cluster cluster-01
[wldeploy] weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'deploy' on null BasicDeploymentMBean for deployment mylibrary#[email protected]. Operation can not be performed until server is restarted.
After looking around a bit on google I saw this issue:
http://download.oracle.com/docs/cd/E11035_01/wls100/issues/known_resolved.html#CR279281
which says
Some OS and NFS combinations result in deployment failures or configuration updates with an exception like:
weblogic.management.DeploymentException: Attempt to operate 'distribute' on null BasicDeploymentMBean
Workaround or Solution:
* Run statd() and lockd() processes on every NFS client that accesses a remote NFS volume.
* If multiple servers that share the same domain root are started with different user Ids of same group, set the correct "umask" for the server processes so that a file created by one server can be opened for read/write by other servers without security exceptions.
Unfortunately, I wasn't running NFS, so the workaround didn't help me.
Through dump luck, I tried this:
I replaced the domainroot/tmp folder with a symbolic link to a folder on each machine's local filesystem. Following that change my deployments work everytime.
Does anyone know why this change worked? What is the purpose of the /tmp folder in a domain folder?
Are there any switches I could turn on to get more information about the exact error that causes the deployment mbean to come back null?It may not be the same situation, but I had this "deployer:149189" error and it turned out to be mixing WLS 10.0 and 10.3 installations together in the same install directory and not being scrupulous about environment setup. I think the problem was caused by accidentally running a 10.0 domain with Java 1.6.
Eoin. -
Cluster with only two machines.
Hi all,
Can I make in weblogic6.0 a cluster with two machines. One Aministration and the
other managed ?????
regards, Juan.
Is'nt there a restriction for running All WLS cluster machines on the same
port ?
Or is it just for the Mged Servers ...
"Cameron Purdy" <[email protected]> wrote in message
news:3d1e1d61$[email protected]..
> Not exactly. You'll run a managed server on each of those on the same port
> number, and on one of them you'll run the admin server on a different
port.
>
> Peace,
>
> Cameron Purdy
> Tangosol, Inc.
> http://www.tangosol.com/
>
> "Juan Alonso" <[email protected]> wrote in message
> news:3d1ca2d8$[email protected]..
> >
> > Hi all,
> >
> > Can I make in weblogic6.0 a cluster with two machines. One Aministration
> and the
> > other managed ?????
> >
> > regards, Juan.
>
>
-
Persistent Store Problems for MYSQL Enhanced Cluster With OpenMQ 4.4
I am trying to implement an enhanced cluster with failover. I have edited the config files for each broker instance for a persistent store. I have appended the following to each of the config.properties files:
imq.brokerid=myclusterinstanceINSTANCE1 # I substitute INSTANCE2 for INSTANCE1 for broker #2
imq.persist.store=jdbc
imq.persist.jdbc.dbVendor=mysql
imq.persist.jdbc.mysql.property.url=jdbc:mysql://xxx.xxx.xxx.xx:3306/test
imq.persist.jdbc.mysql.user=user1
imq.persist.jdbc.mysql.needpassword=true
imq.persist.jdbc.mysql.password=mypass
imq.cluster.ha=true
imq.cluster.clusterid=mycluster
imq.cluster.brokerlist=xxx.xxx.xxx.x:37676,yyy.yyy.yyy.y:37676
I then create the persistence storage with "imqdbmgr create tbl". When I view the data in the tables it creates, I have one row. Under Store_Version, I have 410. Under LOCK_ID, it has NULL. When I go to start the brokers with imqbrokerd, I get the following error:
ERROR [B3198]: Error initializing cluster manager:
com.sun.messaging.jmq.jmsserver.util.BrokerException: [B4239]: Failed to load persistent store version from database table MQVER41Cmycluster
at com.sun.messaging.jmq.jmsserver.persist.jdbc.VersionDAOImpl.getStoreVersion(VersionDAOImpl.java:310)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBTool.updateStoreVersion410IfNecessary(DBTool.java:350)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.JDBCStore.checkStore(JDBCStore.java:3599)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.JDBCStore.<init>(JDBCStore.java:127)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.sun.messaging.jmq.jmsserver.persist.StoreManager.getStore(StoreManager.java:157)
at com.sun.messaging.jmq.jmsserver.Globals.getStore(Globals.java:967)
at com.sun.messaging.jmq.jmsserver.cluster.ha.HAClusterManagerImpl.initialize(HAClusterManagerImpl.java:181)
at com.sun.messaging.jmq.jmsserver.Globals.initClusterManager(Globals.java:903)
at com.sun.messaging.jmq.jmsserver.Broker._start(Broker.java:777)
at com.sun.messaging.jmq.jmsserver.Broker.start(Broker.java:410)
at com.sun.messaging.jmq.jmsserver.Broker.main(Broker.java:1971)
Caused by: java.lang.NullPointerException
at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1103)
at com.mysql.jdbc.ResultSetImpl.getInt(ResultSetImpl.java:2777)
at com.sun.messaging.jmq.jmsserver.persist.jdbc.VersionDAOImpl.getStoreVersion(VersionDAOImpl.java:298)
... 16 more
I believe this error is attributed to the NULL value under LOCK_ID. I think that the value under LOCK_ID should be the name of the broker from the config file (even though I specified them in the config files). Any ideas?? THANKS!Just some pointers -- maybe this will be of use:
If you haven't already read it, please take a look at the [ MySQL setup guide|https://mq.dev.java.net/OpenMQ_MySQLCluster_Setup_Guide.html] .
We recommend using NDB Data-store of MySQL Cluster, though this isn't an absolute requirement. Due to some issues we have found with earlier versions, we recommend using MySQL Cluster, 7.0.9 or better (the current version is 7.0.16, or 7.1.5). Either of these would contain Connector/J.
I'd also recommend using the latest version -- MQ 4.4update2 (just in case you happen to have an older copy). There were many minor improvements in the integration with MySQL from the original 4.4 release, to update 2. This is linked at the MQ download page: [https://mq.dev.java.net/downloads.html] -
We have a MSSQL 2008R2 Enterprise edition with a two node active passive fail-over cluster running on 2008R2 windows cluster with out any issues,
Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setuphi,
>>Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
Yes it is possible .You need to add new drives as cluster aware and install SQL server and put data and log files on thse drives.YOu would need to create named instance of SQL server and need to create different resource group.Both old installation and new
onw would work separately.
>>Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
Good point indeed.You are about to create Multi instance cluster and should plan for scenario where one node is down and other node is handling load for both instances.Memory and CPU should be enough to handle the load.
>>Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup .
Just for collation if you are installing new instance seems little wierd to me.You can manage collation at column ,database and at server level.
http://technet.microsoft.com/en-us/library/aa174903(v=sql.80).aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Maybe you are looking for
-
Actually I have the authorization key. I would like to know how to use the B_USERSTAT object to give authorization for this authorization key....
-
Thansfer adobe photoshop album starter 3.2 photos to element 8.0
I've had adobe photoshop album starter 3.2 since I've had my computer. All my family photos are stored there. This morning after uploading photos the program kept closing. I clicked on the register and an email was sent to me telling me that as of
-
Odbc driver returned an error (SQLExecDirectW). Error Details Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OB
-
Binding Resource Bundle to Portlet
When i place resource bundle in my webroot resources folder,and i added the tag resource-bundle for my portlet. Its throwing exception can't find resources bundle exception.Anyone knows how to bundle resources to portlet. Please help me.
-
EIC-- Employee Interaction Cente-- UNCAUGHT_EXCEPTION
We have installed EIC, on SAP EIC 6.O When we execute the EIC, by transaction "HREIC" we have a runtime error on the abap system transaction "ST22": The web client is shown good in the internet explorer but we have the runtime error The exception 'CX