managed server trying to start as admin server - weblogic.support.install(Archived)

I am trying to start a managed server and get the following error:
weblogic.management.ManagementException: Booting as admin server, but servername, mserver1, does not match the admin server name, adminserver
     at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:61)
     at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
     at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
     at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
     at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:67)
I already have an admin server running.
How do I get the managed server to not try to start as an admin server?
Thanks,
Tom
--
Edited by tcleal at 03/03/2008 3:30 PM 

How did you start the server?
--
Schelstraete Bart
bart#schelstraete.org
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst 

The nodemanager is started as a windows service. I do an nmConnect() then nmStart('adminserver') then nmStart('mserver1'). This is when I get the error message. 

any resolution to this exception? 

I am experiencing the same issue in a Linux environment.
Has anyone figured out how to resolve this one?

Related

JMX Connectivity Issue for managed servers in a cluster

Hi all,
I have weblogic 12c installed with 1 Admin Server (port 7007) and 3 Clustered Managed Servers (ports 7009, 7010, 7011).
Oracle HTTP Server 11g as front END proxy server to do load balancing on this cluster.
My client EAR runs on cluster and node monitoring EAR runs on Admin Server.
I need to configure each of these managed servers as nodes in the client monitoring application. In-order to do that i need access to JMX port for each of these manages servers.
As per oracle documentation which i have gone through, JMX is auto enabled (am quite not sure about this) on any server created for weblogic domains. So, I am using below URLs to connect to each of the managed servers through my client app by providing the admin console credentials to connect to these nodes.
MS1 : service:jmx:t3://hostname:7009/jndi/weblogic.management.mbeanservers.runtime
MS2 : service:jmx:t3://hostname:7010/jndi/weblogic.management.mbeanservers.runtime
MS3 : service:jmx:t3://hostname:7011/jndi/weblogic.management.mbeanservers.runtime
I am getting below mentioned exception when i try to access the configured node from my client.
In admin server logs:
<Warning> <JMX> <BEA-149504> <The Administration Server was unable to establish JMX Connectivity with the Node3 at the JMX Service URL of
service:jmx:t3://hostname:7011/jndi/weblogic.management.mbeanservers.runtime.>
In my client monitoring application user interface
MSG:
Cannot connect to the server with specified settings
Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
Stack Trace:
com.pega.jmx.ui.util.JMXClientException: Cannot connect to the server with specified settings Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
     at com.pega.jmx.ui.util.JMXClientException.wrap(JMXClientException.java:49)
     at com.pega.jmx.ui.action.AuthenticateAction.execute(AuthenticateAction.java:302)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1480)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:506)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:242)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:216)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:132)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:338)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:221)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3284)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
     at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2163)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2089)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1513)
     at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.Exception: Cannot connect to the server with specified settings Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic.management.mbeanservers'
     at com.pega.jmx.connection.managenodes.WLSJMXRemoteConnection.acquireConnection(WLSJMXRemoteConnection.java:68)
     at com.pega.jmx.connection.managenodes.Node.getMBeanServerConnection(Node.java:405)
     at com.pega.jmx.ui.action.AuthenticateAction.execute(AuthenticateAction.java:142)
     ... 23 more
I am kind of stuck at this point and would need some assistance to fix this issue ASAP.
Can anyone help me out in how to enable JMX (port) for each of the managed server and also how to define specific credentials to access that JMX for monitoring the applications on each of my managed servers.
Thanks in advance,
Revanth 
Hi,
Please make sure that the listen address of the target managed server matches the hostname of the server on which it is running: for example, use the fully qualified hostname in both the properties file and the configuration.
If this helps please mark.
Regards,
Kishore 
Hi Kishore,
I already tried with fully qualified host names and IP addresses as well.
Issue still the same.
Thanks,
RR 
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

Problem starting WL9.2 example server

I cannot start any WL9.2 servers on my Windows box for testing now. I used to be able to run whatever, but I had some issues with our local network and our Sys. Admin fixed something, which might have caused this. I've even went as far as intalling a fresh instance of WL9.2 on my machine, with no luck.
I am getting an odd error, with WL not being able to get the localhost address? Is there a place to set this? What file does WL look in to get the localhost name? (etc\hosts file just has 127.0.0.1 localhost in it.)
java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
     at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:36)
     at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:31)
     at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:91)
     at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:58)
     at weblogic.server.channels.ChannelService.start(ChannelService.java:189)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.net.UnknownHostException: chitwoodce: chitwoodce
     at java.net.InetAddress.getLocalHost(InetAddress.java:1308)
     at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:34)
     at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:31)
     at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:91)
     at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:58)
     at weblogic.server.channels.ChannelService.start(ChannelService.java:189)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) 
