Domain log of managed servers

Hi,
Having gone over the documetation for WL7 logging, I understood that in a
managed environment besides having a local log, the managed servers also
send the messages to the administration server via JMX to a single domain
log.
My question is, what happens if the admin server goes down? will those log
messages be missed, or are they stored somewhere and when the server is up
again they are logged? can someone please shed some light on the workings
of this mechanism.
Thanks
Trevor

Hello,
I guess this thread detail can help you:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/e547a497-7e17-4632-a636-85f0055effdf/advice-on-domain-change-scenario-for-sharepoint-2007-server?forum=sharepointadminlegacy
http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

Similar Messages

Configuring the weblogic domain with multiple managed servers(SOA)

Hi
We are trying to create a domain where we have a admin server and 2 SOA manged servers under a cluster.
domain
Admin_Server
SOA_Cluster
SOA_Managed1
SOA_Managed2
I tries the default values but that puts my soa-infra into the Admin server and as far as I know that is not supposed to be the case.
Can any one tell me what are the libraries that I should be selecting for the cluster when I try configuring the domain?
Thanks

Thanks Vlad.
I found another link that might be helpful to someone who is looking for something like this
https://blogs.oracle.com/reynolds/entry/installing_an_11g_soa_cluster_2
Thanks.

Clustered servers domain log

Hi,
          Having gone over the documetation for WL7 logging, I understood that in a
          managed environment besides having a local log, the managed servers also
          send the messages to the administration server via JMX to a single domain
          log.
          My question is, what happens if the admin server goes down? will those log
          messages be missed, or are they stored somewhere and when the server is up
          again they are logged? can someone please shed some light on the workings
          of this mechanism.
          Thanks
          Trevor


I just ran a simple test with 6.1 sp3. I set the same values you have except for:
Min size: 1k
Time: equal to 5 minutes after I started the server.
It rotated the file correctly. Maybe you need to set the time to something shortly
after you start the server, and decrease the min size to 1k. This will at least
run a test that should rotate the file quickly.
Regards,
Glenn
Developer Relations Engineer
BEA Technical Support
dc wrote:
My domain log file is not being rotated. I am trying to have the file rotated
at least once per day. The following are my domain log file settings:
File Name: config/mydomain/logs/wl-domain.log
Rotation Type: by Time
File Min Size: 500k
Rotation Time: 00:00
File Time Span: 24 hours
<checked> Number Of Files Limited
File Count: 30
I am running Weblogic Server 6.1 SP3 on Solaris 8.
Any ideas?

Running managed servers from different WL versions under a domain

Hi,
Would it be possible to run managed servers (in non clustered way) from different versions of WebLogic under a single domain, with admin server of higher WebLogic version controlling the domain and the managed servers?
Regards,
Gobi

Hi Gobi,
we can make it run such a way but it may lead to many complication with patch sets.
Few thing work in one environment and other will not so it is not at all recommended way to set such configuration.
Regards,
Kal

Managed Servers not starting with options configured in config.xml

Hi,
I Installed an Weblogic 10.3 on a Red Hat system and i configured an domain and 2 managed servers.
I configured the servers with some java arguments like this:
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m
I do see in the ${DOMAIN_HOME}/config/config.xml the managed servers with the settings that I have configured it via the Web Gui Admin Console.
Now I want to start the Managed Servers with the following command:
+cd ${DOMAIN_HOME}/bin+
+./startManagedWebLogic.sh managed-server1 http://admin:port+
When i check the console, I don't see the correct JVM settings! Also other options that I configured in the Web Gui Admin Console, don't appear in the logfile.
The JVM settings I see, are those from the AdminServer.
How can I change/fix this?
Please help.
Kind regards,
Werner

Hi,
Please add the changes to the startup script startManagedWeblogic.sh.
You can add the memory args settings as "-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/home/oracle/logs/managed-server{1,2}_gc.log -XX:NewSize=128m -XX:MaxNewSize=128m -Xms384m -Xmx384m -XX:PermSize=128m"
Please let me know if it dosent fix.

Admin server not sending bootstrap servlet configuration to managed servers

