This discussion is archived
14 Replies Latest reply: Sep 7, 2009 2:11 AM by 720305 RSS

weblogic server is not getting started.

717608 Newbie
Currently Being Moderated
Hi

We are getting problem in starting weblogic server 10.2 .
We have two machine they switch each other by cluster.
On one machine , Weblogic server does not start when cluster switch to this machine.
When server starts , it hangs. We get following eroor:

s*tarting weblogic with Java version:*
The Autonomy executable IDOLserver/DiSH/AutonomyDiSH.exe is not executable.  Cannot start the search engine.
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
Starting WLS with line:
*/home/bea/bea102/jdk150_11/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=256m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/home/bea/bea102/wlserver_10.0 -Dwls.home=/home/bea/bea102/wlserver_10.0/server -Dweblogic.home=/home/bea/bea102/wlserver_10.0/server -Dwli.home=/home/bea/bea102/wlserver_10.0/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/bea/bea102/patch_wss110/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlw1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wls1001/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlp1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/bea/bea102/wlserver_10.0/server/lib/weblogic.policy weblogic.Server*
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)

This issue is in our production environment. So plaese help me considering it URGENT.

Thanks
  • 1. Re: weblogic server is not getting started.
    716864 Newbie
    Currently Being Moderated
    Remove the following from the script that is used to start the server.
    -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n.
    This is used to debug the process and I don't think you may need to start a production system in debug mode.
  • 2. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    Thanks for reply.

    Yes U r right.
    We may need not to start a production system in debug mode but
    Server was stating nomaly previously. Now it hangs in between of server start giving error:

    ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
    JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)

    Please help me.
  • 3. Re: weblogic server is not getting started.
    717137 Newbie
    Currently Being Moderated
    It seems to me that you have WebLogic Portal instance that is using Autonomy that can not be started. Fail of this Autonomy search engine makes it critical for WLS to start. Autonomy can not bind to IP and port. There are potentially many reasons for that failure:
    1. It might be that you have already Autonomy running on this machine
    2. It might be that you have more than one instance of WLS (like two managed servers) on the same hardware and both of them are trying to start Autonomy with the same parameters (IP + port)
    3. You moved configuration from on hardware to another and forgot to change IP in the configuration of the Autonomy
    4. You changed IP address and you did not change IP in the Autonomy settings.

    Regards

    Maciej
  • 4. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    Thanks for ur reply.
    Nice to get your suggestion.
    I have some conclusion .
    1. It might be that you have already Autonomy running on this machine
    Our machine is linux. and I have checked
    # ps -ef|grep bea102
    root 12225 10361 0 16:20 pts/1 00:00:00 grep bea102
    # ps -ef|grep java
    root 15842 10361 0 16:23 pts/1 00:00:00 grep java

    No Autonomy is running.
    So there is no possibilty , that any other server is running.
    2. It might be that you have more than one instance of WLS (like two managed servers) on the same hardware and both of them are trying to start Autonomy with the same parameters (IP + port)
    On this machine , only one instance of server is installed. We have two different machine. Cluster switch from one machine to another when problem arise on one machine.
    3. You moved configuration from on hardware to another and forgot to change IP in the configuration of the Autonomy
    This is not. Our configuration has worked well for a long time. We are not using two instance of server on same machine.
    Suddenly problem arises. We did no changes.
    4. You changed IP address and you did not change IP in the Autonomy settings.
    We have not done this. But one thing is there that we have two machine and IP of both machine is mapped to single virtual IP.

    Please suggest some more root cause coz of that WLS is not starting and hangs on.
  • 5. Re: weblogic server is not getting started.
    717137 Newbie
    Currently Being Moderated
    This is interesting that your machine is linux because in the error message it shows that it tries to start "IDOLserver/DiSH/AutonomyDiSH.exe" - so it tries to start Windows executable file that of course does not exist on linux installation. Are these starting / environment scripts original? Or did you modify them?

    Check and verify also scripts for starting autonomy - they are placed in the %WL_HOME%\cm\thirdparty\autonomy-wlp10

    Maciej
  • 6. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    Hi

    I run this command to make u confirm that our machine is

    # uname -a
    Linux SL-CMSR1 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux

    Please suggest me why are we getting error while starting server.

    **ERROR: transport error 202: bind failed: Address already in use **
    **ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) **
    JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
  • 7. Re: weblogic server is not getting started.
    717137 Newbie
    Currently Being Moderated
    Chceck on netstat if port 8453 is available and
    - if YES than try to remove from starting scripts following flags "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n"
    - if NO modify in starting scripts port 8453 to other one

    Maciej

    Edited by: MaciejGruszka on 2009-08-18 01:21
  • 8. Re: weblogic server is not getting started.
    717866 Newbie
    Currently Being Moderated
    In setDomainEnv.sh, Change debug port to some other port (example :8452) and it shall work.

    Check this out :
    how to run weblogic 8.1 and weblogic 9.2 simultaneously
  • 9. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    I haved checked by netstat, 8453 is not available.

    and we also haved changed port from 8453 to 8455 in starting script.

    Still we are getting same error.
  • 10. Re: weblogic server is not getting started.
    717137 Newbie
    Currently Being Moderated
    Find in this script following lines:

    PRODUCTION_MODE=""
    export PRODUCTION_MODE


    And modify them to the following

    PRODUCTION_MODE="true"
    export PRODUCTION_MODE

    Rgrds


    Maciej
  • 11. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    Nice to help me.

    We observe the server start up log. We did all that you suggested.
    Still I am not able to start the production server. As we get very lesser chance to RND on production server.
    The new problem is now  , when we start the server, its hangs, and did not start.

    I am posting the sever startup log:
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


    J*AVA Memory arguments: -Xms256m -Xmx2048m -XX:MaxPermSize=256m*
    *.*
    WLS Start Mode=Production
    *.*
    CLASSPATH=""
    *.*
    PATH=""
    *.*
    *****************************************************
    ** 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:
    The Autonomy executable IDOLserver/DiSH/AutonomyDiSH.exe is not executable.  Cannot start the search engine.
    java version "1.5.0_11"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
    Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode)
    Starting WLS with line:
    */home/bea/bea102/jdk150_11/bin/java -server -Xms256m -Xmx2048m -XX:MaxPermSize=256m -da -Dplatform.home=/home/bea/bea102/wlserver_10.0 -Dwls.home=/home/bea/bea102/wlserver_10.0/server -Dweblogic.home=/home/bea/bea102/wlserver_10.0/server -Dwli.home=/home/bea/bea102/wlserver_10.0/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/bea/bea102/patch_wss110/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlw1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wls1001/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlp1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/bea/bea102/wlserver_10.0/server/lib/weblogic.policy weblogic.Server*
    *<Sep 1, 2009 1:14:12 AM LKT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:*
    */home/bea/bea102/wlserver_10.0/platform/lib/cm/content_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/wlp_services.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/analytics_sys.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/commerce_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/groupspace_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_system-full.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/nf-jspcmods.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/nf-system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wlp-schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wlp_content_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wps_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wsrp-common.jar>*
    *<Sep 1, 2009 1:14:12 AM LKT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_11-b03 from Sun Microsystems Inc.>*
    *<Sep 1, 2009 1:14:13 AM LKT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR348244 Fri Oct 19 11:57:37 PDT 2007*
    WebLogic Server Temporary Patch for CR346064 Fri Oct 19 13:27:18 PDT 2007
    WebLogic Server Temporary Patch for CR346063 Fri Oct 05 14:48:13 PDT 2007
    WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
    WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
    WebLogic Server Temporary Patch for CR346060 Thu Oct 18 15:28:01 PDT 2007
    WebLogic Server Temporary Patch for CR350528 Fri Nov 02 16:19:36 PDT 2007
    WebLogic Server Temporary Patch for CR354048 Thu Dec 06 13:52:09 IST 2007
    WebLogic Server Temporary Patch for CR348229 Wed Oct 24 13:49:07 PDT 2007
    WebLogic Server Temporary Patch for CR356295 Wed Dec 19 15:37:45 EST 2007
    WebLogic Server 10.0 MP1  Thu Oct 18 20:17:44 EDT 2007 1005184 >
    *<Sep 1, 2009 1:14:15 AM LKT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home/bea/bea102/license.bea>*
    *<Sep 1, 2009 1:14:15 AM LKT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>*
    *<Sep 1, 2009 1:14:15 AM LKT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>*
    *<Sep 1, 2009 1:14:15 AM LKT> <Notice> <Log Management> <BEA-170019> <The server log file /home/bea/bea102/user_projects/domains/tmpasldomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>*

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Sever hangs on the line

    */home/bea/bea102/user_projects/domains/tmpasldomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>*


    please give some more suggestion.

    Thnaks
  • 12. Re: weblogic server is not getting started.
    720305 Newbie
    Currently Being Moderated
    Hi,
    plz check your CPU utilization for this and check which service is using maximum percentage of CPU.
  • 13. Re: weblogic server is not getting started.
    717608 Newbie
    Currently Being Moderated
    Hi Frriend

    In the system only our application is running.
    I checked the CPU utilazation. Its is 0%.

    And previously server was getting started normally.
    So I dont think that CPU Utilization may be the issue.
    Kindly suggest me some more reason
    so that i can reach to root cause.
  • 14. Re: weblogic server is not getting started.
    720305 Newbie
    Currently Being Moderated
    Hi,
    When i was facing this issue, it was due to heap memory...i tuned it according to my RAM and then it worked saw your -Xms256m and -Xmx2048m, try keeping maximum and minimum heap to same figure.may be you JVM is taking too much of time to manage heap; and also try out increasing you -XX:MaxPermSize accordingly.
    also,
    check your garbage collection data, that will show you what the problem is, check for PermGeneration committed and Used size.If committed size is used completely try increasing MaxPermSize.

    Also take thread dump of your running process and analyze those by detecting deadlock and stuck threads.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points