• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

problem to starting server

 
karthik rajakumaran
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are 1 nested errors:

weblogic.management.ManagementException: Unable to obtain lock on D:\Documentum\
bea9.2\domains\DctmDomain\.\servers\adminServer\tmp\adminServer.lok. Server may
already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
va:159)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.ja
va:58)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirec
toryService.java:75)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
ager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
icesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)

>
<Apr 10, 2007 12:52:56 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Ser
ver state changed to FAILED>
<Apr 10, 2007 12:52:56 PM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A cr
itical service failed. The server will shut itself down>
<Apr 10, 2007 12:52:56 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Ser
ver state changed to FORCE_SHUTTING_DOWN>

how do i start serve? pls comment on this.
 
Shekar Atmakur
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Please kill all instances of Weblogic processes running on the system and then try starting the server again.
 
karthik rajakumaran
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks shekar,
I shut down the alreday running java.exe processes by using task manager.
Then I started weblogic server sucessfully.

Thanks for your reply,

Karthik Rajakumaran
 
Madusudhanan Ragothaman
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
seems like another instance of weblogic is running.

if you are running in a unix box do a

ps -ef | grep "java" or ps -ef | grep "weblogic" or ps -ef | grep "you istance name" and kill everything .

if windows , Say ctrl + alt + delete , kill all javac instance, and restart weblogic.

You should be fine
 
karthik rajakumaran
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks madhusudhanan,
I've did same as you scrabed.It starts fine.
Thanks for your reply.

Karthik Rajakumaran.
 
hazari yuvraj
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In unix env use command ps -ef|grep java to find java running process,kill the same.
restart the server.

Sunil Singh Yuvraj
 
Deepak Bala
Bartender
Posts: 6663
5
Firefox Browser Linux MyEclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This thread is around 2 years old. I doubt the OP is still around to read your reply, but thanks for posting your thoughts
 
Rajukpo kumar
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

May i know why this error is coming...?

I am using netbeans and weblogic. I am getting this error many times, 5-6 times a day. And whenever error occurred IDE will be strucked without any response.
So it is wasting my time a lot.

Any help!!!

Thanks,
Raju
 
anandraj tadkal
Ranch Hand
Posts: 98
Oracle Redhat
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Raju,

This error occurs in two scenarios:
1. If the server is already running.
2. If the server is not properly killed and at times it does retain some references to the .lok file under the tmp directory of the DOMAIN/server folder and the lok file is not relinquished totally.

When the server starts it checks if any .lok file in present in the tmp file.
If yes, it would try to acquire a lock on that one.

If the lock is already held by some other process, then it would throw this error.

Solution:
Check the running processes which can acquire lock on the .lok files and kill them.

Restart the server.

Cheers,
Anandraj
http://weblogic-wonders.com

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic