DEBUG PARAMETERS IN WEBLOGIC:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Weblogic Server log file with SSL debug flags enabled
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Using the WebLogic Admin Console
a) Navigate to the tab page "Environments > Servers > {affected server} > Debug"
Browse the debug tree and enable the following debug flags
default > DebugSSL
weblogic > security > DebugSecurity
weblogic > security > DebugSecurity > ssl > DebugSecuritySSL
b) Navigate to the tab page "Environments > Servers > {affected server} > Logging > Advanced"
Change Standard Out: Severity Level -> Debug
c) Reproduce the problem again
d) Collect the Managed Server log files
e.g. DOMAIN_HOME/servers/[servername]/logs/[servername].log [servername].out
LOG_FILE="$LOG_HOME/$SERVER_NAME.out"
-Dweblogic.security.SSL.HostnameVerifier=weblogic.security.utils.SSLWLSWildcardHostnameVerifier
java -Dweblogic.security.SSL.verbose=true -Dweblogic.webservice.client.ssl.strictcertchecking=false examples.webservices.basic.javaclass.SSLClient
DebugHttp
DebugHttpLogging
JAVA_OPTIONS=-Dweblogic.debug.DebugHttp=true -Dweblogic.debug.DebugHttpLogging=true %JAVA_OPTIONS%
JAVA_OPTIONS=-Dweblogic.debug.DebugHttp=true -Dweblogic.debug.DebugHttpLogging=true -DDebugURLResolution=true -Dweblogic.debug.DebugWebAppModule=true
HTTP Trace flags
-Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true -Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
DebugSSL
-Dssl.debug=true -Djavax.net.debug=all -Dweblogic.debug.DebugSSL=true -Dweblogic.debug.DebugSecuritySSL=true -Dweblogic.StdoutDebugEnabled=true -Dweblogic.log.StdoutSeverityLevel=Debug -Dweblogic.log.LogSeverity=Debug
HTTP Webservice:
-Dweblogic.log.StdoutSeverity=Debug
-Dweblogic.wsee.verbose=weblogic.wsee.conversation.*, weblogic.wsee.callback.* <-- -dweblogic.wsee.verbose="* " all="" class="" debug="" debugging="" es="" for="" nbsp="" or="" p="" package="" s="" specific="" to="">-Dweblogic.webservice.verbose=true <-- 8.1="" debugging="" for="" p="" stack="" webservice="" wls="">-Dweblogic.wsee.debug=*
-Dweblogic.wsee.verbose.timestamp=true
You can add more verbose debugging from individual subsystem in webservice using -Dweblogic.wsee.verbose by listing the subsystems in comma-separated list, as shown above. Alternatively, you can use use -Dweblogic.wsee.verbose=* to output all the debug logging.
-Dweblogic.debug.DebugHttp=true -Dweblogic.wsee.verbose=* -Dweblogic.debug.DebugHttp=true -Dweblogic.debug.DebugHttpLogging=true -DDebugURLResolution=true -Dweblogic.debug.DebugWebAppModule=true -Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true -Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
HTTP Trace flags
-Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true -Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
-Dweblogic.slc=true
Use this flag to enable debug level traces that show status for lower-level WLS services, including starting and stopping the domainRuntimeServerService.
-Dweblogic.debug.DebugServerLifeCycle=true
Use this flag to enable debug level traces for Server Life Cycle. Set the trace flags as shown in this example taken from the managed server startup log startManagedWebLogic.sh:
JAVA_OPTIONS="-Dweblogic.security.SSL.trustedCAKeyStore="/refresh/Middleware/wlserver_10.3/server/lib/cacerts" ${JAVA_OPTIONS}"
JAVA_OPTIONS="-Dweblogic.debug.DebugServerLifeCycle=true ${JAVA_OPTIONS}"
Log files will be found in %DOMAIN_HOME%\servers\%SERVER_NAME%\logs\%SERVER_NAME%.log; the actual path names depend on the names used during the initial domain and server configuration. Look for the Debug messages associated with ServerLifeCycle:
ACTION PLAN
-------------------------------------------------------
1, Please enable the following DEBUG from Admin Console for the target weblogic server where the application runs
From WLS, Console:
1.1, Domain Structure ->
1.2, Domain Structure ->
1.3, Domain Structure ->
1.4, restart the target weblogic server and upload the WLS DEBUG logs and application logs after the issue is reproduced.
2, Please explain the topology involved, For example, is there load balancer or proxy server sitting in front of weblogic servers
3, Regarding to the "Caused by: java.net.BindException: Address already in use" shown in application logs,
3.1 can your application team check involved application codes to ensure that java.net.HttpURLConnection.getOutputStream() if involved is invoked only once during http client communication.
For example,
----------getOutputStream being called twice in this example----------
try (PrintWriter pw = new PrintWriter(new BufferedWriter(new
OutputStreamWriter(con.getOutputStream(), "utf-8")));
OutputStream os = new BufferedOutputStream(con.getOutputStream())) {
--------------------
3.2 can your application team explain where the application is connecting to, for example, a endpoint outside weblogic domain? or another managed server in the domain? and what is involved in the application activities (seems like application is making http client call to another endpoint that may be bining address twice?) -
=====Application error===============
2018-02-13 20:31:39,688 ERROR [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] common.GISLogger - GeocodeServiceImpl : processRecords : S011 : SERVER ERROR
com.g1.dcg.client.ConnectionException: Address already in use
at com.g1.dcg.gateway.transport.http.HttpGatewayConnection.process(HttpGatewayConnection.java:224)
at com.g1.dcg.client.RemoteService.process(RemoteService.java:51)
Deploy Debug:
-Dweblogic.debug.DebugDeploy=true -Dweblogic.debug.DebugDeploymentService=true -Dweblogic.debug.DebugDeploymentServiceTransport=true
Cluster debug
-Dweblogic.debug.DebugCluster=true
-Dweblogic.debug.DebugClusterHeartbeats=true
-Dweblogic.debug.DebugClusterFragments=true
Change the logging severity to Debug
Servers-->Server_name-->Logging-->Advanced-->
Standard out :Severity level:Debug
Log file :Severity level:Debug
Message Bridge debug flags
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
-Dweblogic.debug.DebugMessagingBridgeRuntimeVerbose=true
-Dweblogic.debug.DebugMessagingBridgeStartup=true
JTA Debug flags
-Dweblogic.debug.DebugJTAXA=true
-Dweblogic.debug.DebugJTA2PC=true
-Dweblogic.debug.DebugJTAJDBC=true
-Dweblogic.log.StdoutSeverity=Debug
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.log.LogSeverity=Debug
-Dweblogic.log.RedirectStdoutToServerLogEnabled=true
Http debug
-Dweblogic.debug.DebugHttp=true
-Dweblogic.debug.DebugHttpLogging=true -DDebugURLResolution=true -Dweblogic.debug.DebugWebAppModule=true
HTTP Trace flags
-Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true -Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
Kernel & Muxer Debug Flag
-Dweblogic.kernel.debug=true
-Dweblogic.debug.DebugMuxer=true
-Dweblogic.debug.DebugMuxerDetail=true
-Dweblogic.debug.DebugMuxerTimeout=true
-Dweblogic.debug.DebugMuxerConnection=true
-Dweblogic.debug.DebugMuxerException=true
RJVM Abbrevation, Connection & Messaging Debug
-Dweblogic.debug.DebugMessaging=true
-Dweblogic.debug.DebugConnection=true
-Dweblogic.debug.DebugRouting=true
-Dweblogic.debug.DebugAbbrevs=true
-Dweblogic.LogRemoteExceptionsEnabled=true
Server Migration Debug flag
-Dweblogic.kernel.debug=true -Dweblogic.log.StdoutSeverity=Debug
-Dweblogic.debug.DebugServerMigration=true
-Dweblogic.debug.DebugSingletonServices=true
Deployment Debug flag
weblogic.debug.DebugDeploymentServiceInternal
weblogic.debug.DebugDeploymentServiceStatusUpdates
weblogic.debug.DebugDeploymentServiceTransport
weblogic.debug.DebugDeploymentServiceTransportHttp
Classloader Debug flags
-Dweblogic.utils.classloaders.GenericClassLoader.Verbose=true
-Dweblogic.utils.classloaders.ChangeAwareClassLoader.Verbose=true
-Dweblogic.utils.classloaders.ClasspathClassFinder=true
-Dweblogic.utils.classloaders.DefaultFilteringClassLoader.Verbose=true
-Dweblogic.utils.classloaders.FilteringClassLoader.Verbose=true
-Dweblogic.utils.classloaders.FilteringClassLoader.ResourceDump=true
-Dweblogic.utils.classloaders.URLClassFinder.Verbose=true
Webservice Security related:
-Dweblogic.wsee.security.verbose=true
-Dweblogic.wsee.security.debug=true
-Dweblogic.debug.DebugSecurityCredMap=true
Crypto related:
-Dweblogic.xml.crypto.encrypt.verbose=true
-Dweblogic.xml.crypto.dsig.debug=true
-Dweblogic.xml.crypto.dsig.verbose=true
-Dweblogic.xml.crypto.wss.debug=true
-Dweblogic.xml.crypto.wss.verbose=true
-Dweblogic.xml.crypto.keyinfo.debug=true
-Dweblogic.xml.crypto.keyinfo.verbose=true
-Dweblogic.xml.crypto.dsig.debug=true
-Dweblogic.xml.crypto.dsig.verbose=true
-Dweblogic.xml.crypto.encrypt.debug=true
-Dweblogic.xml.crypto.encrypt.verbose=true
SAML related:
-Dweblogic.debug.DebugSecuritySAMLService=true
-Dweblogic.debug.DebugSecuritySAMLCredMap=true
-Dweblogic.debug.DebugSecuritySAMLAtn=true
-Dweblogic.debug.DebugSecuritySAMLLib=true
-Dweblogic.debug.DebugSecuritySAML2Service=true
-Dweblogic.debug.DebugSecuritySAML2CredMap=true
-Dweblogic.debug.DebugSecuritySAML2Atn=true
-Dweblogic.debug.DebugSecuritySAML2Lib=true
General:
-Dweblogic.log.StdoutSeverity=Debug
-Dweblogic.wsee.verbose=weblogic.wsee.conversation.*, weblogic.wsee.callback.*
-Dweblogic.webservice.verbose=true
-Dweblogic.wsee.debug=*
-Dweblogic.wsee.verbose.timestamp=true
Note: You can use use
-Dweblogic.wsee.verbose=* to output all the debug logging.
HTTP Session Debug
-Dweblogic.debug.DebugHttpSessions=true
-Dweblogic.debug.DebugReplication=true
-Dweblogic.debug.DebugHttp=true
Weblogic Security Debug
-Dweblogic.Log.LoggerSeverityProperties="Security=Notice"
-Dssl.debug=true
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.security.SSL.verbose=true
-Dweblogic.security.SSL.debugEaten=true
-Dweblogic.security.SSL.protocolVersion=SSL3
-Dweblogic.DebugSecurityAtz=true
-Dweblogic.DebugSecurityAtn=true
-Dweblogic.DebugSecurityAdjudicator=true
-Dweblogic.DebugSecurityRoleMap=true
-Dweblogic.Debug=weblogic.MasterDeployer
-Dweblogic.Debug=weblogic.SlaveDeployer
-Dweblogic.Debug=weblogic.DeploymentTaskRuntime
-Dweblogic.Debug=weblogic.DeployerRuntime
-Dweblogic.Debug=weblogic.ApplicationContainer
-Dweblogic.debug.DebugSecuritySAMLAtn=true
-Dweblogic.debug.DebugSecuritySAMLLib=true
-Dweblogic.debug.DebugSecuritySAML2Service=true
-Dweblogic.debug.DebugSecuritySAML2CredMap=true
-Dweblogic.debug.DebugSecuritySAML2Atn=true
-Dweblogic.security.realm.debug=true
-Dweblogic.security.RSA.verbose=true
-Dweblogic.security.RC4.verbose=true
-Dweblogic.client.SocketConnectTimeoutInSecs
-Djavax.security.auth.useSubjectCredsOnly=false
-Dweblogic.security.enableNegotiate=true
-DDebugSecurityAdjudicator=false
-Dweblogic.Debug.DebugSecurityAtz=false
-Dweblogic.Debug.DebugSecurityAtn=false
-Dsun.security.krb5.debug=false
LDAP-Related Debug Flags
-Dweblogic.debug.DebugEmbeddedLDAPLogLevel=11
-Dweblogic.debug.DebugEmbeddedLDAP=true
Node Manager
-Dweblogic.nodemanager.debugEnabled=true
-Dweblogic.nodemanager.debugLevel=90
Server lifecycle debug
flags
-Dweblogic.slc=true
-Dweblogic.slcruntime=true
-Dweblogic.debug.DebugServerLifeCycle=true
Java Messaging Services
Messaging Kernel
-Dweblogic.debug.DebugMessagingKernel=true
MDB connectivity
-Dweblogic.debug.DebugEjbMdbConnection=true
JMS Wrappers
-Dweblogic.debug.DebugJMSWrappers=true
JMS SAF
Sending side:
-Dweblogic.debug.DebugJMSSAF=true
-Dweblogic.debug.DebugJMSMessagePath=true
Receiving side:
-Dweblogic.debug.DebugJMSBackEnd=true
-Dweblogic.debug.DebugJMSFrontEnd=true
-Dweblogic.debug.DebugJMSMessagePath=true
JMS Distributed Destinations
-Dweblogic.debug.DebugJMSCommon=true
-Dweblogic.debug.DebugJMSDistTopic=true
-Dweblogic.debug.DebugJMSMessagePath=true
JMS Boot
-Dweblogic.debug.DebugJMSBoot=true
-Dweblogic.debug.DebugMessagingKernelBoot=true
-Dweblogic.debug.DebugStoreIOLogicalBoot=true
JMS store
Logical IO:
-Dweblogic.debug.DebugJMSStoreIOLogical=true
-Dweblogic.debug.DebugJMSStoreIOLogicalBoot=true
Physical IO:
-Dweblogic.debug.DebugStoreIOPhysical=true
-Dweblogic.debug.DebugStoreIOPhysicalVerbose=true
Store XA:
-Dweblogic.debug.DebugStoreXA=true
-Dweblogic.debug.DebugStoreXAVerbose=true
JMS CDS
-Dweblogic.debug.DebugJMSCDS=true
JMS Backend
-Dweblogic.debug.DebugJMSBackEnd=true
JMS Frontend
-Dweblogic.debug.DebugJMSFrontEnd=true
JMS Dispatcher
-Dweblogic.debug.DebugJMSDispatcher=true
Messaging Bridge :
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
-Dweblogic.debug.DebugMessagingBridgeRuntimeVerbose=true
-Dweblogic.debug.DebugMessagingBridgeStartup=true
Clustering
-Dweblogic.diagnostics.debug.DebugLogger.DISABLED=false & one or all of the following
-Dweblogic.debug.DebugClusterAnnouncements=true
-Dweblogic.debug.DebugCluster=true
-Dweblogic.debug.DebugClusterFragments=true
-Dweblogic.debug.DebugJTAMigration=true
-Dweblogic.debug.DebugAsyncQueue=true
-Dweblogic.debug.DebugReplication=true
-Dweblogic.debug.DebugReplicationDetails=true
-Dweblogic.debug.DebugServerMigration=true
-Dweblogic.debug.DebugSingletonServices=true
-Dweblogic.debug.DebugConsensusLeasing=true
-Dweblogic.debug.DebugUnicastMessaging=true
-Dweblogic.cluster.leasing.ClusterFormation=true
-Dweblogic.cluster.leasing.ClusterGroupView=true
-Dweblogic.cluster.leasing.ClusterLeader=true
-Dweblogic.cluster.leasing.ClusterLeaderService=true
-Dweblogic.cluster.leasing.ClusterMember=true
-Dweblogic.cluster.leasing.ClusterMessaging=true
-Dweblogic.cluster.leasing.LeaseClient=true
-Dweblogic.cluster.leasing.LeaseServer=true
-Dweblogic.cluster.leasing.LeaseView=true
-Dweblogic.cluster.leasing.MachineState=true
-Dweblogic.cluster.leasing.DiscoveryService=true
-Dweblogic.cluster.leasing.DisconnectMonitor=true
-Dweblogic.cluster.leasing.MessageEndPoint=true
-Dweblogic.cluster.leasing.MessageSender=true
-Dweblogic.cluster.leasing.SRMResult=true
-Dweblogic.cluster.leasing.FailureDetector=true
-Dweblogic.cluster.leasing.SRMService
RMI & IIOP
-Dweblogic.diagnostics.debug.DebugLogger.DISABLED=false & one or all of the following
-Dweblogic.debug.DebugCorbaClientHttp=true
-Dweblogic.debug.DebugCorbaClientIIOP=true
-Dweblogic.debug.DebugIIOPNaming=true
-Dweblogic.iiop.naming=true
-Dweblogic.debug.DebugIIOPOTS=true
-Dweblogic.iiop.ots=true
-Dweblogic.debug.DebugIIOPTransport=true
-Dweblogic.iiop.transport=true
-Dweblogic.debug.DebugIIOPTunneling=true
-Dweblogic.iiop.http.tunnelLogin=true
-Dweblogic.iiop.http.tunnelRecv=true
-Dweblogic.iiop.http.tunnelSend=true
-Dweblogic.debug.client.dgc=true, to enable debug for dgc
-Dweblogic.rmi.extensions.server.ServerHelper.DebugExportObject=true
-Dweblogic.debug.DebugDGCEnrollment=true
-Dweblogic.debug.ForceGCEachDGCPeriod=true
-Dweblogic.debug.LogDGCStatistics=true
-Dweblogic.debug.DebugMessaging=true
-Dweblogic.debug.DebugGenericMethodDescriptor=true
-Dweblogic.debug.DebugIIOPDetail=true
-Dweblogic.debug.DebugIIOPMarshal=true
-Dweblogic.debug.DebugIIOPTransport=true
-Dweblogic.debug.DebugIIOPSecurity=true
-Dweblogic.debug.DebugIIOPStartup=true
-Dweblogic.debug.DebugIIOPRepalcer=true
-Dweblogic.debug.DebugIIOPConnection=true
-Dweblogic.debug.DebugIIOPDetail=true
-Dweblogic.debug.DebugIIOPDetail=true
-Dweblogic.iiop.marshal=true
-Dweblogic.iiop.transport=true
-Dweblogic.iiop.security=true
-Dweblogic.iiop.startup=true
-Dweblogic.iiop.replacer=true
-Dweblogic.iiop.connection=true
Deployment debugs
-Dweblogic.debug.DebugDeployment=true -Dweblogic.debug.DebugDeploymentServiceInternal=true -Dweblogic.debug.DebugDeploymentServiceTransport=true -Dweblogic.debug.DebugDeploymentServiceTransportHttp=true -Dweblogic.debug.DebugDeploymentServiceStatusUpdates=true
If you have problem in edit lock, system resource deployment or configuration updates, you may also turn on configure debug flag:
-Dweblogic.debug.DebugConfigurationEdit=true
HTTP Debugs
-Dweblogic.debug.DebugURLResolution=true
-Dweblogic.debug.DebugHttp=true
-Dweblogic.debug.httpd=true
-Dweblogic.debug.httpd.log=true
-Dweblogic.debug.httpd.servlet=true
JTA
-Dweblogic.debug.DebugJTAPropagate=true
-Dweblogic.debug.DebugJTAGateway=true
-Dweblogic.debug.DebugJTAXA=true
-Dweblogic.debug.DebugJTA2PC=true
-Dweblogic.debug.DebugJTAJDBC=true
-Dweblogic.debug.DebugJDBCSQL=true
JNDI
-Dweblogic.debug.DebugJNDI =true
-Dweblogic.debug.DebugJNDIResolution =true
-Dweblogic.debug.DebugJNDIFactories =true
-Dweblogic.debug.DebugJNDIAppVersion =true
Workmanager
-Dweblogic.workmanager=true
-Dweblogic.StuckThreadHandling=true
-Dweblogic.IncrementAdvisor=true
-Dweblogic.MinThreadsConstraint=true
-Dweblogic.responsetimerequestclass=true
-Dweblogic.workmanagerservice=true
Server Life Cycle
-Dweblogic.slc=true -Dweblogic.slcruntime=true -Dweblogic.debug.DebugServerLifeCycle=true
Classloaders
-Dweblogic.utils.classloaders.GenericClassLoader.Verbose=true
-Dweblogic.utils.classloaders.ChangeAwareClassLoader.Verbose=true
-Dweblogic.utils.classloaders.ClasspathClassFinder=true
-Dweblogic.utils.classloaders.DefaultFilteringClassLoader.Verbose=true
-Dweblogic.utils.classloaders.FilteringClassLoader.Verbose=true
-Dweblogic.utils.classloaders.FilteringClassLoader.ResourceDump=true
-Dweblogic.utils.classloaders.URLClassFinder.Verbose=true
WebService
-Dweblogic.wsee.verbose=*
Security
SAML:
-Dweblogic.debug.DebugSecuritySAMLService=true
-Dweblogic.debug.DebugSecuritySAMLCredMap=true
-Dweblogic.debug.DebugSecuritySAMLAtn=true
-Dweblogic.debug.DebugSecuritySAMLLib=true
-Dweblogic.debug.DebugSecuritySAML2Service=true
-Dweblogic.debug.DebugSecuritySAML2CredMap=true
-Dweblogic.debug.DebugSecuritySAML2Atn=true
-Dweblogic.debug.DebugSecuritySAML2Lib=true
-Dweblogic.debug.DebugSecurityCredMap=true
WebService Security
-Dweblogic.xml.crypto.wss.debug=true
-Dweblogic.xml.crypto.wss.verbose=true
-Dweblogic.xml.crypto.keyinfo.debug=true
-Dweblogic.xml.crypto.keyinfo.verbose=true
-Dweblogic.xml.crypto.dsig.debug=true
-Dweblogic.xml.crypto.dsig.verbose=true
-Dweblogic.xml.crypto.encrypt.debug=true
-Dweblogic.xml.crypto.encrypt.verbose=true
You can also apply these debugs from the Weblogic Server console by navigating through the following path :
Environments ---> Servers ---> ServerName ---> Debug
These is also a small utility named "DebugScopeViewer" which provides information about the debug flags :
java weblogic.diagnostics.debug.DebugScopeViewer
For GCOverhead limit
==============================
Add "-Dweblogic.management.disableManagedServerNotifications=true" flag as a java option for Admin server to resolve this issue
-Dcom.bea.wlw.netui.disableInstrumentation=true -D_Offline_FileDataArchive=true -Dweblogic.connector.ConnectionPoolProfilingEnabled=false
DB Test:
java.util.Properties props = new java.util.Properties();
props.put("user", "ams_ams_user_wl103");
props.put("password", "Ams_ams_user_wl103#123");
java.sql.Driver d=Class.forName("oracle.jdbc.OracleDriver").newInstance();
java.sql.Connection conn=Driver.connect("jdbc:oracle:thin:@xdhfd11-scan1:1521/ams_piexaprd_oltp_srvc.world", props);
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The data file and change log file used by the embedded LDAP server can potentially grow quite large. You can configure maximum sizes for these files with the following weblogic.Server command line arguments:
-Dweblogic.security.ldap.maxSize=
-Dweblogic.security.ldap.changeLogThreshold=
Embedded LDAP Server Replication
The WebLogic Server embedded LDAP server for a domain consists of a master LDAP server, maintained in the domain's Administration Server, and a replicated LDAP server maintained in each Managed Server in the domain. When changes are made using a Managed Server, updates are sent to the embedded LDAP server on the Administration Server. The embedded LDAP server on the Administration Server maintains a log of all changes. The embedded LDAP server on the Administration Server also maintains a list of Managed Servers and the current change status for each one. The embedded LDAP server on the Administration Server sends appropriate changes to each Managed Server and updates the change status for each server. This process occurs when an update is made to the embedded LDAP server on the Administration Server. However, depending on the number of updates, it may take several seconds or more for the change to be replicated to the Managed Server.
You can configure the behavior of the embedded LDAP server on the Administration Server and the Managed Servers in a domain using the Administration Console. By selecting the Domain > Security > Embedded LDAP page in the Administration Console, you can set these attributes:
Refresh Replica At Startup — Specifies whether the embedded LDAP server in a Managed Server should refresh all replicated data at boot time. This setting is useful if you have made many changes when the Managed Server was not active, and you want to download the entire replica instead of having the Administration Server push each change to the Managed Server.
Master First — Specifies whether a Managed Server should always connect to the embedded LDAP server on the Administration Server, instead of connecting to the local replicated LDAP server.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
No comments:
Post a Comment