Windows – weblogic server Stopped, Error connecting to WebLogic domain

eclipseweblogicwindows

I was setting up my first workspace in Eclipse and Weblogic 10.3.6 server,

I started the Weblogic server and I am getting the below error in Server's Tab of eclipse.

   Oracle WebLogic server 11gR1 (10.3.6) base_domain [Stopped, Error connecting to WebLogic domain]

When I hopped on to the console tab of eclipse It says that the server is started in the Running Mode and also I was able to access the console login 

 <Feb 5, 2020 5:04:46 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> 
 <Feb 5, 2020 5:04:46 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>



 http://localhost:7001/console/login/LoginForm.jsp

I tried restart my machine and start the server using startWebLogic Windows command

I got the following Error message,

JAVA Memory arguments: -Xms1024m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=1024m  -XX:MaxPermSize=2048m
.
WLS Start Mode=Development
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http:\\hostname:port\console        *
***************************************************
starting weblogic with Java version:
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
<Feb 5, 2020 5:40:45 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java 
 HotSpot(TM) 64-Bit Server VM Version 24.79-b02 from Oracle Corporation>
 <Feb 5, 2020 5:40:55 PM CST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>
 <Feb 5, 2020 5:41:05 PM CST> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

I tried almost all the solutions available on serverfault and stackoverflow.

Any advice?

Best Answer

I had the same error. My problem was I was running an Nginx listening in port 7003. So, that was causing a port conflict with Weblogic. My solution was to remove that reverse proxy from Nginx. You could also check if you have any process listening on 7003 with the commands:

netstat -aon | findstr 7003

taskkill /f /pid

I hope this help anyone who get the same trouble.

Related Topic