Managed Servers are fluctuating .

Hi,
Installed WebLogic Server 10.3.5.
Having AdminServer + 8 Managed Servers.
AdminServer + ManagedServers-1/2/3/4 on machine X
ManagedServers-5/6/7/8 on machine Y
All 8 servers are in cluster.
Domain Name : mattermanagement
Issue :
ManagedServer-7 and ManagedServer-8 alone go down, and upon refresh in the console, servers show in Running mode. They're fluctuating.
Not sure whether they're really going down, and coming up.
From logs , i can see only 2 types of error messages like :
<03-Mar-2015 13:15:34 o'clock GMT> <Error> <JMX> <BEA-149500> <An exception occurred while registering the MBean null.
java.lang.IllegalArgumentException: Registered more than one instance with the same objectName :
mattermanagement:ServerRuntime=managed7_mattermanagement,MessageDrivenEJBRuntime=ReportingMDB_wli.reporting.jmsprovider.queue,Name=ReportingMDB_wli.reporting.jmsprovider.queue,ApplicationRuntime=JMS Reporting Provider,Location=managed7_mattermanagement,Type=EJBPoolRuntime,EJBComponentRuntime=jmsreportprovider.jar new:[email protected]e existing [email protected]5
        at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:168)
        at weblogic.management.mbeanservers.compatibility.internal.CompatibilityObjectNameManager.lookupObjectName(CompatibilityObjectNameManager.java:65)
        at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:87)
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
Any idea why managedServers-7/8 alone having issue ? What casing this ?
Anything i need to check/verify ?
Thanks

Hi,
Can you check if there is a conflict or you have used the same name for two resources in Weblogic.
Because if the resources have the same name it causes a conflict.
Have a look at the below thread which have the same issue reported
https://community.oracle.com/thread/2290229
Mbean Null /// PermGen // Manifest.mf --- Many many errors.
weblogic error while starting the application
And for the below error message you can follow the recommendation in the below link and check
<03-Mar-2015 13:23:22 o'clock GMT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
ServerIdentity failed validation, downgrading to anonymous. error (BEA/Weblogic forum at JavaRanch)
Hope it helps

Similar Messages

Admin server is going down, but managed servers are fine.

HI,
Admin server is going after sometime of starting, but nodemanger and managed servers are running fine, I didn't anything in admin.log everything looks fine.
WebLogic Server 8.1 SP4
jrockit81sp4_142_05
Pls let me whats the problem with admin server.

Way too little information to go on. What operating system? Are you looking at stdout and stderr for messages? Do any random files show up in the directory in which you started the adminserver (core files, hotspot error files, etc)? Does it occur if you switch to using Sun's JDK? Have you tried undeploying any applications (other than the console, of course) or startup classes from the admin server?

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

The Managed servers are going down frequently due to leasing renewal.

