Admin Server client not contacting server its running on

Hi All,
I've got an OS X server that for some reason ( probably due to me pratting around) has decided not to have a working server admin prog. I can fire up the client program and point it at any of the IP addresses that the server is listening on and then you get an error message basically saying that the server admin daemon is not contactable.
an ls -lrt in /var/log to see if anything shows up gives me
Jul 31 07:57:38 britten com.apple.SecurityServer[77]: Succeeded authorizing right com.apple.server.admin.streaming by client /usr/sbin/QuickTimeStreamingServer for authorization created by /System/Library/CoreServices/ServerManagerDaemon.bundle.
in secure.log
and Jul 31 07:58:46 [152] kCGErrorIllegalArgument: _CGXCacheMergeShmem: Invalid mergeShmemID (461)
in windowserver.log ... but that keeps happening
I'm running osx server 10.5.7 and my server admin prog is 10.5.3(2789.1.1)
So ...
1). How can i find out if the back end daemon is running
2). what port(s) does it listen on
3). How can I turn on some logging to see what's happening when I run serve admin
4). Any other tips as to how to find out why its not working
Rgds
Alex

Just as an update, I tried upgrading the server admin tools to 10.5.7 to match the OS release. Although the install seemed to work i.e. I receive an install completed successfully message " when i click on the "About Server Admin" I still see the version number as 10.5.3 I've tried this under my account which has admin rights and form the root user, both with the same result.
Looking in the Server Admin directroy, i can see the timestamps associated with some directories have changed while other things haven't. Could I be running bits of 10.5.3 and bits of 10.5.7?
Rgds
Alex

Similar Messages

How to find what port the admin server is running

how can I find out what port the admin server is running on a server?
thanks,

Hi
Go to your domain root folder/config and open config.xml file in any editor. Search for the name of the admin server which is typically like AdminServer and under this tag see if you have a tag by name <listen-port>. If yes, then you should see the port number. If not, it means it is running at default port of 7001.
If you have admin access, i hope when you login you will be giving url like http://adminhost:adminport/console. Now this adminport is the port on which admin server is running. If not, then check config.xml file.
Thanks
Ravi Jegga

How to start managed server from admin server both running

I have an admin server on one machine and created a managed server on different
machine, I am not able to start managed server from either machine. When I used
the admin server machine to start the managed server remotely I got this message
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server (running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Thanks.

"fkeita" <[email protected]> wrote in message
news:[email protected]...
>
I have an admin server on one machine and created a managed server ondifferent
machine, I am not able to start managed server from either machine. When Iused
the admin server machine to start the managed server remotely I got thismessage
>
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
>
Try running netstat to see whether another process is actually running at
the given address/port.
Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
the box to see whether the ips addreses are correct.
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server(running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
ed during initialization. Exception:java.lang.SecurityException:Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>Seems to be some issue with security credentials.
Try running the manageed server directly (as sort of admin) by not passing
the admin server url and bringing it just like an admin server.
See if this works. If it works, then soemthing wrong in the way the admin
server is receiving the request/security credentials from managed server.
Also make sure both managed and admin servers are on the same patch/service
pack level.
-Sabha

How to start managed server from admin server both running on separate machines

          I have an admin server on one machine and created a managed server on different
          machine, I am not able to start managed server from either machine. When I used
          the admin server machine to start the managed server remotely I got this message
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
          ogic Managed Server "managedserver3" for domain "admindomain">
          <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
          create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
          java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
          a
          ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
          to
          bind to any port such that it is not reachable from the console.>
          <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception>
          When I tried to connect managed server from its machine to admin server (running
          on separate machine ) I got this error
          Starting WebLogic Server...
          Connecting to http://fkeita:7001...
          <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
          ng using realm myrealm.>
          <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
          ed during initialization. Exception:java.lang.SecurityException: Authentication
          for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
          initialize the server: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          >
          The WebLogic Server did not start up properly.
          Exception raised:
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Reason: Fatal initialization exception
          Throwable: java.lang.SecurityException: Authentication for user system denied
          java.lang.SecurityException: Authentication for user system denied
          at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          SecurityServiceManager.java:978)
          at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          erviceManager.java:1116)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          at weblogic.Server.main(Server.java:31)
          Thanks.


          I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
          server, but it did not work, and got error messages. Error messages are posted
          on my first posting.
          "pankaj" <[email protected]> wrote:
          >Use the startManagedWeblogic.cmd / .sh script to start your
          >Managed/Clustered servers
          >
          >
          >"fkeita" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I have an admin server on one machine and created a managed server
          >on
          >different
          >> machine, I am not able to start managed server from either machine.
          >When I
          >used
          >> the admin server machine to start the managed server remotely I got
          >this
          >message
          >>
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
          ><Starting WebL
          >> ogic Managed Server "managedserver3" for domain "admindomain">
          >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
          ><Unable to
          >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
          >port:
          >8002.
          >> java.net.BindException: Cannot assign requested address: JVM_Bind
          >Perhaps
          >the
          >> a
          >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
          >port
          >8002.>
          >>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
          >failed
          >> to
          >> bind to any port such that it is not reachable from the console.>
          >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception>
          >>
          >> When I tried to connect managed server from its machine to admin server
          >(running
          >> on separate machine ) I got this error
          >>
          >> Starting WebLogic Server...
          >> Connecting to http://fkeita:7001...
          >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
          >initializi
          >> ng using realm myrealm.>
          >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
          ><Server fail
          >> ed during initialization. Exception:java.lang.SecurityException:
          >Authentication
          >> for user system denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
          ><Unable to
          >> initialize the server: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> >
          >>
          >***************************************************************************
          >> The WebLogic Server did not start up properly.
          >> Exception raised:
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >> Reason: Fatal initialization exception
          >> Throwable: java.lang.SecurityException: Authentication for user system
          >denied
          >> java.lang.SecurityException: Authentication for user system denied
          >> at
          >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
          >> SecurityServiceManager.java:978)
          >> at
          >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
          >> erviceManager.java:1116)
          >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
          >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
          >> at weblogic.Server.main(Server.java:31)
          >>
          >> Thanks.
          >
          >