I am having a bit of strange issue.
I have weblogic 8.1 SP5 domain in PROD.
14 managed servers in the domain
When i start the managed serverA, sometimes it starts, sometimes it doesnt.
By looking at admin server logs, i found the following.
When the managed ServerA doesnt start, the admin server has the following log snippet
<<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server ServerA.>
####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA>
####<Apr 14, 2009 2:37:01 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
When the managed ServerA starts, the admin server has the following log snippet
Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server serverA.>
####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server serverA.>
####<Apr 14, 2009 2:38:15 AM EDT> <Info> <Configuration Management> <MachineA> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server serverA.>
####<Apr 14, 2009 2:38:21 AM EDT> <Info> <Configuration Management> <catlmsxp166.corp.cox.com> <adminServer> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> *<The bootstrap servlet has finished sending the configuration to serverA.>*
The difference is that admin server unable to send the bootstrap servlet configuration to managed servers, as highlighted above
Has anyone encountered this issue?
If so, is there is solution to this?
Right now i am doing the work around (Which is restart admin server and then start managed server, for every managed server that does not start)
But i cant do this all the time.
MY domain has 14 managed servers. All of them exhibit similar behaviour.
Some times they start, some times they dont.
Edited by: gvamsius on Apr 14, 2009 1:22 PM
Edited by: gvamsius on Apr 14, 2009 1:23 PM

Honestly I've never seen a similar problem.
Could you show us the "standard out" when you start the servers?
Could you to show us the standard out when you start the servers?

Creating new Managed Servers on remote machines

Hi,
We have a multi-machine domain already in place. Nodemanager is configured and we're using the architecture suggested in Oracle SOA Enterprise Deployment Guide, where we have one domain home for the AdminServer and one domain home for the Managed servers. Right now what we need to know is how to add new managed servers in the easiest and fastest way possible on the mserver home on both the adminserver local machine and on the remote machine, this is a development environment and we need to be able to quickly create and delete these servers for developers to work.
We know that the standard way of doing it is doing a pack (for the managed servers only), and then an unpack on the mserver home both on local and remote machine after changing the root directory of these servers to match those homes. Here is were we have our first doubts. Do the unpack command command has to be run with the already running servers down? Does this pack and unpack process affects what we already have deployed on the running managed servers? And last but not least, is there any way to automate this process? Because we need to give the developers the ability to create clusters on the environment through the admin server console, but without giving them access to the underlying operating system.
If this seems like a newbie question is because we are, we're just in the process of migrating oas 10g to weblogic 11g and there are tons of basic administration stuff that seem pretty strange for us, we've looked through the Oracle manuals and metalink but even though some show you how to create the domain with remote managed servers for the first time, we couldn't find any mention on how to add the mserver efficiently after that.
Thanks!

Cris,
Thanks again for your help, we're trying to figure out how to present this procedure to our customer, just one thought though, we were thinking about moving away from the architecture presented by de SOA Enterprise Deployment guide, and using a single domain home located on the shared storage, that way we could create the managed servers from the admin console without having to use pack/unpack and deciding where to run the servers just by configuring machines and nodemanager. However, we haven't seen this kind of configuration anywhere on Oracle manuals, is there any other problem you are aware of in this idea? We're using a storage with multipath for the shared disk so we're not very concerned about availability (and if the storage went down the weblogic domain would be the least of our problems).
Regards, Franco.

Performance of Clustered Managed Servers

WLS 10.3.5 on Solaris10
we have the clustered weblogic10.3.5 domain with two managed servers, which a web app deployed.
we use proxy server (an ohs server) as the frontend host.
we tested for the app login, if both managed servers are started, the login takes about 2 mins.
however if only one managed server is started, the login only takes less 1/2 min.
There is no problem to support two managed servers in the ram and cpu on the server
Why?
where should we start to look into the issue?

Hi,
According to the info you sent, there are 71GB of swap area in use and 7GB of real memory free.
This is not conclusive, as we don't know what is in the swap area. It could be part or the entire JVM for your application. Also, we have to take into consideration shared memory.
I believe you are running many applications in that server, and possible multiple environments.
In order to avoid spending too much time investigating other config issues that might not exist, I think you should try to eliminate the swap to see if this is the issue. I believe that this could be the main issue, based on the info I have so far.
Would be possible for you to stop all or some of the applications running in that server? Then you should check the available RAM (make sure that there are at least 10GB available before starting both managed servers) and restart both managed servers which you have your application running.
Regarding the response times for the login, does it always take the same time to login? You mentioned about 30 seconds, this also seems very high to me. Are your discarding the first login after the server restart? Depending on which framework you are using, it might be interpreting some artifacts or compiling the JSPs in the first execution.
Regards,
Fabio Douek

Domain Created: Failed Restarting Managed Servers in a cluster

Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick

Hi Revanth,
The issue seems to be with the JMX URL value defined in the 'server URL' property.
Apparently I ran into the same issue as I was unable to access the Admin Server URL from the SMA.
Changing the Host and Port value properly resolved the issue for me.
Regards,
Anandraj

Management Servers in untrusted domains