We have 3 SOA Managed Servers in our Production Environment running each of them on 3 different Machines.
The servers are going down frequently due to leasing renewal issue.
Please see the errors below. SOA_MS3 was the Cluster Leader.
From SOA_MS1 logs we see -
<Jun 15, 2011 12:11:24 AM MDT> <Warning> <Cluster> <WL-000147> <Server "SOA_MS1" failed to renew lease in the leasing basis hosted by SOA_MS3.>
<Jun 15, 2011 12:11:24 AM MDT> <Error> <Cluster> <WL-000150> <Server failed to get a connection to the leasing basis hosted by SOA_MS3 in the past 30 seconds for lease renewal. Server will shut itself down.>
<Jun 15, 2011 12:11:24 AM MDT> <Critical> <Health> <WL-310006> <Critical Subsystem ServerMigration has failed. Setting server state to FAILED.
Reason: ServerSOA_MS1 failed to renew lease in the leasing basis hosted by SOA_MS3>
<Jun 15, 2011 12:11:24 AM MDT> <Critical> <WebLogicServer> <WL-000385> <Server health failed. Reason: health of critical service 'ServerMigration' failed>
<Jun 15, 2011 12:11:24 AM MDT> <Notice> <WebLogicServer> <WL-000365> <Server state changed to FAILED>
<Jun 15, 2011 12:11:24 AM MDT> <Error> <com.bea.weblogic.kernel> <BEA-000000> <cannot load libary 'stackdump': java.lang.UnsatisfiedLinkError: no stackdump in java.library.path
>
<Jun 15, 2011 12:11:24 AM MDT> <Error> <WebLogicServer> <WL-000383> <A critical service failed. The server will shut itself down>
<Jun 15, 2011 12:11:24 AM MDT> <Notice> <WebLogicServer> <WL-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 15, 2011 12:11:24 AM MDT> <Notice> <Cluster> <WL-000163> <Stopping "async" replication service>
From SOA_MS2 logs we see -
15, 2011 12:11:16 AM MDT> <Warning> <Cluster> <WL-000147> <Server "SOA_MS2" failed to renew lease in the leasing basis hosted by SOA_MS3.>
<Jun 15, 2011 12:11:16 AM MDT> <Error> <Cluster> <WL-000150> <Server failed to get a connection to the leasing basis hosted by SOA_MS3 in the past 30 seconds for lease renewal. Server will shut itself down.>
<Jun 15, 2011 12:11:16 AM MDT> <Critical> <Health> <WL-310006> <Critical Subsystem ServerMigration has failed. Setting server state to FAILED.
Reason: ServerSOA_MS2 failed to renew lease in the leasing basis hosted by SOA_MS3>
<Jun 15, 2011 12:11:16 AM MDT> <Critical> <WebLogicServer> <WL-000385> <Server health failed. Reason: health of critical service 'ServerMigration' failed>
<Jun 15, 2011 12:11:16 AM MDT> <Notice> <WebLogicServer> <WL-000365> <Server state changed to FAILED>
<Jun 15, 2011 12:11:16 AM MDT> <Error> <com.bea.weblogic.kernel> <BEA-000000> <cannot load libary 'stackdump': java.lang.UnsatisfiedLinkError: no stackdump in java.library.path
>
<Jun 15, 2011 12:11:16 AM MDT> <Error> <WebLogicServer> <WL-000383> <A critical service failed. The server will shut itself down>
<Jun 15, 2011 12:11:16 AM MDT> <Notice> <WebLogicServer> <WL-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Also, In SOA_MS3 logs we see the followi error -
####<Jun 15, 2011 11:43:18 PM MDT> <Error> <Cluster> <soaprdi3> <SOA_MS3> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1308202998662> <WL-000168> <Failed to restart/migrate server "SOA_MS3" because of Failed to start the migratable server on one of the candidate machines
Failed to start the migratable server on one of the candidate machines
at weblogic.cluster.singleton.MigratableServerState.serverUnresponsive(MigratableServerState.java:95)
at weblogic.cluster.singleton.MigratableServersMonitorImpl.timerExpired(MigratableServersMonitorImpl.java:164)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks,

Its been many days support working on this, they do not have any clue. we escalated, not much of clue they have yet.
So, wanted put it across industry experts on SOA.
Any idea on what causes this Leasing renewal issue and the potential resolution?
Thanks

Weblogic 10.3.6 managed servers are not working properly

Hi,
i am using weblogic 10.3.6. I have 6 managed server and one Admin server. I observed one thing that when i up Managed6 and run my application. In one of the java file i am using one jar file to fetch one class(Bussiness Object instance). For managed 6 the code is working fine. it gives me the same class file. but if i up any other managed server then i am getting the Impl of that class.
can anyone help me out. Thanks in advance.

Hi,
You shouldn't have to edit the startup.properties manually.
Try the following sequence:
1. Shut down all managed servers;
2. Change the property in the Admin Console;
3. Restart the AdminServer;
4. Start the managed servers and check the property;
Make sure the managed server do not start in Independence Mode