Weblogic admin server stops running after a while

Hi,
we have a distributed environment 11.1.2. On the server where we have weblgic admin server running, it seems to stop running everytime I disconnect from the server. I end up starting it everytime I login to the server. How can I keep it running all the time?Doesn't it start as part of the 'start EPM' script?
here is the error I am getting:
Caused By: javax.management.RuntimeMBeanException: ODL-52055: The handler 'epmcs
s-handler' is already defined.
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean
.doInvoke(OracleStandardEmitterMBean.java:885)
at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMB
eanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:94)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartIntercep
tor.internalInvoke(MBeanRestartInterceptor.java:116)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
Truncated. see log file for complete stacktrace
Caused By: java.lang.IllegalArgumentException: ODL-52055: The handler 'epmcss-ha
ndler' is already defined.
at oracle.as.management.logging.impl.LogConfig._updateHandler(LogConfig.
java:564)
at oracle.as.management.logging.impl.LogConfig.addHandler(LogConfig.java
:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
Truncated. see log file for complete stacktrace
>
<Dec 22, 2010 5:11:46 PM EST> <Warning> <RMI> <BEA-080003> <RuntimeException thr
own by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.m
anagement.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.St
ring;Ljavax.security.auth.Subject;)
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException:
ODL-52059: The logger 'oracle.EPMREG' already has handler 'epmreg-handler'..
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException:
ODL-52059: The logger 'oracle.EPMREG' already has handler 'epmreg-handler'.
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(Default
MBeanServerInterceptor.java:856)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBe
anException(DefaultMBeanServerInterceptor.java:869)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:838)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349)
Truncated. see log file for complete stacktrace
Caused By: javax.management.RuntimeMBeanException: ODL-52059: The logger 'oracle
.EPMREG' already has handler 'epmreg-handler'.
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean
.doInvoke(OracleStandardEmitterMBean.java:885)
at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMB
eanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:94)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartIntercep
tor.internalInvoke(MBeanRestartInterceptor.java:116)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
Truncated. see log file for complete stacktrace
Caused By: java.lang.IllegalArgumentException: ODL-52059: The logger 'oracle.EPM
REG' already has handler 'epmreg-handler'.
at oracle.core.ojdl.logging.config.LoggingConfigurationDocument.addHandl
erToLogger(LoggingConfigurationDocument.java:644)
at oracle.core.ojdl.logging.config.LoggingConfigurationDocument.addHandl
erToLogger(LoggingConfigurationDocument.java:283)
at oracle.as.management.logging.impl.LogConfig._updateLogger(LogConfig.j
ava:541)
at oracle.as.management.logging.impl.LogConfig.updateLogger(LogConfig.ja
va:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Dec 22, 2010 5:11:46 PM EST> <Warning> <RMI> <BEA-080003> <RuntimeException thr
own by rmi server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.m
anagement.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.St
ring;Ljavax.security.auth.Subject;)
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException:
ODL-52059: The logger 'oracle.EPMCSS' already has handler 'epmcss-handler'..
javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException:
ODL-52059: The logger 'oracle.EPMCSS' already has handler 'epmcss-handler'.
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(Default
MBeanServerInterceptor.java:856)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBe
anException(DefaultMBeanServerInterceptor.java:869)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:838)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349)
Truncated. see log file for complete stacktrace
Caused By: javax.management.RuntimeMBeanException: ODL-52059: The logger 'oracle
.EPMCSS' already has handler 'epmcss-handler'.
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean
.doInvoke(OracleStandardEmitterMBean.java:885)
at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMB
eanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:94)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartIntercep
tor.internalInvoke(MBeanRestartInterceptor.java:116)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterce
ptor.doInvoke(AbstractMBeanInterceptor.java:245)
Truncated. see log file for complete stacktrace
Caused By: java.lang.IllegalArgumentException: ODL-52059: The logger 'oracle.EPM
CSS' already has handler 'epmcss-handler'.
at oracle.core.ojdl.logging.config.LoggingConfigurationDocument.addHandl
erToLogger(LoggingConfigurationDocument.java:644)
at oracle.core.ojdl.logging.config.LoggingConfigurationDocument.addHandl
erToLogger(LoggingConfigurationDocument.java:283)
at oracle.as.management.logging.impl.LogConfig._updateLogger(LogConfig.j
ava:541)
at oracle.as.management.logging.impl.LogConfig.updateLogger(LogConfig.ja
va:201)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
Edited by: 784749 on Dec 22, 2010 2:14 PM

