Weblogic admin console problem

[bcme10]

We've been having a problem with our admin console staying up. After starting the admin console process, we'll tail the log file to make sure it comes up ok. But as soon as we discontinue the tail, the admin console goes down and we have to restart it.

We made some modification to the config.xml recently, but we tried puting those changes back but we are still experiencing the same proplem.

Any ideas? Thanks in advance/

bc

 

[roylec]

A couple of questions first.

1) I consider the Admin Console to be the HTML GUI that connects to the Administration Server Process. Do you mean this GUI or the Server Process.

2) Can you show the tail command you are using please? (re-test it then post the same commands you used.)

 

[bcme10]

1) I am refering to the GUI.
2) basically, "tail -f /opt/logs/adminlog"

Thanks in advance.

bc

 

[z28sarefun]

Are you starting the server on the command line? ie:
$startWebLogic.sh &
-or-
$startManagedWebLogic.sh <myserver>

http://admin.server

&

If so, try writing a script that calls the server from a shell environment other than your own. Something like:

#!/bin/sh

cd <path to file>

./startManagedWebLogic.sh <myserver>

http://admin.server

>> <stdout_log_name> 2>&1 &

I guess you could type all that at a prompt but it's a pain.

This basically sends all output to the filename you specify and backgrounds the process. This way you can also leave the server running when you logout.

Make sense? (sometimes I don't)

Brian

 

[bcme10]

Yes, we have scripts in place that start the managed servers and the admin console in the background piping any output to text files. The problem is sometimes the admin console just dies and we have to restart it.

Any ideas what might cause the admin console to fail unexpectedly?

Thx

 

[z28sarefun]

So it dies when you discontinue the tail or it dies randomly with no corresponding action on your (the SAs) part?

Also, do you use caching realms?

B

 

[roylec]

Can you post the config.xml you use for this domain please?

 

[bcme10]

Figured it out.
The console stays up in the background if we logout completely with the exit command. If we just close out the telnet window the weblogic script that was run would fail even though we started it with the &. basically,

nohup startWeblogic.sh > /logs/admin.out &

Wierd.