Weblogic giving license error for only one managed server

weblogic

Hi i am running weblogic 8.1 on a unix server. I currently had 4 managed servers running fine and started two more today. Unfortunately people started getting denied with a "The server is not licensed for this operation.connect rejected, the server license allows connections from only 5 unique IP addresses. When i check my license.bea file it appears to be for only a developer license, which would make sense. The part I'm confused on is why my other 4 managed servers never receive this message. Don't they all use the same license file? They are all in the same directory?

Best Answer

Looks like your Weblogic install is unlicensed, or at least you haven't installed the license file. You need to stick the file license.bea in the BEA_HOME directory.

The 5 IP limit is always enforced by Weblogic when running in development mode.

It's also advisable to use a reverse web proxy in front of the Weblogic managed servers.

Related Solutions

How to restart a WebLogic domain remotely using Ant

You can reboot a WebLogic managed server remotely via the wlserver ANT task, but such requests must be done through the domain Admin server. For example:

<wlserver 
    adminserverurl="t3://myadminhost:7001"
    username="weblogicAdminUser"
    password="weblogicPassword"
    servername="MyManagedServer" 
    action="reboot"
    noExit="true"/>

Having said that, using the ANT task to reboot a managed server can be unreliable. I would recommend using the Weblogic Scripting Tool (WLST) instead.

Ssl – Custom Trust and Custom Identity Keystore in WebLogic 10.3

Create the boot.properties file:

${DOMAIN_HOME}/servers/AdminServer/security/boot.properties

edit the content to add the following:

username=weblogicAdminUsername
password=weblogicAdminUnencryptedPassword
TrustKeyStore=CustomTrust
CustomTrustKeyStoreFileName=/path/to/custom/keystore
CustomTrustKeyStorePassPhrase=keystoreUnencryptedPassword

Start the WebLogic server.

After startup, note the contents of the boot.properties file are now encrypted.

An alternative way to do it is as follows:

JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.TrustKeyStore=CustomTrust "
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStorePassPhrase=customKeystorePassword "
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStoreFileName=/my/custom/keystore.jks "

Append the above lines to the domain's bin/setDomainEnv.sh file. Customize the last two.

Best Answer

Related Solutions

How to restart a WebLogic domain remotely using Ant

Ssl – Custom Trust and Custom Identity Keystore in WebLogic 10.3

Related Topic