I've never seen this and we've been running 8.1.5 for a while. Have you tried dumping threads to see what the admin server is doing? On UNIX, run 'kill -QUIT <admserv_pid>'. Can't remember if/how this can be done on Win32. I believe Console requests use the weblogic.admin.HTTP execute queue and it only has two threads. Could be that something is blocking those threads leading to this.
I would also look into why your admin server takes 2 minutes to discover your managed servers. That seems unseemly long to me. Mine takes a few seconds at most. Since the Console does cause the admin server to talk to the managed servers, these two things might be related. Maybe you've got some kind of network/DNS lag that could be eliminated.

Admin console is not accessible even when the Admin server is running

Running Weblogic 10.3.2 on RHEL 5.x and EM -11.0.1.0
Found the following errors in the server logs
<May 26, 2010 1:59:35 PM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'FMW Welcome Page Application [Version=11.1.0.0.0]'.
java.lang.IllegalArgumentException: URI is not hierarchical
at java.io.File.<init>(File.java:363)
at oracle.as.jmx.framework.util.MBeansXmlServletContextListenerSupport.getRelativePathsToMBeansXmlFiles(MBeansXmlServletContextListenerSupport.jav
There is a deployment problem with the welcome page.
Could not access the admin console.
Reinstalled everything but getting the same error
Thanks in Advance
Anurag

yes solved.......there was firewall enabled which was not allowing the https traffic to flow.
Firewall disabled and the admin console was accessible.
Thanks!!

Admin server running into issues in SOA.

Hi All,
Can anyone help me.
I have recently installed Oracle SOA suite on Linux box. While I was running the Admin Server I am running into Some issues. Though Admin Server is running fine but all that I am running out of memory because of the Logs. Can anyone help me find the issue and solve. I can do some other arrangements to save memory. IF you could help me for any issue I would be so happy. One more thing SOA suite installed on Admin server instead soa_server1 or soa_server2. I still need to SOA-infra setup onto soa_server1 or soa_server2(on different remote machines) [if this info could help also.]
This issue is repeating every 5 secs.
<Jul 16, 2013 5:35:21 PM EDT> <Error> <oracle.soa.mediator.common.listener> <BEA-000000> <DBLocker caught exception while retrieving locked messages. Will retry retrieval after 2 seconds
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "TENANT_ID": invalid identifier
Error Code: 904
Call: SELECT CASE_ID, CONTAINER_ID, DUMMY1, MSG_ID, COMPONENT_DN, OPERATION, CREATION_DATE, PRIORITY, COMPONENT_STATUS, QNAME_LOCAL_PART, CASE_INFO, QNAME_NAMESPACE, LOCK_TIME, SOURCE_URI, TENANT_ID, INSTANCE_CREATED, IS_EVENT, STATUS FROM MEDIATOR_DEFERRED_MESSAGE WHERE (((STATUS = ?) AND (LOCK_TIME = ?)) AND (CONTAINER_ID = ?))
        bind => [1, 2013-07-16 17:23:12.814, A8424220EE5D11E2BF9C6D1C72885086]
Query: ReadAllQuery(oracle.tip.mediator.common.persistence.MediatorDeferredMessage)
        at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:305)
        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:614)
        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:468)
        at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:447)
        at oracle.toplink.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:117)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:250)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:583)
        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:2500)
        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:2458)
        at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:467)
        at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:874)
        at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:679)
        at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:835)
        at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:445)
        at oracle.toplink.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2265)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1079)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1063)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1037)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1009)
        at oracle.tip.mediator.dispatch.db.DBAccess.getMessageFromDB(DBAccess.java:800)
        at oracle.tip.mediator.dispatch.db.DBAccess.getDeferredMessages(DBAccess.java:821)
        at oracle.tip.mediator.dispatch.db.DeferredDBLocker.getLockedMessages(DeferredDBLocker.java:153)
        at oracle.tip.mediator.common.listener.DBLocker.getLockedMessages(DBLocker.java:173)
        at oracle.tip.mediator.common.listener.DBLocker.run(DBLocker.java:93)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "TENANT_ID": invalid identifier
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)
        at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947)
        at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
        at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823)
        at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671)
        at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:135)
        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeSelect(DatabaseAccessor.java:814)
        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:540)
        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:468)
        at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:447)
        at oracle.toplink.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:117)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:250)
        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:583)
        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:2500)
        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:2458)
        at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:467)
        at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:874)
        at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:679)
        at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:835)
        at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:445)
        at oracle.toplink.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2265)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1079)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1063)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1037)
        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1009)
        at oracle.tip.mediator.dispatch.db.DBAccess.getMessageFromDB(DBAccess.java:800)
        at oracle.tip.mediator.dispatch.db.DBAccess.getDeferredMessages(DBAccess.java:821)
        at oracle.tip.mediator.dispatch.db.DeferredDBLocker.getLockedMessages(DeferredDBLocker.java:153)
        at oracle.tip.mediator.common.listener.DBLocker.getLockedMessages(DBLocker.java:173)
        at oracle.tip.mediator.common.listener.DBLocker.run(DBLocker.java:93)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Thank you all.