Can a gateway server alert me that the management servers are unavailable?

I have an environment spread across four countries. In the main country is my MS cluster and the Operations and OperationsDW Dbs. This works great. Until something happens to the Operations and OperationsDW Dbs which also kills our exchange server in the
main country.
Can a gateway server tell me that this is happening so I know to resolve?

Email alerts arr handled by the RMS server. The client are acting based on the MP which is downloaded to the local server and the agent will pass on the ginfo to the gateway server and it will in turn send to MS and RMS. If RMS is. It available, the information
or trigger will be queued at the gateway until rms is available
Blog: Http://theinfraguys.com
Follow me at Facebook http://www.facebook.com/theinfraguys
Please remember to click “Mark as Answer” on the answer if it helps you in anyway

Direct Access Management Servers, what are the entry good for?

In the advanced Direct Access setup wizard you have the ability to enter your management servers. I haven't been able to find an explanation of why, what is it good for? If I understand everything correct DA gives full access to the subnet so why is it of
interest to list some servers as "management servers"?

Hi,
Management servers are servers that you are able to access from the da client Before logged on as a user.
Your domain controllers are by default infrastructure servers, but in many cases you want to add for example SCCM, NAP and other servers to be accessable prior logon.
If you are using the manage-out functionality in DirectAccess, and want to access a client prior anyone is logged on, the management server is also needed there.
http://technet.microsoft.com/en-us/library/jj574200.aspx
Microsoft Certified Trainer
MCSE: Desktop, Server, Private Cloud, Messaging
Blog: http://365lab.net

Error while starting managed servers in a cluster

Hi,
          I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
          I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
          The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
          Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
          Can someone please tell me if I've missed something? I'd appreciated any help with this.
          Thanks
          Ameeth
          <Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
          .>
          <Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
          <Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
          r HTTP from Reactor-1.
          java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
          at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
          at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
          at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
          ketFactory;I)V(HttpClient.java:128)
          at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
          Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
          at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
          at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
          at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
          at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
          at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
          at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
          at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
          at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
          >
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
          ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
          emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
          icates with a full strength (domestic) license.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
          :\bea\weblogic81\server\lib\DemoTrust.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
          :\bea\JROCKI~1\jre\lib\security\cacerts.>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
          7002, ip address 127.0.0.1>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
          ip address 127.0.0.1>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
          ain "ReactorAdminServer" running in Development Mode>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
          <Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
          <Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
          r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
          actor-1.
          java.io.IOException: Reference to server no longer exists.
          Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
          n for this error.
          at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
          11)
          at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
          at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
          at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
          at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
          at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
          at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
          at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
          at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)

make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?

How many managed Servers do you need?

Hi,
One thing that has come up time and time again, is when trying to think about a new project and a new WL domain, is trying to know how many WL Managed Servers do you need?
Does BEA have some sort of metrics which says ok for this amount of input we recommend you having 4 managed servers on 4 single boxes?
And is there think on have 2 managed servers on 1 box or 2 managed servers on two boxes?
Any Help Appreciated.
Kind Regards,
Alistair.

Hi :-D
I don't believe BEA have guide lines on how many Managed servers are required based on Metrics. You could look at some performance evaluations but it's really only relevant if your application acts in the same way.
Cheers,
Doug.

Shutdown(block='false') only works via Admin Server, not managed servers

