Server Starting Issue

Sever Starting issues

There could be many starting issues few of them I am listing here. Starting issue can be categoriged as

1. Admin Server cannot start

2. Managed Server cannot start

1. Admin Server connot start

BEA-090870 Security issue while starting Admin Server

Exception:

####<Oct 28, 2010 3:38:41 AM PDT> <Error> <Security> <Unknown> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1288262321492> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.

weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError

at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)

Solution

Amazon.com WidgetsThe workaround is suggested as 'Please login to the Database and then run the below SQL file to execute different queries mentioned in this file: Suppose Database User Login is “weblogic” then login to Database with this credential and run the script under $BEA_HOME\wlserver_10.3\server\lib\ rdbms_security_store_oracle.sql Then restart your AdminServer'.

Sometime this issue raised with IP address doesnot matches to FQDNS (Fully Qulified Domain name server).

2. Managed Server cannot start

BEA-000362

When you got this error it is related to managed server configuration it might araised when you newly configured a domain.

<Oct 2, 2011 3:51:56 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: [Management:141247]The configuration directory /home/wluser/domains/myprod/config does not exist and the admin server is not available.

at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:200)

at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)

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:802)

at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:489)

at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)

at weblogic.Server.main(Server.java:67)

This Exception trace tells you what to do. Read the first line carefully,

<Mar 30, 2009 2:56:49 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

java.net.UnknownHostException: mywebhostname.com: myhostname.com

at java.net.InetAddress.getAllByName0(InetAddress.java:1128)

at java.net.InetAddress.getAllByName0(InetAddress.java:1098)

at java.net.InetAddress.getAllByName(InetAddress.java:1061)

Hence ping from all web machines before you go for starting managed server first time in a domain to Admin server is running on machine.

1. There could be DNS names in the routing table which are unresolvable

2. IP address can be accessable when you access with FQDNS it doesnot work means DNS names not resolving at your machine.

3. One more issue there could be when one of the router restrarted in your network, there may be possibility of DNS clash. Such as same name can be assigned to two IP addresses.

Unix command identifies that there is a problem when the managed server connecting the admin server first time the machine is not able to lookup the remote machine where admin server is running.

~]$ getent wlapp1vip1.mycomp.com

13.0.41.51 wlapp1vip1.mycomp.com

13.0.41.0 wlapp1vip1.mycomp.com