kaaash <> wrote:
I cannot start any WL9.2 servers on my Windows box for testing now. I used
to be able to run whatever, but I had some issues with our local network
and our Sys. Admin fixed something, which might have caused this. I've
even went as far as intalling a fresh instance of WL9.2 on my machine,
with no luck.
I am getting an odd error, with WL not being able to get the localhost
address? Is there a place to set this? What file does WL look in to get
the localhost name? (etc\hosts file just has 127.0.0.1 localhost in it.)weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.net.UnknownHostException: chitwoodce: chitwoodce at
java.net.InetAddress.getLocalHost(InetAddress.java:1308) atweblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:34)
atweblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:31)
at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:91) atweblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:58)
at weblogic.server.channels.ChannelService.start(ChannelService.java:189)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) atweblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)You can manually change the config.xml file, and add for example:
<listen-address>127.0.0.1</listenaddress>
Shoud be located together with '<listenport>7001</listenport>'
B
--
Schelstraete Bart
bart#schelstraete.org
http://www.schelstraete.org

lock system id to a specific IP ....thoughts ????

question:
can we prevent the ability for anybody to login to the admin console from a machine
other than the actual machine where the admin server is running on ???
thank you for your time on this ..............any thoughts or ideas ????
Apr 16, 2004 11:37:32 AM EDT Error Deployer The Slave Deployer failed to complete the deployment task wi
th id 21 for the application RxServices.
weblogic.management.ApplicationException: Cannot expand JarFile /usr/local/bea/rxsvcs_devit/weblogic70_sp2/user_projects/RXSERVICES_DEVIT/RxServices.earinto dir /usr/local/bea/rxsvcs_devit/weblogic70_sp2/user_projects/RXSERVICES_DEVIT/./RXSERVICES_DEVIT_MS1/.wlnotdelete/RxServices
     at weblogic.j2ee.J2EEApplicationContainer.throwAppEx(J2EEApplicationContainer.java:2131)
     at weblogic.j2ee.J2EEApplicationContainer.explodeEar(J2EEApplicationContainer.java:2111)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:486)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1062)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
"arun" <arun#xyz.com> writes:
can we prevent the ability for anybody to login to the admin console from a machine
other than the actual machine where the admin server is running on ???I don't believe so. Currently the console uses the same channel as
AS-MS bootstrap so if the console was limited you would't be able to
boot the domain. However, this is an interesting use case, we should
have the machinery to allow this in 9.0.
andy
Is there anything more in the logs? There should be a nested
IOException which is of interest to us.
Anyway, I'd double-check your disk space and permissions.
Also, if you expand the EAR file yourself, and then deploy the
directory, it works, right?
-- Rob
Paul wrote:
Apr 16, 2004 11:37:32 AM EDT Error Deployer The Slave Deployer failed to complete the deployment task wi
th id 21 for the application RxServices.
weblogic.management.ApplicationException: Cannot expand JarFile /usr/local/bea/rxsvcs_devit/weblogic70_sp2/user_projects/RXSERVICES_DEVIT/RxServices.earinto dir /usr/local/bea/rxsvcs_devit/weblogic70_sp2/user_projects/RXSERVICES_DEVIT/./RXSERVICES_DEVIT_MS1/.wlnotdelete/RxServices
     at weblogic.j2ee.J2EEApplicationContainer.throwAppEx(J2EEApplicationContainer.java:2131)
     at weblogic.j2ee.J2EEApplicationContainer.explodeEar(J2EEApplicationContainer.java:2111)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:486)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1062)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Andy,
could you please elloborate more on this .............
you would't be able to boot the domain.does it mean that we can boot the domain if we are on the physical box of the
admin server than ???
please help me understand this ....
-arun
Andy Piper <andy_nospam#xemacs.org> wrote:
"arun" <arun#xyz.com> writes:
can we prevent the ability for anybody to login to the admin consolefrom a machine
other than the actual machine where the admin server is running on???
I don't believe so. Currently the console uses the same channel as
AS-MS bootstrap so if the console was limited you would't be able to
boot the domain. However, this is an interesting use case, we should
have the machinery to allow this in 9.0.
andy

如何将weblogic实例设置到windows service中

