Startup.properties settings for managed servers
We are using WLS 9.2 MP3 on Solaris 10 (SPARC).
I have built a few test systems in an attempt to document configurations and noticed my managed servers on the systems start up with a different "weblogic.management.server" setting in the log files. This setting appears in the <domain>/servers/<server name>/data/nodemanager/start.properties file as "AdminURL=http:\://xxx.xxx.xxx.xxx\:7001"
Each system was built and rebuilt using the same settings. Each system has multiple interfaces. One system has an entry of AdminURL=http:\://192.168.100.100\:7001 and another system has an entry of AdminURL=http:\://10.10.10.100\:7001 even though each system was built just like the other.
Every time I manually change the adminURL setting it gets reset on each server restart (which I expected). I have not specified (that I know of) the IP address or interface of the admin server anywhere in the "server start" settings. I also notice the admin server is starting on all interfaces on the system (not sure if this is good/bad/indifferent).
Can anyone tell me where the startup.properties file entries are pulled from?
As a followup: I just noticed (after my post) a slight difference between my systems. One has a fiber connection whereas the others do not. When I execute 'ifconfig -a' I see the interfaces/IP's in different orders (because the interfaces are named differently). I also noticed a wlsifconfig.sh script in one of the startup files. It almost appears as though the wlsifconfig.sh script is setting the AdminURL value and is pulling it from the last interface it finds in the ifconfig listing?????
Thanks for any assistance
To diagnose problems with Thunderbird, try one of the following:
*Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.
*Restart the operating system in '''[http://en.wikipedia.org/wiki/Safe_mode safe mode with Networking]'''. This loads only the very basics needed to start your computer while enabling an Internet connection. Click on your operating system for instructions on how to start in safe mode: [http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-including-safe-mode Windows 8], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7 Windows 7], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-vista Windows Vista], [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true" Windows XP], [http://support.apple.com/kb/ht1564 OSX]
; If safe mode for the operating system fixes the issue, there's other software in your computer that's causing problems. Possibilities include but not limited to: AV scanning, virus/malware, background downloads such as program updates.
Similar Messages
-
How to install Window service for Managed Servers of a Cluster
Dear All,
I am preparing a production setup consist of three machines A,B and C. Machines A is the Admin Server which hosts a cluster consist of two managed nodes. I intend to schedule both these nodes, targeted to two different machines (machines B node-b and machine C host node-c), as startup task on daily basis. I have no Node Manager running on machine A, but on machine B and machine C.
I am only interested to schedule started task for node-b and node-c only. I need to know how to install the Windows services for the node-b and node-c since there are targeted on remote machines. Starting managed server as Win sevice works in the case of standalone managed servers but not sure when it comes to cluster setup.I appreciate if you can throw some light on this question.
Thanks
KrisKrish,
>Let say I gracefully shutdown both managed servers while >Admin is running. Do you think both these nodes while be >brought up ? I dont think they will come up.
If you require an automatic restart when the managed server did not enter a failed state you can use the weblogic.Admin utility to ping the servers and kick off a server startup in the normal way with nodemanger see:
http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
If your servers entered a failed state you can use weblogics self health monitoring.
>Can we use JMX MBean to start managed servers ?
Yes.
As long as the nodemanagers are running you can start the managed servers using scripted commands using the weblogic.Admin class or your own java app using JMX.
I think you may also be able to use WLST
http://dev.bea.com/codelibrary/code/wlst.jsp
hope this helps
cheers
Please see the
Hussein Badakhchani
www.orbism.com -
Changing settings for DNS Servers?
I need to enter some DNS settings in order to use certain programs on the network. On a Windowz machine, these settings are entered into an area called DNS suffixes.
I go to Network and try to enter the names into DNS Servers, though it is only allowing me to enter certain characters. For example, it will not let me enter a "l" or a "p." Why is this?
Thanks.The only thing you can enter for DNS servers is the actual IP address in the form: xxx.xxx.xxx.xxx, e.g., 192.0.100.40
-
What should be the client url for managed servers in a cluster
Hi guys,
I have created a cluster(cluster_1) having 4 managed servers. 2 managed servers on my machine(IP1) and 2 managed servers on other machine(IP2).
I am able to deploy a xxx.war file on my admin server
also
I am able to deploy the same war file on my cluster
When I try to hit the client url, it gives me back the correct data, but it creates the session on the admin server and not the cluster.
If I remove the xxx.war file from the deployment(deployed on admin server) and redeploy the xxx,war file on the cluster, it gets deployed successfully , but the client url gives me a 404 error.
What should I do, so that after hitting the client url, it creates the session on the managed servers in the cluster ?
My admin server is not the part of this cluster.
cluster ip:127.0.0.1
ip1: 10.25.63.130
ip2: 10.25.63.131
please help
SalilHi Salil
This is exactly what I mentioned in my earlier post. You CANNOT and should NOT expose the managed server url (host, port) to the end users. Because as you already figured out, you can specify only one. Or they cannot try one at a time like that.
This is where, the Load Balancer will come into picture like Apache Web Server. After installing Apache web server, usually it runs at default port 80. So you just expose the apache host to outside world. Also most companies will have Firewalls and Apache is outside of Firewall and all weblogic servers are inside the Firewall. In apache, you configure the weblogic cluster details like the host names and ports of each managed server etc in httpd.conf file etc.
Ex: For outside users, they may try like http://apachehost/myWeb/myHello.jsp -> apachehost is the host name where Apache web server is running at port 80. NOW Apache is smart enough to do Load Balancing and Failover. If 100 users access the site with 4 managed servers, ideally each managed server will get 25 requests (load balancing). Also if 2 servers are killed, automatically, request will NOT go to them, but to other 2 live servers etc etc. Apache takes care of this.
Bottom line, please see my earlier post, and you need to have some sort of Web Server like Apache for your cluster setup.
Thanks
Ravi Jegga -
SCCM 2012 license for managing Servers
Hi,
We want to manage windows servers with SCCM 2012. Can someone explain what are the licensing options available and how much it cost per server.
Regards,
MadhanThis came up on this forum recently. Here you go
http://social.technet.microsoft.com/Forums/en-US/db10f78f-3c44-40fd-92a8-1264ee06dccb/configmgr-2012-licensing?forum=configmanagergeneral
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
While starting managed servers asks for password of localhost
We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
The problem I have narrowed down is that there are startup.properties file for the managed servers.
It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
While SOA1 it is asking for password for the above host and the managed server is not starting.
Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
I could not yet figure out why it is behaving differently in the first node.
This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
It works perfectly in production environment.Hi
Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
username=domainadminusername
password=doaminadminpassword
When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
Exmaple locations:
On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
Thanks
Ravi Jegga -
What is the Ideal Production Setup For One Admin and 4 Managed Servers
Dear Experts
I will be starting with production setup including one Admin server and 4 managed servers in one single domain.
I am thinking of creating a single node environment(no clusters) as the machine has following configuration
OS : Windows Server 2008 R2 Datacenter
RAM : 48 GB
System Type : 64 bit
Processor : Intel(Xenon) 4 processors [email protected]
Can you please let me know if this configuration would suffice for the 4 managed servers if i assign Xmx and Xms as 4096 and Heap Space as 1024 to all the Managed Servers.
It is very urgent and i need to convey to the Infrastructure team if harware procurement is required.
We are looking at somewhere around 300 concurrent users(maximum load) and 100(minimum load) at a given point of time.
Please reply ASAP.
Thanks in advance
Edited by: Abhinav Mittal on Apr 23, 2013 7:58 PM
Edited by: Abhinav Mittal on Apr 23, 2013 8:03 PMHeap size must be calculated according to the applications that are been deployed on each JVM.
With no deployments, you dont need more than 256k for managed servers heap size and 512k for adminserver. As biggest its your heap size, longer will take your garbage collection. And if you can prevent it, better do it.
Kinds,
Gabriel Abelha -
Node Manager installed as service does not start managed servers. WLS 10.3
Hi All,
I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
<Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
<Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
The node manager properties file contains the following
#Mon Apr 20 10:54:45 PDT 2009
DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
JavaHome=C\:\\bea\\JROCKI~1
AuthenticationEnabled=false
NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
LogLevel=INFO
DomainsFileEnabled=true
StartScriptEnabled=false
StartScriptName=startWebLogic.cmd
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
The managed servers' boot.properties file and startup file are below
boot.properties:
#Thu Jul 23 13:48:26 PDT 2009
CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
TrustKeyStore=CustomTrust
password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
CustomTrustKeyStoreType=JKS
username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
startup.properties:
#Server startup properties
#Thu Jul 23 13:48:27 PDT 2009
Arguments=-Xms1024m -Xmx1024m -Xnohup
JavaHome=C\:\\bea\\jrockit_160_05
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
BeaHome=C\:\\bea
ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
AdminURL=http\://localhost\:7001
JavaVendor=BEA
AutoRestart=true
AutoKillIfFailed=false
I am wondering if I left out a parameter some where.
Any help would be greatly appreciated.
Thanks,
GregFirst of all, I assume you mean "... up it does NOT start ..."?
It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers. -
Have NodeManager start managed servers on machine reboot
Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
Ideas appreciated,
dmac.Hi Dmac,
To achieve this in Windows, you must consider the following WLS Components:
1. Node Manager
2. Admin Server
3. Managed Server
Node Manager
For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
Create a Windows service for Node Manager:
1. WL_HOME\server\bin\installNodeMgrSvc.cmd
2. Verify in Windows Services that a service was created.
Admin Server
For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Admin Server
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password>
2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=AdminServer
set PRODUCTION_MODE=true
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
"%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Managed Server
For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
Create a Windows service for the Managed Server (using wls_forms as an example)
1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
username=weblogic
password=<the weblogic username password e.g manager11g>
2. Create a command script called installWLSFORMS_Service.cmd which has lines like
SETLOCAL
set DOMAIN_NAME=<your wls domain>
set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_FORMS
set PRODUCTION_MODE=true
set ADMIN_URL=http://mymachine.mycompany.com:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL
NOTES:
a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
Configuring the Windows service to restart upon failure
As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
Example of starting the Admin Server and a Managed Server using Node Manager
1. Create a batch script similar to this:
Myscript.cmd
call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
2. Create a Python script similar to this:
ServerStart.py
nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
nmStart('AdminServer')
connect ('weblogic','welcome1','t3://192.168.0.101:7001')
nmstart('myserver','Server','t3://192.168.0.101:7002')
If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
Some Additional Information to Remember
The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place. -
Problem Starting Managed Servers
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring up my Managed
Server its not reading the command line arguments which I supplied through the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
are not read and so I am having errors like Unable to load libraries, etc.
Also when I saw the log file for managed server the class path and the arguments
are printed in a different way than I have set. I dont know if thats a problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the console is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I havent typed that
in the console. Has any one have experince with setting the command line arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatly appreciated.
Thanks,
KiranSeems a method signature does not match with the implementation in the
library either due to namemangling or incompatible versions of libraries.
You are loading your own custom native libraries for security.
Best would be use the default startManagedServer -- once the server has
started, copy and paste the entire value of java.library.path into the
startup arguments for Remote start.
For instance in my server log file:
####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
<main> <system> <> <141034> <Java system property: java.library.path =
/home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
I would set that as the arguments :
-Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
usr/lib
If this does not work, then java for some reason is not taking library paths
set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
of arguments to java. Another thing is before starting the NodeManager, set
the LD_LIBRARY_PATH to point the library directories and see if this helps.
regards,
Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
>
Sabha,
I am trying to start the managed server via remote start. After readingyour reply
I have cleaned up the argument list for remote start. Now I am gettingaltogether
a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
I dont know why I am having trouble to do the same through the remotestart).
>
I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
to the argument liist which I did. Below you can find the exact error Ihave got:
>
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
referenced symbol not found
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
va:52)
>
atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
9)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
l.java:208)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
rImpl.java:81)
>
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.security.acl.Realm.getRealm(Realm.java:84)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
>
Please let me know if you need more description.
Thanks,
Kiran
"Sabha" <[email protected]> wrote:
Either you are attempting to start a managed server through its
NodeManager
for which the remote startup arguments are not correct or something else
is
wrong. How are you starting the server? The remote start is only when you
want to start the server through NodeManager and not for normalinvocation
of the startManagedServer script.
Does the server really start? can you paste the startup arguments for the
remote start of the managed server as saved in the config.xml.
What is the log generated when the managed server is startedup.
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Sabha,
The main problem is:
What ever I am trying to give in the command line arguments through theConsole:
Servers -> serverName -> Remote Start->Arguments.
is not being read during managed server start up.
I have all the libraries defined defined in java.lib.path. I dont knowwhy
its not
being read by managed server during start up. Am I missing something.
-Kiran
"Sabha" <[email protected]> wrote:
If its unable to load the performance packs, try setting
java.library.path
to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
can just copy what is in the admin weblogic.log file for the
java.library.path (make sure the paths are correct and applicable forthe
maanged server box also) and pass that as an argument as
in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
-Sabha
"Kiran" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to start Managed Server on Sun Solaris. My admin Server
and
managed Server
are on the same Machine.
My admin Server starts up with out any problem. WhenI try to bring
up
my
Managed
Server its not reading the command line arguments which I supplied
through
the Console:
Servers -> serverName -> Remote Start->Arguments. For some reason
these
command arguments
are not read and so I am having errors like Unable to load
libraries,
etc.
Also when I saw the log file for managed server the class path and
the
arguments
are printed in a different way than I have set. I dont know if thats
a
problem or
not. I am copying part of that for your reference.
classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
i
c
6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
i
t
y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
I have checked the config.xml file and what ever I have set in the
console
is being
saved properly in the xml file.
Can any one know why the back slash is printed above even though I
havent
typed that
in the console. Has any one have experince with setting the command
line
arguments
and class path through console for Managed servers.
I am stuck up at this point. Any help in this regard will be greatlyappreciated.
Thanks,
Kiran -
Re: Precompiling JSP with admin/managed servers
Thanks, but I'm not doing any copying.
The admin/managed-server communication copies things to the managed server,
which then always recompiles the pages when hit.
-Greg
Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
"Robert Coonrad" <[email protected]> wrote in message
news:[email protected]...
>
> check out post 8366...i found that i was not preserving
> the lastmodified date on my jsps and this was causing
> unnecessary re-compilation.
>
> hope it helps...
> bobc
>
> "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
> >I believe I have exhausted all permutations of EARing/notEARing,
> >WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
> >placing them in a static location and setting workingDir to that
location,
> >combinations of the above.
> >
> >No matter what, the managed server re-compiles pages the first time they
> >are
> >hit. Non admin/managed-server I have no problems.
> >
> >Can anyone from BEA comment on this problem? Or give me a workaround
> >for
> >getting a cluster working with precompiled jsps?
> >
> >-Greg
> >
> >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >news:[email protected]...
> >> Grrr... The JSP engine is extremely frustrating! I've spent many hours
> >> fighting the "staleness" checker in WL. I've been through all of the
> >> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
> >> pre-compilation working on single-server deployments, but admin/managed
> >> server deployments have me beat.
> >>
> >> WL6.1, SP1, Solaris
> >>
> >> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
> >> place. The fixed place contains pre-compiled versions of all jsps
> >made on
> >> that machine using jspc not 20 minutes earlier using the JSP files
> >in the
> >> exploded EAR file used by the admin server as the model for managed
> >> servers.. The managed servers are on the same machine.
> >>
> >> When the admin server gives an application to a managed server, the
> >managed
> >> server creates a temporary directory containing all of the webapp
> >> components, etc. The file timestamps on these files is the set by
> >the
> >> copying process to the time of the managed server boot (why?!?!????!?),
> >so
> >> the staleness check always thinks they are new and could care less
> >what
> >> precompiled jsps I have in my workingDir, the WEB-INF/classes
directory,
> >or
> >> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
> >in
> >> this scenario.
> >>
> >> If I tell the managed server to precompile everything on boot (about
> >45
> >> minutes for this app) it will create versions of the classes that match
> >th
> >e
> >> new JSP file timestamps, but this does not even survive a reboot of
> >the
> >> managed server because it AGAIN creates a new temp version of
everything
> >on
> >> the next reboot with new timestamps.
> >>
> >> If I wait for the managed server to boot and find the directory like
> >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
> >copy
> >> (via cp -pr to retain timestamps) all of the original webapp components
> >on
> >> top of the temp versions, the staleness checker is happy and the
> >> pre-compiled versions work fine.
> >>
> >> There HAS to be a way to package pre-compiled versions of the JSPs
> >in the
> >> "model" application in the admin server and keep from having to
precompile
> >> the JSPs on every managed server every time managed server is booted..
> >>
> >> It would help if we had a way to bypass the staleness checking
> >completely..
> >> Or you guys should make the timestamps on the files copied by the
> >> admin/managed deployment process match properly so the staleness
checker
> >> doesn't think the JSP is different.
> >>
> >> It would also help if the engineer who wrote this could explain the
> >rules
> >> being implemented by the staleness checker. So far all the messages
> >in
> >the
> >> newsgroup have amounted to point solutions for problems without a good
> >> understanding of what the engine is checking for and/or doing under
> >the
> >> covers. Looking at the generated .java files for the JSP pages helps,
> >but
> >> it is not good enough...
> >>
> >> Anyone out there have a working admin/managed server JSP application?
> >> -Greg
> >>
> >> -----------------------------------------------------------
> >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >>
> >>
> >>
> >
> >
>
The admin/managed-server communication copies things to the managed server, which then always recompiles the pages when hit.
This is a known issue and is fixed. The timestamps of the compiled classes was not being preserved when extracted from the war file used to distribute to the managed servers. This will be available in WLS6.1 Service Pack 3 - and there is a temporary patch available for SP2. Please ask your friendly BEA support person for it (you can refer to CR058946)
I'd give you the patch myself, but they like to keep track of these things...
Regards,
Alex
"Girish" <[email protected]> wrote in message news:[email protected]...
>
> "Aditya Kiran Gavvala" <[email protected]> wrote:
> >Greg,
> >
> >I have been following your posts, because our application deployment
> >ran
> >into exact same problem you ran into. I had spent a full two days
> >researching into the problem. And I figured the solution. Hope this
> >helps.
> >
> >Here are my discoveries:
> >
> >The following applies only to the following environment:
> >OS: Linux (perhaps for Win/Unix/Solaris etc)
> >WLS 6.0 SP2 ( no rolling patches): I found Rolling Patch2 (RP2) not useful
> >for this problem.
> >Clustered environment with Admin/Managed servers
> >
> >- When you compile JSP using weblogic.jspc compiler it puts the JSP file
> >timestamp into the compiled class. You can see it in the generated java
> >file
> >(you need to supply -keepgenerated switch to jspc)
> >
> >- When a request is made to a JSP page after the application is deployed,
> >it
> >seems to be retrieving this timestamp from the compiled class file and
> >comparing it with the JSP file timestamp. If they dont match a compile
> >command gets run by the server. Thereby you see a compile happening at
> >run
> >time.
> >
> >- If you have exploded directory deployment, when you start the managed
> >servers they create a ".war" file (under some temp dir) with all the
> >JSP
> >source files going into the file. You can notice this by looking into
> >the
> >server log file. Therefore all JSP source files get a brand new timestamp
> >in
> >the archive (a timestamp later than what was put class files by
> >weblogic.jspc). So, the server at run time sees that the timestamp in
> >the
> >class file is older than the JSP source file and runs a recompile. So
> >DONT
> >DO EXPLODED directory deployment if your environment is as described
> >in this
> >post.
> >
> >- If you have ".war" file deployment, you will not have a problem. At
> >the
> >start up time managed server still creates "".war" file under a temp
> >directory however it seems to be copying the content of the your ".war"
> >file. So, the timestamps of JSP remain the same as they were before.
> >SO NO
> >RE-COMPILATION.
> >
> >- Another important thing to remember is to make sure you specify the
> >workingDir in the weblogic.xml file. That is where the precompiled class
> >files should reside. This should be any directory the server uses as
> >scratch
> >pad to compile classes or find (pre)compiled classes. This is not a
> >directory inside your .war file is what I am trying to get at.
> >
> >Hope this helps,
> >Aditya
> >
> >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >news:[email protected]...
> >> Thanks, but I'm not doing any copying.
> >>
> >> The admin/managed-server communication copies things to the managed
> >server,
> >> which then always recompiles the pages when hit.
> >>
> >> -Greg
> >>
> >> -----------------------------------------------------------
> >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >>
> >> "Robert Coonrad" <[email protected]> wrote in message
> >> news:[email protected]...
> >> >
> >> > check out post 8366...i found that i was not preserving
> >> > the lastmodified date on my jsps and this was causing
> >> > unnecessary re-compilation.
> >> >
> >> > hope it helps...
> >> > bobc
> >> >
> >> > "Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
> >> > >I believe I have exhausted all permutations of EARing/notEARing,
> >> > >WARing/notWARing, placing precompiled jsp class files in
> >WEB-INF/classes,
> >> > >placing them in a static location and setting workingDir to that
> >> location,
> >> > >combinations of the above.
> >> > >
> >> > >No matter what, the managed server re-compiles pages the first time
> >they
> >> > >are
> >> > >hit. Non admin/managed-server I have no problems.
> >> > >
> >> > >Can anyone from BEA comment on this problem? Or give me a workaround
> >> > >for
> >> > >getting a cluster working with precompiled jsps?
> >> > >
> >> > >-Greg
> >> > >
> >> > >"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
> >> > >news:[email protected]...
> >> > >> Grrr... The JSP engine is extremely frustrating! I've spent many
> >hours
> >> > >> fighting the "staleness" checker in WL. I've been through all
> >of the
> >> > >> newsgroup messages pertaining to pre-compiling, etc., and I've
> >gotten
> >> > >> pre-compilation working on single-server deployments, but
> >admin/managed
> >> > >> server deployments have me beat.
> >> > >>
> >> > >> WL6.1, SP1, Solaris
> >> > >>
> >> > >> I've done the pageCheckSeconds=-1 and the workingDir is set to
> >a
> >fixed
> >> > >> place. The fixed place contains pre-compiled versions of all
> >jsps
> >> > >made on
> >> > >> that machine using jspc not 20 minutes earlier using the JSP files
> >> > >in the
> >> > >> exploded EAR file used by the admin server as the model for managed
> >> > >> servers.. The managed servers are on the same machine.
> >> > >>
> >> > >> When the admin server gives an application to a managed server,
> >the
> >> > >managed
> >> > >> server creates a temporary directory containing all of the webapp
> >> > >> components, etc. The file timestamps on these files is the set
> >by
> >> > >the
> >> > >> copying process to the time of the managed server boot
> >(why?!?!????!?),
> >> > >so
> >> > >> the staleness check always thinks they are new and could care
> >less
> >> > >what
> >> > >> precompiled jsps I have in my workingDir, the WEB-INF/classes
> >> directory,
> >> > >or
> >> > >> anywhere else. The pageCheckSeconds=-1 seems to be completely
> >ignored
> >> > >in
> >> > >> this scenario.
> >> > >>
> >> > >> If I tell the managed server to precompile everything on boot
> >(about
> >> > >45
> >> > >> minutes for this app) it will create versions of the classes that
> >match
> >> > >th
> >> > >e
> >> > >> new JSP file timestamps, but this does not even survive a reboot
> >of
> >> > >the
> >> > >> managed server because it AGAIN creates a new temp version of
> >> everything
> >> > >on
> >> > >> the next reboot with new timestamps.
> >> > >>
> >> > >> If I wait for the managed server to boot and find the directory
> >like
> >> > >> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
> >> > >copy
> >> > >> (via cp -pr to retain timestamps) all of the original webapp
> >components
> >> > >on
> >> > >> top of the temp versions, the staleness checker is happy and the
> >> > >> pre-compiled versions work fine.
> >> > >>
> >> > >> There HAS to be a way to package pre-compiled versions of the
> >JSPs
> >> > >in the
> >> > >> "model" application in the admin server and keep from having to
> >> precompile
> >> > >> the JSPs on every managed server every time managed server is
> >booted..
> >> > >>
> >> > >> It would help if we had a way to bypass the staleness checking
> >> > >completely..
> >> > >> Or you guys should make the timestamps on the files copied by
> >the
> >> > >> admin/managed deployment process match properly so the staleness
> >> checker
> >> > >> doesn't think the JSP is different.
> >> > >>
> >> > >> It would also help if the engineer who wrote this could explain
> >the
> >> > >rules
> >> > >> being implemented by the staleness checker. So far all the messages
> >> > >in
> >> > >the
> >> > >> newsgroup have amounted to point solutions for problems without
> >a
> >good
> >> > >> understanding of what the engine is checking for and/or doing
> >under
> >> > >the
> >> > >> covers. Looking at the generated .java files for the JSP pages
> >helps,
> >> > >but
> >> > >> it is not good enough...
> >> > >>
> >> > >> Anyone out there have a working admin/managed server JSP application?
> >> > >> -Greg
> >> > >>
> >> > >> -----------------------------------------------------------
> >> > >> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
> >> > >> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >
> >
>
[att1.html]
-
Precompiling JSP with admin/managed servers
Grrr... The JSP engine is extremely frustrating! I've spent many hours
fighting the "staleness" checker in WL. I've been through all of the
newsgroup messages pertaining to pre-compiling, etc., and I've gotten
pre-compilation working on single-server deployments, but admin/managed
server deployments have me beat.
WL6.1, SP1, Solaris
I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
place. The fixed place contains pre-compiled versions of all jsps made on
that machine using jspc not 20 minutes earlier using the JSP files in the
exploded EAR file used by the admin server as the model for managed
servers.. The managed servers are on the same machine.
When the admin server gives an application to a managed server, the managed
server creates a temporary directory containing all of the webapp
components, etc. The file timestamps on these files is the set by the
copying process to the time of the managed server boot (why?!?!????!?), so
the staleness check always thinks they are new and could care less what
precompiled jsps I have in my workingDir, the WEB-INF/classes directory, or
anywhere else. The pageCheckSeconds=-1 seems to be completely ignored in
this scenario.
If I tell the managed server to precompile everything on boot (about 45
minutes for this app) it will create versions of the classes that match the
new JSP file timestamps, but this does not even survive a reboot of the
managed server because it AGAIN creates a new temp version of everything on
the next reboot with new timestamps.
If I wait for the managed server to boot and find the directory like
.../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically copy
(via cp -pr to retain timestamps) all of the original webapp components on
top of the temp versions, the staleness checker is happy and the
pre-compiled versions work fine.
There HAS to be a way to package pre-compiled versions of the JSPs in the
"model" application in the admin server and keep from having to precompile
the JSPs on every managed server every time managed server is booted..
It would help if we had a way to bypass the staleness checking completely..
Or you guys should make the timestamps on the files copied by the
admin/managed deployment process match properly so the staleness checker
doesn't think the JSP is different.
It would also help if the engineer who wrote this could explain the rules
being implemented by the staleness checker. So far all the messages in the
newsgroup have amounted to point solutions for problems without a good
understanding of what the engine is checking for and/or doing under the
covers. Looking at the generated .java files for the JSP pages helps, but
it is not good enough...
Anyone out there have a working admin/managed server JSP application?
-Greg
Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
check out post 8366...i found that i was not preserving
the lastmodified date on my jsps and this was causing
unnecessary re-compilation.
hope it helps...
bobc
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote:
>I believe I have exhausted all permutations of EARing/notEARing,
>WARing/notWARing, placing precompiled jsp class files in WEB-INF/classes,
>placing them in a static location and setting workingDir to that location,
>combinations of the above.
>
>No matter what, the managed server re-compiles pages the first time they
>are
>hit. Non admin/managed-server I have no problems.
>
>Can anyone from BEA comment on this problem? Or give me a workaround
>for
>getting a cluster working with precompiled jsps?
>
>-Greg
>
>"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
>news:[email protected]...
>> Grrr... The JSP engine is extremely frustrating! I've spent many hours
>> fighting the "staleness" checker in WL. I've been through all of the
>> newsgroup messages pertaining to pre-compiling, etc., and I've gotten
>> pre-compilation working on single-server deployments, but admin/managed
>> server deployments have me beat.
>>
>> WL6.1, SP1, Solaris
>>
>> I've done the pageCheckSeconds=-1 and the workingDir is set to a fixed
>> place. The fixed place contains pre-compiled versions of all jsps
>made on
>> that machine using jspc not 20 minutes earlier using the JSP files
>in the
>> exploded EAR file used by the admin server as the model for managed
>> servers.. The managed servers are on the same machine.
>>
>> When the admin server gives an application to a managed server, the
>managed
>> server creates a temporary directory containing all of the webapp
>> components, etc. The file timestamps on these files is the set by
>the
>> copying process to the time of the managed server boot (why?!?!????!?),
>so
>> the staleness check always thinks they are new and could care less
>what
>> precompiled jsps I have in my workingDir, the WEB-INF/classes directory,
>or
>> anywhere else. The pageCheckSeconds=-1 seems to be completely ignored
>in
>> this scenario.
>>
>> If I tell the managed server to precompile everything on boot (about
>45
>> minutes for this app) it will create versions of the classes that match
>th
>e
>> new JSP file timestamps, but this does not even survive a reboot of
>the
>> managed server because it AGAIN creates a new temp version of everything
>on
>> the next reboot with new timestamps.
>>
>> If I wait for the managed server to boot and find the directory like
>> .../applications/.wlnotdelete_man1/wlap7336/webapp/... and physically
>copy
>> (via cp -pr to retain timestamps) all of the original webapp components
>on
>> top of the temp versions, the staleness checker is happy and the
>> pre-compiled versions work fine.
>>
>> There HAS to be a way to package pre-compiled versions of the JSPs
>in the
>> "model" application in the admin server and keep from having to precompile
>> the JSPs on every managed server every time managed server is booted..
>>
>> It would help if we had a way to bypass the staleness checking
>completely..
>> Or you guys should make the timestamps on the files copied by the
>> admin/managed deployment process match properly so the staleness checker
>> doesn't think the JSP is different.
>>
>> It would also help if the engineer who wrote this could explain the
>rules
>> being implemented by the staleness checker. So far all the messages
>in
>the
>> newsgroup have amounted to point solutions for problems without a good
>> understanding of what the engine is checking for and/or doing under
>the
>> covers. Looking at the generated .java files for the JSP pages helps,
>but
>> it is not good enough...
>>
>> Anyone out there have a working admin/managed server JSP application?
>> -Greg
>>
>> -----------------------------------------------------------
>> Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
>> www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
>>
>>
>>
>
>
-
Limit on number of Managed Servers in a cluster
Hi All,
Do you know if there is any limit on number of managed servers I can have in a
cluster.
If there is a limit then how many?
If not, is there a recommended limit from BEA?
We are using Weblogic 6.1 SP2 and we have 16 managed servers running in the cluster.
Under heavy load (through put about 600-800) the console is not responding fast.
Also when we try to monitor the Weblogic Servers from the console under Monitoring->performance
, the screen is not getting refreshed faster(which makes me think the monitoring
info I see on the console is not completely correct).
I have a heap size of 96m for admin and 768m for Managed Servers.
Did anyone see this problem before.
Are there any command line arguments that I can add to make my console respond
faster?
If not, do we have any patch from BEA that makes console work faster?
Please suggest.
Thanks for your attention,
Kiran
Hi Vineet,
In Latest version of SAP MDM which is 7.1 we have the liberty to use multiple Main tables so answer to your question is yes we can use 20-30 main tables, now the question is that what type of data model you are prepairing this question is just to understand your entire structure and may be suggest some thing at higher level on which you can think and then take corrective action as per your thoughts.
Generally even if you are integrating Customer/Products in single repository and then designing the main table you wont have to prepare such huge number of main tables you can have these two main tables and then rest of then as sub tables and refer it to each other also you need to know what imapct it will have on system performance becuase they would be referring to each other and also if you are creating some thousands of records in each repository then it is more advisable to use limited number of main tables and use MDM to it's fullest capability by designing such model that we have best utlisation of server performance.
Hope it helped a bit.
Let me know if you need any further information on same.
Thanks and Regards
Praful. -
Disaster Recovery Scripts for Managed Server MSI Startup
I am trying to get some custom start scripts created for each of my managed servers in the event the admin console is down or server gets hosed. We use nodemanager to start the managed servers in a Windows environment. I have about 8 managed servers and they all use the same nodemanager classpath but all have different server start arguments (different memory settings, etc....) so I need to make different custom scripts for each.
Verbose Garbage Collection to Determine Heap Size .....this thread by Jay has been very helpful but so far I am just getting kicked back to the syntax screen like something is wrong in my script. Attached is the script and the output when I run it. Any help would be appreciated...thanks.
startManagedFPCE1.cmd contents
java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=beaadmin -Dweblogic.management.password=beaadminxxx -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle\Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
Results of running above script:
C:\Oracle\Middleware\user_projects\domains\SIT11\servers\FPCE1>java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=b
eaadmin -Dweblogic.management.password=beaadminsit11 -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle
\Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\
sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\M
iddleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\dep
recated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-server to select the "server" VM
-hotspot is a synonym for the "server" VM [deprecated]
The default VM is server.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options"bharat nagwani" <[email protected]> wrote:
>
Hi,
Configuration: Weblogic 8.1SP2 on Windows 2000, 1 admin server and 14
managed
servers
whats the right way from these 2 scenarious to create a domain on managed
server
1. create domain on managed server using configuration wizard. Then point
to this
domain from administration server remote start tab(root directory). This
is what
we do so far.This is the best way to create managed servers for your domain.
>
2. Just enter user_projects/domains folder/$domain name$ in remote start
tab(root
directory)
on admin server console and when you start the managed server from
admin console
the domain folder and files will be created.
Yes, the managed server is started in this case at the root directory you specified.
The difference is in the
1. first case we see all scripts like startManagedWeblogic, setenv, boot.properties
etc
this may help(we still dont know) if one wants to bring up managed
server
manually using
startManagedServer.bat without using node manager.Yes, that is correct. You will need to edit the startManagedServer.bat to include
the admin server URL, username and paswword..
>
2. second case only 2-3 files get created like msi-config.xml and SerializedSystemIni.dat
Basically first case is superset of second case.
What is the experience of people in this regard?
thanks much
bharat -
Where to increase Java Heap settings for Admin and Managed Server.
Hello Experts
I am having issue with increasing the JVM memory arguments for the Admin and Managed Servers. I have tried in a couple of places to increase the memory arguments (Xms and Xmx to 1024m)but its not taking effect. When I start the Admin Server and Managed server , I do not see the increased Heap settings. Here is what I see -
"Starting WLS with line : /oracle/app/bi/Oracle_BI1/jdk/java -server - Xms256m -Xmx512m -XX:MaxPermSize=512m"
I have the following memory arguments in the setDomainEnv.sh located in <DOMAIN_HOME>/bin
XMS_SUN_64BIT ="2048"
export XMS_SUN_64BIT
XMX_SUN_64BIT="2048"
export XMX_SUN_64BIT
Looks like this did not work , so I added an entry in the setOBIDomainEnv.sh file hoping to increase the Java memory , but that does not work either. Below is from setOBIDomainEnv.sh file -
Really, trying to understand where/how the JVM settings are controlled from. Please guide me.
Appreciate your time.
RakeshUnder setobidomainenv.sh you will also find the admin server tag's so you need to increase the jvm parameters in there too. Depending upon your java vendor and bit version(Sun/Oracle/IBM/HP and 32-bit vs 64-bit ) So change accordingly
eg:
if server group is not obi then we can assume that it is Admin Server
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
# -UseSSE42Intrinsics required for server running EM
if [ "${JAVA_USE_64BIT}" = "true" ] ; then
# Admin Server memory args for 64-bit Sun JVM
SERVER_MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics"
export SERVER_MEM_ARGS
similarly in setdomain.sh you will find the args as below:
XMX_SUN_64BIT="512"
export XMX_SUN_64BIT
XMS_SUN_64BIT="256"
export XMS_SUN_64BIT
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
WLS_MEM_ARGS_64BIT="-Xms256m -Xmx512m"
export WLS_MEM_ARGS_64BIT
WLS_MEM_ARGS_32BIT="-Xms256m -Xmx512m"
export WLS_MEM_ARGS_32BIT
after setting them just execute them ./setdomain.sh and ./setobidomainenv.sh and then try to start the admin and managed servers and see the process running with the updated values.
Maybe you are looking for
-
Java Program to copy file from one directory to another failing
Hello All, Oracle Applications 12.1.3 RDBMS: 11.2.0.30 SQL*Plus: 10.1.0.5.0 Java beginner here so help is much appreciated. I'm have some java code that I'm using to copy a file from one directory to another in an Oracle Applications Server. I noti
-
Computer can't find printer on wireless network
Hi I have a HP laserjet pro 200 m276nw and it is connected to my WIFI, but when im tryin to add the printer under printers and faxes, it dosn't show. Windows just keeps seaching the network but it never showes. Does anybody have an idea about what's
-
Viewing Streaming video on E61I
Hi, Recently got the E61i device, and have an unlimited data plan, but I am unable to connect to any streaming videos on youtube or any other site. It says cannot connect to server, I checked with the CARRIER and there is no restriction from their en
-
Deployment: How to get rid of certificate import pop up in Reader XI
I want to deploy XI to our machines, but before I do so, I have to be sure, there are no pop ups confusing the users. There is a pop up asking me to import older certificates and I can select between "Import" and "Default" - which is weird enough. Ho
-
4.6 C Project coped to -- ECC 6.0
I am new to LSMW. I have copied one project from 4.6 C to ECC 6.0. The lsmw worked fine in 4.6C with lsmw and vd02... however I got a problem in ECC 6.0 , the lsmw is not updated . Also vd02 looks different , in between vd02 and via LSMW in both in 4