Hi Ravi,
You are much appreciated for your valuable time and knowledge..
Then delete old domain. Its corrupted. You can clean it by manually updating jdbc datasource files under config/jdbc folder. But I will NOT recommend this. Just delete this domain folder and from user_projects/appliations also delete the folder with same domain name.
Create a brand new domain using config wizard. Select SOA or BPM whichever you want, and also Enterprise Manager. Then at database, carefully select 11.7 Schemas that you created earlier.
Though I have not created a new domain. (still Ravi is correct)
Issues were resolved by updating the new RCU schema with latest version of RCU 11.1.1.7.
Here What I did is ran the rcu.bat on my local and connected to remote DB.created new schema for each components namely soa-infra,orabam,owsm,MDS. with a new prefix.
I did not drop the previous schema for SOA.
went to *Domain-home*/config/jdbc/
took the back up for all the *.xml files excluding read.xml(anyway its just an info file).
Now edited the schema component. Someone might change their schema component password. but my suggestion is not to give any new passwords to the schema components while creating new RCU schema for SOA.
What I did is changed the component passwords (I know how to mess up and also know how to fix if it's messed up) and ended up with errors.
So I have now started the server with the command
./startWebLogic.sh -Dweblogic.configuration.schemaValidationEnabled=false
Still I had errors coming up. But I least bothered about the errors because these errors can be solved once get to know what you are doing.
My server started. Happy then
Went to admin-url:port/console
then Home>Summary of JDBC Data Sources
next lock & edit
select each jdbc component and changed the password and confirm password for each
then save each time for each next activate the changes.
(as I changed all components passwords like <password-encrypted>asdl;lasdfadf=<password-encrypted/>   to <password>welcome1=<password/> in each *.xml file at *domain-home/config/jdbc*)
I have restarted the Admin server from Command prompt. Expecting that I was doing correct.
Succeeded. I did not believe that I have seen not even a single error.
My sincere request that don't mess up with any *.xml file if you are not sure and make sure to take a back up
Thank you.
Thanks a lot.
-Seshikanth

Weblogic 8.1 managed server unable to contact Admin server

I have a strange issue here.
I have admin server on Linux Machine A
Managed server on Linux Machine B.
When i try to start managed server on Machine B, i get the following error.
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
But i know for sure that Admin server is running on that port 7100 for sure.
It has been for the last 3 years.
To see if Machine B and Machine A have network issues, i did telnet.
From Machine B: i typed the following
telnet MachineA 7100
Connected to MachineA.
Escape character is '^]'
The above telnet command tells us that no network issues exist.
After a few tries, the managed server contacts to admin server and comes up.
This is not a one time thing.
I saw this behavior many times.
How should i resolve this?
Edited by: gvamsius on Feb 12, 2009 1:23 PM

Every thing is configured fine.
Nothing wrong with Configuration.
This domain has been running for the past 3 years.
Recently, i found something interesting in admin server logs, when i try to start the managed servers.
I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
Here is the log snippet when managed server A contacts Admin server and starts up successfully.
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <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 Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Here is the log snippet when managed server B contacts Admin server and does not start.
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' 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 Managed Server B.>
####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
The difference as you can see here is that managed server starts up only when Admin Server does the following
<*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers?

Not able to boot OES admin server

Hi,
I am not able to boot the admin server after running the install-ales-schema.bat. It gives Arme not Ready Exception.
<Apr 24, 2010 9:03:12 PM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: Weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed i
n such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions. weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:991)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
Edited by: user12057577 on Apr 24, 2010 3:17 AM

