Tag: Managed Server

SOA_SERVER ( Managed Server ) Take too Long time to Start/Restart

Posted on by Osama Mustafa in Fusion Middleware
On the weblogic console when trying to start managed Server it’s take too long time to start in my case it’s SOA_SERVER, almost 25 min only to start, which is not correct . to avoid this problem you need to follow the below steps simple but effective :-

Under Java Home ( That Used by Weblogic ) :-

cd /u01/app/fmw/jdk/jre/lib/security 

There’s file called Java.Security 

Edit this File using any Editor ( vi for example ).

Search for the following line :-

securerandom.source=file:/dev/urandom

And Change it to :-

securerandom.source=file:/dev/./urandom

Or Another way add the below line to startup script in weblogic :-

-Djava.security.egd=file:/dev/./urandom

Hope this will solve your problem.

Thank you
Osama Mustafa

Managed Server ERROR: transport error 202: bind failed: Address already in use

Posted on by Osama Mustafa in Fusion Middleware

ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]

This Error Appeared when trying to start Managed server the Log Shown the above error, which already clear, in my case i have 2 managed server SOA and OSB in the same AdminServer each of them trying to access on the same PID process using Node Manager to solve this issue please follow the below steps.
Solutions :-
  • Inside Domain Path for example /u01/app/fmw/domains/Base_domain/bin
  • Edit setDomainEnv.sh and search for the below :-

if [ “${DEBUG_PORT}” = “” ] ; then
        DEBUG_PORT=”8453″
        export DEBUG_PORT
fi

if [ “${SERVER_NAME}” = “” ] ; then
        SERVER_NAME=”AdminServer”
        export SERVER_NAME
fi

  •  Add New Lines under the above to contain server name and available DEBUG_PORT on the server like the below:-

if [ “${SERVER_NAME}” = “soa_server1” ] ; then
   DEBUG_PORT=”7453″
   export DEBUG_PORT
fi

if [ “${SERVER_NAME}” = “osb_server1” ] ; then
   DEBUG_PORT=”7454″
   export DEBUG_PORT
fi

 Now Restart AdminServer and Try to start Managed Server, Take Backup from setDomainEvn.sh before editing.

Thank you
Osama mustafa

Managed Server BI_Server Unable To Start After Create Node manager Service

Posted on by Osama Mustafa in Fusion Middleware
Problem Description :

After Install Weblogic and BI On Windows, And Create Admin Server as Services BI_server unable to start, Node manager Created Service Created Without Any Error.

Cause & Solution : 

After Investigation I found Class Path is too Long So what i did like the following, Edit installSVC.cmd To set Classpath  to be Short

you will find the below line in the InstallSvc.cmd all you have to do is change it to be like Line in Red Color :

@echo off

echo %CLASSPATH% > %USERDOMAIN_HOME%\cp.properties

if “%ADMIN_URL%” == “” goto runAdmin
@echo on
set CMDLINE=”%JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS%
-classpath @%USERDOMAIN_HOME%\cp.properties 
-Dweblogic.Name=%SERVER_NAME% -Dweblogic.management.username=%WLS_USER%
-Dweblogic.management.server=\”%ADMIN_URL%\”
-Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE%
-Djava.security.policy=\”%WL_HOME%\server\lib\weblogic.policy\” weblogic.Server”

goto finish

Thank you
Osama Mustafa