Hello,
We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
connect(user, pwd, http://localhost:7001)
shutdown('myserver1', 'Server', block='false')
shutdown('myserver3', 'Server', block='false')
shutdown('myserver5', 'Server', block='false')
shutdown('myserver7', 'Server', block='false')
shutdown('myserver9', 'Server', block='false')
All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
connect(user, pwd, url='t3://localhost:8001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:9001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:10001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:11001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:12001')
shutdown(block='false')
disconnect()
NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
Best regards,
Michael

Hi Mike,
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
or
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Regards,
Kal

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
          >>
          >>
          >>
          >
          >

Multicast Error When Starting Managed Servers

Environment: HP-UX 11i, Weblogic 8.1 SP1.
          We're getting the following error when we start managed servers in our clustered environment:
          <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
          37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
          java.net.SocketException: Can't assign requested address
          at java.net.PlainDatagramSocketImpl.join(Native Method)
          at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
          at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
          at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
          at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
          at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
          at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          >
          We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
          1) Different multicast addresses/ports;
          2) The util.multicastTest app.
          3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
          Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
          Thanks in advance for any help...
          Brian


Environment: HP-UX 11i, Weblogic 8.1 SP1.
          We're getting the following error when we start managed servers in our clustered environment:
          <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
          37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
          java.net.SocketException: Can't assign requested address
          at java.net.PlainDatagramSocketImpl.join(Native Method)
          at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
          at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
          at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
          at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
          at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
          at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
          at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
          at weblogic.Server.main(Server.java:32)
          >
          We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
          1) Different multicast addresses/ports;
          2) The util.multicastTest app.
          3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
          Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
          Thanks in advance for any help...
          Brian

Question on Managed servers

Hi
I have one admin server and 2 managed servers in our prodcution server.
The managed servers are using 2 different data sources . both defined
from the admin server.
Now my question is
If I shutdown the admin server and try to run the managed server it will
work perfectly and I tried it out . Is this an expecterd behaviour??
If I shutdown one managed server and the admin server , does it releases
any connections made in the conenction pool which is used by the managed
server
Please advise
TIA

you can do greaceful shutdown from console or by using weblogic.Admin
SHUTDOWN command.
sree
"dn" <[email protected]> wrote in message
news:[email protected]..
sree
Thanks for the answer
When you mean graceful shutdown , is it the shutdown we can do from the
admin console , or is there any other way to do that
Thanks
sree bodapati wrote:
If I shutdown the admin server and try to run the managed server it will
work perfectly and I tried it out . Is this an expecterd behaviour??yes thats expected. admin server is used to configure the managed
servers.
the actually pool you created is targeted to the managed server and itwill
get created on the managed server.
If I shutdown one managed server and the admin server , does it releases
any connections made in the conenction pool which is used by the managed
serverYes if you do a graceful shutdown the managed servers will release allthe
connections properly to the db and then shutdown. shutting down just the
admin server when the pool is targeted to the managed server will haveno
effect on the pool on managed server.
"dn" <[email protected]> wrote in message
news:[email protected]..
Hi
I have one admin server and 2 managed servers in our prodcution
server.
>>>
The managed servers are using 2 different data sources . both defined
from the admin server.
Now my question is
If I shutdown the admin server and try to run the managed server it will
work perfectly and I tried it out . Is this an expecterd behaviour??
If I shutdown one managed server and the admin server , does it releases
any connections made in the conenction pool which is used by the managed
server
Please advise
TIA

Cluster Monitoring didn't show all the managed servers in cluster .

Hi
We have below configuration :
domain :- 6 clusters
each cluster :- 3 managed servers (managed servers are on different physical boxes)
when monitoring the cluster we can see
for ms1 it shows : ms1,ms2 but not ms3
for ms2 it shows : ms1,ms2 but not ms3
for ms3 it shows : ms1,ms2,ms3
ms3 is Running.
Why ms1 and ms2 are not able to see ms3? This is happening with all the clusters.ms1 and ms2 are not able to see ms3.
Is the reason that heart beat messages are not received by ms1 and ms2 even though ms3 is running?
Is this because network issue?
Is it that if JVM is busy doing full Gc then it ignores Hearbeat messages. ?
Please correct me if i ma wrong.
Thanks in advance.. :)

Hi,
Did u check if the server MS3 was running .. also did u see any exception/error/warn message in the system.out log.
regards,
Zeno

Managed Servers are fluctuating .

Similar Messages

Maybe you are looking for