Hi,
Can you mention the steps you used before running the ales_install script? Which WLS version are you using for Admin Server? Is it CP3 or CP4 patched?

Can Managed Server self-tuning its performance without Admin Server?

I have an web application deployed on a managed server.
My observation is:
- If the Admin Server is not running, the application will keep accepting incoming external http requests and delayed the processing of them.
- If the Admin Server is running, the application will start the processing soon after the incoming requests arrive.
Can any body explain the reason behind it? Only default work manager is used in the above case.
Thanks

This seems a strange behaviour.
How is structured the application (app/webApp/ejbs/...)?
How is targetted ? The target is only on the managed instance?
Bye
Mariano

BEA-141151 The admin server could not be reached at ...

I have been at this for 3 days now... I created a new ManagedServer, but I'm not able to make it connect to the Admin server.
The Admin server is running and listening on port 5306. I can connect to the Admin Console (web).
I can also connect to the Admin server via WLST, using this command: connect('operator','operator01','t3://localhost:5306')
However, when I try to run the managed server from a script, it does not see the Admin server. This is the command I run:
java -Dweblogic.Name=ManSer1 -Dweblogic.management.server=t3://localhost:5306 -Dweblogic.RootDirectory=<path to my domain> weblogic.Server
This is the error I get:
<BEA-141151> <The admin server could not be reached at http://localhost:5306.>
I believe it's trying to connect using "http", because I've never actually connected in the past. Here is a website explaining this: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13749/weblogicserver.htm#i1031832
Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.
I'm not sure what else to try... Firewalls are not in play, since this is traffic moving around on the local machine. I'm running on SunOS. Weblogic is version 9.2 MP3.
Appreciate any help.

Is the NodeManager , AdminServer running ?The NodeManager is not running. Is it required?
Also, I haven't closed the command prompt.
I noticed the issue when I tried to deploy my project. Connected to Localhost/7001 but in the deploy project window, I dont see any soa_server instance
running. Also, in the console the soa_server status is shutdown.

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?

Cloned OMS - WebLogic Admin Server not available....

Greetings,
We are working our way through an active active R4 OMS setup, and we just successfully cloned oms1 to oms2 via cloud control, and executed the post install steps. We now need to access each of the OMSs WebLogic Admin Server Console to confirm LDAP settings, and the oms2 WebLogic Admin Server Console is unavailable. The oms2 clone has the same WebLogic Admin Server details as oms1 (see below).
Is that by design, i.e. only one WebLogic Admin Server Console with two load balanced OMSs?
Which files do we need to edit on oms2 to get oms2's WebLogic Admin Server on-line?
oms1:
/u01/app/oracle/product/middleware_r4/oms/bin/emctl status oms -details
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Admin Server is RUNNING
oms2:
WLS Domain Information
Domain Name            : GCDomain
Admin Server Host      : oms1.mastec.com
Admin Server HTTPS Port: 7102
Thank you,