请高手指点,我要配置server实例在windows service中。我这有bea的网站参考,http://e-docs.bea.com/wls/docs81/adminguide/winservice.html。我的目的主要是想随着windows的启停weblogic也会随着启停。启停weblogic需要有用户名和密码才可以。
用户名密码更改、日志重定向、dump信息重定向等实际管理操作的内容、步骤也写进去。
高手请帮小弟
帖子经 user10434435编辑过 
在你的域目录下有installService.cmd这么一个文件,打开这个文件根据你的实际情况更改以下参数:
SERVER_NAME
DOMAIN_NAME
WLS_USER
WLS_PW
然后保存运行这个文件就可以了 
我也是这样做的,我也加了日志,延迟启动,我验证service是安装好了,可我启动weblogic——windows service启动报错。***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Management:141137]Managed Server was attempting to boot in Managed Server Independence mode, but was unable to complete the boot process as the Managed Server was unable to locate the cached configuration file: d:\bea\user_projects\domains\abcddomain\.\msi-config.xml'
Reason: weblogic.management.configuration.ConfigurationException: [Management:141137]Managed Server was attempting to boot in Managed Server Independence mode, but was unable to complete the boot process as the Managed Server was unable to locate the cached configuration file: d:\bea\user_projects\domains\abcddomain\.\msi-config.xml
*************************************************************************** 
你加的被管服务器作为windows服务,应该在脚本里把url加上 
url我配置了,set ADMIN_URL=http://localhost:7001
manager server是起来了,可我的admin server没有起来。
=====================================================
这是我的配置
echo off
SETLOCAL
set DOMAIN_NAME=abcddomain
set USERDOMAIN_HOME=d:\bea\user_projects\domains\abcddomain
set SERVER_NAME=abcserver
set PRODUCTION_MODE=true
set ADMIN_URL=http://10.200.24.163:7001
set MEM_ARGS=-Xms40m -Xmx250m
set JAVA_OPTIONS=-Dweblogic.Stdout="d:\bea\user_projects\domains\abcddomain\stdout.txt" -
Dweblogic.Stderr="d:\bea\user_projects\domains\abcddomain\stderr.txt"
call "d:\bea\weblogic81\server\bin\installSvc.cmd"
ENDLOCAL
===========================================
现在出现的错误是:
<2008-12-19 上午09时09分59秒 CST> <Warning> <Management> <BEA-141141> <Failed to connect to an admin server running at http://10.200.24.163:7001. The error message returned is null.
java.net.SocketException: Socket Closed
     at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:177)
     at java.net.Socket.setTcpNoDelay(Socket.java:771)
     at weblogic.net.http.HttpClient.openServer(HttpClient.java:306)
     at weblogic.net.http.HttpClient.openServer(HttpClient.java:355)
     at weblogic.net.http.HttpClient.<init>(HttpClient.java:139)
     at weblogic.net.http.HttpClient.New(HttpClient.java:212)
     at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:140)
     at weblogic.management.Admin.checkAdminServerIsRunning(Admin.java:1669)
     at weblogic.management.Admin.isAdminServerRunning(Admin.java:1741)
     at weblogic.management.Admin.createInstance(Admin.java:1506)
     at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:769)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
     at weblogic.Server.main(Server.java:32)
===================================================
谢谢
帖子经 user10434435编辑过 
从你的报错信息看,你没有启动管理服务server,启动weblogic的顺序是先启动管理服务server当管理服务server是running状态时被管理的服务server才能启动 
管理服务server和配置被管理的服务server在windows serviec上,用ADMIN_URL就可以连接它们吗?不需要配置别的吗?
是否还要配置个依赖属性? 
不需要,只要保证在启动被管理server的时候管理server是running状态就行了 
在配置managed server之前先把Admin server配置好了。managed server基于Admin server起来的。
managed server配置比Admin server多加个ADMIN_URL变量即可。

Weblogic Server failed to start

My weblogic Server failed to start while trying to run an OSB project in eclipse.
This is the error shown while trying to run the server.
There are 1 nested errors:
weblogic.management.ManagementException: Unable to obtain lock on D:\Oracle\Middleware\user_projects\domains\osb_domain\servers\AdminServer\tmp\AdminServer.lok. Server may already be running
     at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
     at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
     at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
     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:803)
     at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
     at weblogic.Server.main(Server.java:67)
Please help me out to solve this? 
Hi,
It seems that your AdminServer is already running. Now if you make sure that it is not already running then you can go to the following path and delete the "AdminServer.lok"
Path: D:\Oracle\Middleware\user_projects\domains\osb_domain\servers\AdminServer\tmp\AdminServer.lok
And then try to start the server again.
This should solve your issue.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Categories

Resources