Hi,
I am planning a deployment of SCOM 2012 R2 and have several questions regarding the appropriate placement of management and gateway servers.
The environment has multiple untrusted domains and need to monitor both Windows and Linux computers on both sides of the firewall. The main domain has 1500 Windows computers and 1300 Linux computers. The untrusted domain has 250 Windows servers and
450 Linux servers.
It is understandable that gateway servers are utilized to communicate across the firewall.
The questions are:
1. Is it possible to locate one or more management servers in the untrusted domain for the Linux servers and another management server to work with the Windows servers and have those management servers in the untrusted domain communicate through the firewall
via gateway servers to the databases in the main domain?
2. If it is not possible to have management servers in the untrusted domain communicate via the gateways; how many gateways would be required to relay to the management servers in the main domains management group?
3. With the number of Linux servers in the untrusted domain is it better to install a separate management group there?
Thanks, for any advice in dealing with the above scenario.
--SG

Hi There,
Microsoft recommends you to place all the management servers in the same data center so if 1 goes down the other comes to know about it asap.
If you place it in another location then fail over may happen late.
Also you have mentioned to place the management servers in another domain, Which is possible but you need to have trust and permission stuff which is a very hectic work.
So i would suggest you to place gateways as it will help in compression if the network bandwidth is low between the domains and sites.
And based on the MS's Sizing and management options a Gateway server can manage 100 Unix boxes for a dedicated gateway server and 500 per management server on the same domain.
So based on your situation as below:
1300 Linux - Same domain
450 - Different domain
3 Management servers for the main domain for dedicated Linux
1 MS For Windows Agent monitoring.
Totally 4 in a management group for the same domain one.
1 Separate management group with 1 MS will be fine for dedicated Linux monitoring for the 450 servers in the other domain.
If you want to still place gateways then you will need to place 5 Gateway servers which is difficult to manage.
Operations Manager supports the following number of monitored items.
Monitored item
Recommended limit
Simultaneous Operations consoles
50
Agent-monitored computers reporting to a management server
3,000
Agent-monitored computers reporting to a gateway server
2,000
Agentless Exception Monitored (AEM)-computers per dedicated management server
25,000
Agentless Exception Monitored (AEM)-computers per management group
100,000
Collective client monitored computers per management server
2,500
Management servers per agent for multihoming
4
Agentless-managed computers per management server
10
Agentless-managed computers per management group
60
Agent-managed and UNIX or Linux computers per management group
6,000 (with 50 open consoles); 15,000 (with 25 open consoles)
UNIX or Linux computers per dedicated management server
500
UNIX or Linux computers monitored per dedicated gateway server
100
Network devices managed by a resource pool with three or more management servers
1,000
Network devices managed by two resource pools
2,000
Agents for Application Performance Monitoring (APM)
700
Applications for Application Performance Monitoring (APM)
400
URLs monitored per dedicated management server
3000
URLs monitored per dedicated management group
12,000
URLs monitored per agent
50
Refer the below link for the managing details: https://technet.microsoft.com/en-us/library/dn249696.aspx?f=255&MSPPError=-2147217396
Gautam.75801

Can on one domain coexist managed servers for ADF11g and Forms&Reports 11g

Is it possible on one Weblogic Domain to exist both Managed server for ADF 11g and Managed servers for Forms 11g and Reports 11g?
How to install on one Weblogic server these two things? Is it possible and what is recommended in this case?
Thnx in advance!

Hi Rade,
Yes, i think it is possible. In my case I have one Weblogic Server Domain with 3 Managed Server,one for deploy application and the others are the Forms & Reports 11g.
For that you have to install Fusion Middlware 11g.
For ADF 11g i think you have to install Oracle Fusion Application.
Edit:
Please read the note: Installing ADF 11.1.1.3 Runtime into WebLogic 11gR1 Patchset 2 (10.3.3) [ID 1094153.1]
Hope this help
Regards
Edited by: scapy on 6/Out/2011 3:14

Creating Weblogic domain with Admin Server and managed servers on different

I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.

Whilst the method that Lawrence gives can result in a domain that is perfectly functional, it is a method that can result in errors as you are having to enter the same information twice. Also you will create two admin servers, as the second domain creation will have the console added to it on the renamed admin server and this will give issues.
The best method to create a domain spamming multiple physical machines, is to create the domain with all the components on the first machine. This means planning the domain and making sure all components are added once; so having the information about the domain written out is wise. Ensure that the WLS software is installed in the same path on each machine before starting.
Then copy the domain that you have created from one machine to the other, keeping the same paths. You can simply copy (I've used this method multiple times without issue) but the supported way would be to use the WLST PACK and UNPACK methods. These create and extract domains from templates. Some more information on these is given here -> http://docs.oracle.com/cd/E13179_01/common/docs100/pack/intro.html#wp1069056

Error : Running Managed Servers in a cluster

Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick

Hi,
<font color=red>OPTION-A)</font>
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
<font color=red>OPTION-B)</font>
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 10:55 PM

