Link to home
Start Free TrialLog in
Avatar of SANJAY HALDAR
SANJAY HALDARFlag for India

asked on

How to identify if any network issue caused Weblogic server instance(s) to stuck or go down

Hi Expert,

Need your help to understand, How to identify if any network issue (e.g., change in network switches) caused Weblogic server instances (in cluster) to stuck or go down.
What should be the investigation procedure, any particular log file to look into.

Pls Suggest
Avatar of gheist
gheist
Flag of Belgium image

Yes, AdminServer.log is first place to start. Unless you find ANY log line saying something went down (can be monitoring system outside weblogics') you cannot even call oracle support with "problem" that has no material trail.

Please produce few lines from AdminServer.log around whatvever "stuck go down" event happened.
Avatar of SANJAY HALDAR

ASKER

Thanks gheist for your input, we will look in the AdminServer.log and look for any potential input. Will revert back.
ASKER CERTIFIED SOLUTION
Avatar of gheist
gheist
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial