【从翻译mos文章】Weblogic AdminServer 启动fail,报错"unable to get file lock, will retry"

Weblogic AdminServer 启动fail,报错"unable to get file lock, will retry"

参考原始:

Weblogic AdminServer fails with "unable to get file lock, will retry" error message (Doc ID 1613945.1)

适用于:

Oracle WebLogic Server - Version 8.1 and later

Information in this document applies to any platform.

目标:

WebLogic Server启动时报错:

<Jan 7, 2014 9:09:20 AM PST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Jan 7, 2014 9:09:30 AM PST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Jan 7, 2014 9:09:40 AM PST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Jan 7, 2014 9:09:50 AM PST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Jan 7, 2014 9:10:00 AM PST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

解决方案:

当server开始时间,一.lok创建文件。

本文档$FMW_HOME/servers/SERVERNAME/tmp/SERVERNAME.lok下一个。

如果该文件存在,然后,它不能被重新创建,和server无法启动。

解决问题的方法是消除现有lok文件或 kill这个过程是被关押出来的文件被执行。

时间: 2024-10-27 13:14:46

【从翻译mos文章】Weblogic AdminServer 启动fail,报错&quot;unable to get file lock, will retry&quot;的相关文章

【翻译自mos文章】Weblogic AdminServer 启动fail,报错为&quot;unable to get file lock, will retry&quot;

Weblogic AdminServer 启动fail,报错为"unable to get file lock, will retry" 参考原文: Weblogic AdminServer fails with "unable to get file lock, will retry" error message (Doc ID 1613945.1) 适用于: Oracle WebLogic Server - Version 8.1 and later Infor

启动weblogic111g一直提示&lt;141281&gt; &lt;unable to get file lock, will retry ...&gt;

一次非正常关闭weblogic之后,再次启动时启动不成功,一直提示:<141281> <unable to get file lock, will retry ...> 解决方法:进入域目录: [email protected]:~$ cd oracle/middleware/user_projects/domains/yshy_domain/ (1)删除 edit.lok (2)进入config目录删除 config.lok (3)[email protected]:yshy_d

启动Weblogic时报 &lt;unable to get file lock, will retry...&gt;解决方案

启动Weblogic时,报 <unable to get file lock, will retry...>,解决方法: I ran into this error the first time I restarted Weblogic on one of my installs, the only reference that I was able to find is the error description below: BEA-141281 Info: unable to get f

WebLogic ERROR: unable to get file lock, will retry …

由于非正常结束Weblogic 进程才导致启动终端输出这样的错误信息     解决办法一.删掉Domain下的*.lok文件1. 删除edit.lok     cd <DOMAIN_HOME> 删除edit.lok文件     rm edit.lok2.删除 config.lok     <DOMAIN_HOME/config 删除config.lok文件     rm config.lok3.删除AdminServer.lok     cd <DOMAIN_HOME>/se

IntelliJ IDEA 启动tomcat 报错: idea Unable to open debugger port (127.0.0.1:58233): java.net.SocketException &quot;socket closed&quot;

debug启动项目弹出提示 Error running omp: Unable to open debugger port (127.0.0.1:50812): java.net.SocketException "socket closed" 错误.导致tomcat服务器无法启动. 1.根据端口号"80"查找进程号netstat -ano|findstr "80"TCP    0.0.0.0:80             0.0.0.0:0  

【翻译mos文章】Linux x86 and x86-64 系统中的SHMMAX最大值

Linux x86 and x86-64 系统中的SHMMAX最大值 参考原文: Maximum SHMMAX values for Linux x86 and x86-64 (文档 ID 567506.1) 目标: 问题1:32-bit (x86) Linux system 系统中的最大值? 问题2:64-bit (x86-64) Linux system系统中的最大值? 解决方案: 答案1: Oracle Global Customer Support 官方推荐 SHMMAX 的最大值是小于

【翻译自mos文章】在unix/linux中使用文件描述符(File Descriptors)来找回被删掉的文件(数据文件or redo log)

在unix/linux中使用文件描述符(File Descriptors)来找回被删掉的文件(数据文件or redo log) 参考原文: Retrieve deleted files on Unix / Linux using File Descriptors (Doc ID 444749.1) 适用于: Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.3 [Release 8.1.7 to 11.2] Linu

[Android]模拟器不能启动,报错:Cannot set up guest memory &#39;android_arm&#39;: Invalid argument

[错误] 模拟器无法启动,报错:Cannot set up guest memory 'android_arm': Invalid argument [解决办法] 在AVD中(Android Virtual Device Manager)将模拟器的RAM调成512. 参考:http://stackoverflow.com/questions/26620765/cannot-set-up-guest-memory-android-arm-invalid-argument 版权声明:本文为博主原创文

C# 解决SharpSvn启动窗口报错 Unable to connect to a repository at URL &#39;svn://....&#39;

在远程机打开sharpsvn客户端测试,结果报错 Svn启动窗口报错 Unable to connect to a repository at URL 'svn://...' 咋整,我在win10我的开发环境上没报错啊, 一时间各种的想象, 昨天先是svn客户端不能再win7上运行,后来编译平台换成X86模式,sharpsvn.dll 换成x86,问题解决 .注意:必须删除原先生成的bin文件,当时我只删除了exe文件,结果还是报错,debug 模式和 Release 都要换到x86 . 接着点