Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Oracle Weblogic Server (MOSC)

Problem with "<BEA-000365> <Server state changed to FORCE_SUSPENDING>"

Feb 5, 2014 6:15AM edited Feb 12, 2014 12:00PM in Oracle Weblogic Server (MOSC) 2 commentsAnswered

Hi,

I am having problems booting a weblogic server that works fine until two weeks ago. For the weblogic server and I get the following message in the server logs:

<Feb 5, 2014 11:27:38 AM CET> <Notice> <Cluster> <BEA-000102> <Joining cluster SCRITTURA_CLUSTER on 239.192.0.0:7001>

<Feb 5, 2014 11:27:38 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>

<Feb 5, 2014 11:27:38 AM CET> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

<Feb 5, 2014 11:27:42 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>

<Feb 5, 2014 11:27:42 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>

<Feb 5, 2014 11:27:42 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month