Unable to start the Managed servers OIM and SOA after starting the Weblogic

Hi,
We are unable to start the any manager servers after starting the weblogic Admin Server.
We are getting the below error after trying to start the OIM or SOA managed servers.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
Please help us to start the managed servers in the weblogic 10.3.5.
Thanks.

We are getting the below errors after starting the Admin server and Managed servers.
Admin Server:
<Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
Managed Server:
Starting WLS with line:
/opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have to find out why the port 5555 is in listening mode after starting the Admin server.

I am unable to start Managed Servers through Weblogic AdminConsole

Hi,
We are using Weblogic 10.3.1.0 version.
Totaly 4 Managed Severs
1 Admin Server
with Nodemanger.
In Admin Console When ever we going to Stop the Manged Servers.
1. Environment ----- > Servers ---- > Control ----------- > Mananged Server 1 -----------> Force shutdown
2. Then click refresh button ---- showing "FAILED_NOT_RESTARTABLE"
3. after that when ever we going to start the Managed Server in Admin console
First its Showing ----- Starting
and next its showing ----- FAILED_NOT_RESTARTABLE
4. its not coming to Running State.
In Logs
Domain log
-----------> <1273141345460> <BEA-000450> <Socket 8 internal data record unavailable (probable closure due idle timeout), event received 17>
####<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280738> <BEA-000396> <Server shutdown has been requested by weblogic>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <Cluster> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280844> <BEA-000163> <Stopping "async" replication service>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281061> <BEA-000365> <Server state changed to ADMIN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281064> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <Server> <ukirt156> <twpserver1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1273143281113> <BEA-002607> <Channel "Default" listening on 172.21.149.168:7003 was shutdown.>
####<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <ukirt156> <AdminServer> <[ACTIVE] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273143390016> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
AdminServer log
<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 11:57:33 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 12:07:02 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
ManagedServer Log
<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler pause
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
<06-May-2010 11:54:54> <Debug> <NodeManager> <Waiting for the process to die: 19316>
<06-May-2010 11:54:54> <Info> <NodeManager> <Server was shut down normally>
<06-May-2010 11:54:54> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
NodeManager Log
<06-May-2010 11:54:54> <Info> <twp_domain> <twpserver1> <Server was shut down normally>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Boot identity properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Startup configuration properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/startup.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00020">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Starting WebLogic server with command line: /appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/bin/java -Dweblogic.Name=twpserver1 -Djava.security.policy=/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://ukirt156:7001 -Djava.library.path="/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386/jrockit:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/../lib/i386::/appl/nsm/CA/UnicenterNSM/lib:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386/client:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386:/appl/nsm/CA/SharedComponents/ccs/dia/dna/lib:/appl/nsm/CA/SharedComponents/ccs/dia/lib:/usr/lib:/opt/CA/CAlib:/appl/nsm/CA/SharedComponents/lib:/appl/nsm/CA/SharedComponents/Csam/SockAdapter/lib:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/data/share/package/twp/WEB-INF/lib/ojdbc14.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.system.BootIdentityFile=/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7091,ssl=false,authenticate=false -Xms=1200m -Xmx=1200m -Xverbose:gc,gcpause -Dreflexis.scheduler=true -Dreflexis.server=twpserver1 -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Doracle.jdbc.V8Compatible=true weblogic.Server >
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Working directory is "/appl/weblogic/scripts">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00021">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
<06-May-2010 11:56:29> <Info> <twp_domain> <twpserver1> <Server failed during startup so will not be restarted>
<06-May-2010 11:56:29> <Warning> <Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:332)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Server logs
<06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
[JRockit] Management server started on port 7091, ssl=false, authenticate=false.
<06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception <06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the
<06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
<06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Note: if i start the manged servers through WLST script its working fine.
[twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
Please provide the solution, how to solve this issue.
Thanks
SRK

Just at first glance, it seems as though you have one or more configuration issues, perhaps inconsistencies between the node manager server configuration files and the domain's config.xml
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
implies that tmp_domain is configured in /appl/weblogic/oracle/middleware/user_projects/domains, (which is the default from the configuration wizard). However, the node manager and server output logs make it seem like it's trying to use a domain in the directory /appl/weblogic/scripts. Not sure how that happened, perhaps you had two domains? Perhaps copied or moved the domain files? Something else?
In any case, start by checking out your nodemanager.domains file and ensure that it reflects your intended domain directory.

Domain log of managed servers

Similar Messages

Maybe you are looking for