The WLS admin server only exists on the first OMS host. Usually an SLB is used for load balancing.
For information on HA (High Availability) solutions, see:
http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_intro.htm#EMADV9611
Regards,
- Loc

6.0 cluster startup without the admin server...

Is it possible to start a WL6.0 cluster without the admin server being up
          and running? If not, are there any workarounds that eliminate the admin
          server as a single point of failure?


          I have same questions.
          1.The admin server's primary task is up the cluster?And if admin server is down
          that can't affect the cluster running.
          2.Is it right when the cluster is working,the useful ip is admin server's ip?For
          example,admin 10.10.10.1,cluster1 10.10.10.2,cluster2 10.10.10.3,the only useful
          ip is 10.10.10.1 in the cluster.
          3.Is it correct that because the only useful ip is 10.10.10.1,therefor my client
          access the cluster from 10.10.10.1?
          When my admin server is down,then my system will be down.
          4.which is the dispatch in the cluster system ?
          my step of configuration of th cluster:
          1.add two managed servers to admin server and edit startweblogic.cmd;
          2.config cluster.(admin server address 10.10.10.1:8168,cluster address 10.10.10.2:7001,10.10.10.3:7001),multicast(237.0.0.1)
          please help explain these questions!thanks a lot!
          2.
          Kumar Allamraju <[email protected]> wrote:
          >Sorry if i wasn't clear, what i mean to say is
          >
          >When you first start the managed server's you have to have admin server
          >up &
          >running.
          >Admin server can go down when cluster is running, but then you can't
          >add servers
          >to cluster
          >and I think its ok to have it that way from administration point of view.
          >
          >Yes, there's no facility to achieve single point of failure for admin
          >servers.
          >
          >--
          >Kumar
          >
          >
          >
          >William Wallace wrote:
          >
          >> I may be misreading that page, but it doesn't really tell me how to
          >> successfully start to start a managed server is the admin server is
          >down. If
          >> you run the managed server script you get an "cannot connect to admin
          >> server" exception if the admin server is not running. Now, I imagine
          >that I
          >> could script something up to restart the admin server if it's down,
          >but that
          >> doesn't protect me from hardware failure.
          >>
          >> "Kumar Allamraju" <[email protected]> wrote in message
          >> news:[email protected]...
          >> > http://e-docs.bea.com/wls/docs60/adminguide/startstop.html#1035064
          >> >
          >> > --
          >> > Kumar
          >> >
          >> >
          >> > William Wallace wrote:
          >> >
          >> > > Is it possible to start a WL6.0 cluster without the admin server
          >being
          >> up
          >> > > and running? If not, are there any workarounds that eliminate the
          >admin
          >> > > server as a single point of failure?
          >> >
          >

When the Weblogic 6.1 Admin Server crashes.

Hi there!
I'm using weblogic server 6.1 sp1 on windows 2000. I have one
adminserver en a two managed servers. The two managed server are a
cluster.
My question is :
Can i rebuild the admin server on an other machine when the machine
where the admin server is running on has crashed and i can't start up
the machine.
If that is possible please tell me how?
Kind regards,
Ido Dijkstra
(J2ee Develloper)

Mark Hansen <[email protected]> wrote:
I've installed WebLogic 6.1 (sp/3) on a Windows/2000 machine, and am
trying to
set up the administration server to run as a system service.
I've played with the arguments to the installNtService.cmd script that
came with WebLogic,
but can't get the service to run. When I attempt to start the service,
I get the following error:
Server installed as NT Service with incorrect password for user system.
Unable to initialize the server: 'Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system
denied; contact your administrator to correct NT Service attributes
Note that I was able to install the Node Manager as a system service,
and it starts up fine.
Can anyone please tell me what I'm doing wrong?I found that adding the "-password <password>" to the
beasvc.exe command in the "installNtService.cmd" script
resolved the problem.
Note that when I looked at the arguments for the beasvc.exe
program, the -password argument was not listed ;-(
>
Thanks,

Admin Server client not contacting server its running on

Similar Messages

Maybe you are looking for